Connect Commercetools with Salsify to sync product content, attributes, and digital assets, so your teams publish accurate PDPs faster across every channel and market.
• Product records are exported from Salsify via API and mapped to Commercetools product types, attributes, categories, and variant structures (SKU, key, EAN/UPC).
• Locale-specific fields in Salsify are mapped to Commercetools localized strings so language values are written per locale with consistent fallbacks.
• Assets and media URLs are synced as product images and other assets in Commercetools, with ordering and alt text handled when available in Salsify.
• Delta sync logic sends only changed products and variants, with idempotent upserts keyed by SKU or product key to avoid duplicates.
• Validation rules check required attributes and data types before write, and failures are logged with record-level error details for retry handling.
• Channel-specific fields can be routed to separate Commercetools products, staged vs. current projections, or downstream feeds depending on catalog ownership rules.
.png)
We define a field-by-field mapping, including variant-level attributes, enums, and constraints, then validate it against Commercetools product types before any bulk sync.
Yes. We move images, documents, and key rich content fields, and keep references consistent so storefronts and downstream feeds pull the right asset every time.
We map locales and fallback rules, then sync localized titles, descriptions, and attributes into Commercetools localized fields per market and channel needs.
We use delta-based sync with update rules and source-of-truth logic, so only approved fields update and business-owned fields in Commercetools stay intact.
Timeline depends on catalog complexity, localization, and asset volume, but scandiweb has delivered 40+ PIM projects since 2016, so we know where integrations usually slow down.














