Connect Commercetools with Omnisend to sync customers and events for targeted email and SMS automation, better segmentation, and cleaner reporting across campaigns.
• Customer profiles and marketing permissions are synchronized between commercetools and Omnisend, with email or phone used as the primary identifier and duplicates handled via merge rules.
• Order and cart events are forwarded from the storefront or middleware to Omnisend as event payloads, including totals, currency, discounts, and line items for abandoned cart and post-purchase flows.
• Product data for Omnisend catalog features is exported from commercetools, mapping key fields such as SKU, name, price, image URL, product URL, categories, and availability.
• Delta sync logic sends only created or updated entities since the last run, while full refresh jobs can rebuild the catalog feed when mappings change.
• Locale and channel-specific values in commercetools are mapped to Omnisend fields, with fallback rules applied when a localized attribute is missing.
• Sync jobs validate required attributes, log rejected records with error context, and retry transient failures while keeping idempotency for repeated webhooks.
.png)
We map Commercetools events to Omnisend triggers via API so flows fire on real behavior, not delayed exports. Tracking is validated end to end, including deduplication and identity rules.
Typical sync includes customer profiles, consent, product data needed for templates, and events like browse, cart, checkout, purchase, and returns. We keep attribute naming consistent so segments stay stable as your catalog evolves.
Yes, we can route data by store, locale, currency, and channel, and apply country-specific consent logic. This helps keep lists clean and messaging compliant across markets.
We sync the fields Omnisend needs from Commercetools and refresh them on schedule or on change events, depending on your setup. That reduces bad links, wrong prices, and “sold out” promos.
Custom makes sense when you need strict data governance, custom event logic, or higher-volume sync that must be monitored and retried automatically. scandiweb has delivered 2,100+ eCommerce projects since 2003, so we’re used to building integrations that hold up under growth.














