A catalog in Bloomreach Engagement is a structured dataset of items you import into the platform, such as products, articles, or stores, and reference in campaigns. Each item has an ID and a set of fields, such as name, price, image URL, stock status, or category. You look an item up in Jinja and read its fields, for example `catalogs['Products'].item_by_id(product_id)` followed by `item['display_name']`.
Category
Bloomreach Engagement, data
Also known as
Bloomreach catalog; catalogs; catalog item
Catalogs are imported and kept in sync from a feed, file, or API, and each has a schema of typed fields. They are what makes a message about the customer’s own products rather than generic copy: product blocks, recommendation sliders, price and stock lines, and dynamic content all read from a catalog by ID. A single catalog can back many campaigns at once, which is why its data quality sets a ceiling on everything rendered from it.
In practice
Most product names, prices, and recommendation blocks in Bloomreach emails and weblayers are catalog fields rendered through Jinja. That makes the catalog the highest-impact place to fix field-level issues: get the value right once at the field level (encoding, formatting, a non-breaking space between a number and its unit) and every campaign that reads it inherits the fix, instead of patching each template. Two habits prevent silent failures: import as UTF-8 so special characters survive, and always guard the lookup with an {% if item %} check, because referencing a field on a missing item fails the whole render.