Create and maintain product catalogs
Group eligible products into reusable, auditable sets for campaigns, recommendations, and publishing destinations.
What you’ll achieve
- A purposeful, current product set that can be reused without exposing unavailable or incomplete items.
Follow the workflow
-
1
Open Data → Own Data → Catalogs
Confirm the connector and workspace, then review existing catalogs before creating overlapping product groups.
-
2
Define the catalog purpose
Name the audience, season, channel, market, or merchandising use clearly. Avoid generic names that do not explain why the set exists.
-
3
Choose inclusion logic
Use supported product attributes, collections, availability, price, vendor, type, tags, or explicit selections. Keep rules narrow enough to inspect and broad enough to stay maintained.
-
4
Exclude unsuitable products
Remove unavailable, incomplete, restricted, duplicate, wrong-market, or missing-destination items before using the catalog externally.
-
5
Preview the resolved products
Check item count and sample records after saving. Inspect images, titles, variants, price, currency, and availability rather than trusting the rule alone.
-
6
Use and recheck the catalog
Select the catalog in supported recommendations or publishing flows, and review it before seasonal launches because connector changes can alter membership.
Verify your work
- Catalog membership matches its written purpose
- No sampled item is unavailable, incomplete, or in the wrong market
- The catalog resolves correctly in a supported downstream editor
If something doesn’t look right
Catalog is empty
Test each inclusion rule and confirm synchronized products contain the chosen attributes.
Unexpected products appear
Add exclusions or repair the source product fields.
Membership changed
Compare connector updates and dynamic rules before a campaign launch.
Limitations and safeguards
Dynamic catalogs change when source product fields change; capture or approve a final product set when a campaign requires a fixed selection.