Connect Commercetools with Tidio to capture pre-purchase questions, trigger smart chat flows, and route chats to support inboxes for faster replies and more recovered carts.
• Tidio is embedded on the Commercetools storefront via a widget snippet, and chat sessions are associated with a browser session or identified customer when available.
• Customer identifiers and consent state are passed to Tidio so known shoppers can be recognized across conversations, with anonymous visitors kept as guest profiles until they identify themselves.
• Order events from Commercetools (creation, status changes, shipment, and cancellation when exposed) are synced or pushed to Tidio as conversation context and timeline attributes.
• Cart snapshots and key totals are mapped to Tidio visitor fields to surface “what’s in cart” context during live chat without exposing full line-item data when not required.
• Webhooks and/or scheduled delta syncs route only changed records, with retries and idempotency keys used to avoid duplicate updates on transient failures.
• Sync jobs validate required fields, log payloads and responses, and store correlation IDs so support-side context can be traced back to the originating Commercetools entity.
.png)
We pass Commercetools session, cart, and order identifiers into Tidio as visitor properties so agents see context while chatting. The exact mapping depends on your storefront (custom, Next.js, or other) and consent setup.
Typically cart items, order number and status, shipping method, and basic customer identifiers. We scope fields to what support needs and what you can expose safely.
Yes, chats can be routed to Tidio inboxes and converted into tickets, with order IDs stored for follow-up. We also add deep links back to Commercetools tools or your OMS when needed.
Yes, we can segment flows and routing by locale, store key, currency, or market. This keeps automation and agent queues aligned with how your Commercetools project is structured.
scandiweb has delivered 2,100+ eCommerce projects since 2003, including complex integrations across platforms. We build the integration as a versioned, testable layer so it’s easy to extend and audit.














