Connect commercetools with Kontainer DAM to link SKUs to images, video, and metadata, so teams can publish consistent assets across PDPs, retailers, and product data workflows.
• SKUs and product identifiers in commercetools are mapped to Kontainer asset links, with asset IDs stored as references on products or variants.
• Asset metadata in Kontainer (titles, tags, usage rights, locale fields, and custom attributes) is mapped to commercetools attributes for consistent downstream consumption.
• Product media relationships are synchronized via API, with delta updates sending only changed assets or metadata when available.
• Image and video renditions are delivered through Kontainer URLs, and rendition presets are selected per channel where defined.
• Ownership is split: asset files and media governance remain in Kontainer, while product structure, pricing, and inventory remain in commercetools.
• Sync jobs validate required fields (SKU link, media type, and locale), and processing logs capture errors, retries, and skipped records for auditability.
.png)
We map commercetools product types, SKUs, and attributes to Kontainer assets, then sync references and metadata via APIs so PDPs pull the right image, video, and tags.
Common sync includes SKU links, asset URLs, titles, alt text, rights info, campaign tags, and language-specific metadata for images and video.
Yes. Kontainer can hold brand-approved media and enrichment metadata, while commercetools remains the system of record for pricing, inventory, and checkout.
It can, as long as your localization model is defined. We sync per locale and channel so each market gets the correct assets, copy variants, and usage rights.
We use approval states, permissions, and validation rules in Kontainer, then only publish approved assets into commercetools references or downstream feeds.




