Integration pattern
PIM and catalog integration pattern
PIM and catalog integrations keep attributes, media, variants, localization, search data, and channel completeness consistent.
Data Flow
Pattern data flows
- product model, attributes, variants, bundles, and classifications
- digital assets, alt text, technical documents, and media metadata
- localized copy, channel completeness, and enrichment rules
- catalog publication, delta updates, validation, and rollback
Checklist
Pattern checklist
Step 1
Define source of truth for every object in the lane.
Step 2
Choose real-time, event-driven, scheduled, or batch sync per flow.
Step 3
Document payload contracts, transformations, identifiers, and validation.
Step 4
Build retries, idempotency, monitoring, reconciliation, and runbooks.
Step 5
Link the pattern to platform-specific pages and provider pages.
Which platforms does this pattern support?
CCI applies this pattern across SAP Commerce Cloud, Salesforce Commerce Cloud, Shopify Plus, Adobe Commerce, commercetools, BigCommerce, VTEX, Spryker, OroCommerce, WooCommerce, and custom stacks.
Can we use this pattern for an existing integration?
Yes. It can be used as an audit model to find missing ownership, mapping, monitoring, or recovery steps.
Does this require middleware?
Not always. Middleware is useful when orchestration, transformation, queueing, or multi-system routing is needed. Direct APIs may be enough for narrower flows.
Related Pages
Related pages
Use this pattern on your stack.
Book discovery and we will adapt the pattern to your systems, owners, and roadmap.