Connect Commercetools with Pimberly to centralize product data, speed up enrichment and localization, and publish consistent PIM content to every storefront and feed.
• Product records in Pimberly are mapped to Commercetools product types, variants, attributes, and categories, with channel- and locale-specific values mapped to Commercetools localized fields.
• Asset metadata and image URLs are synchronized, and Commercetools product images are linked to the relevant variants based on Pimberly’s asset associations.
• Delta-based exports send only changed products and assets, while full syncs support initial loads and periodic reconciliation of the Commercetools catalog.
• Identifiers such as SKU, key, and external IDs are used to match entities, with validation handling for required attributes, attribute types, and option sets.
• Publish events in Pimberly trigger update jobs that create or update products in Commercetools, with status and error details written to logs for traceability.
• Category trees and product assignments are kept aligned, including mapping rules for taxonomy changes and handling of removed links without deleting master records.
.png)
We map Pimberly fields to Commercetools product types, attributes, and variant structures, then validate required fields and enums to prevent import failures.
Yes – we sync localized strings, assets, and channel-specific content so each Commercetools locale stays consistent with Pimberly approvals.
Typical sync includes titles, descriptions, attributes, categories, images, and pricing-ready metadata, with rules for what Pimberly owns versus what stays in Commercetools.
It can, as long as we model store views, channels, or projections correctly and enforce per-market completeness checks before publish.
Most timelines depend on catalog size and data quality, but scandiweb has delivered 40+ PIM projects since 2016, so we know where integrations tend to stall and how to avoid it.














