Integration combo
Shopify to Emarsys integration
Shopify holds the transactional truth: orders, customers, behaviour. Emarsys (SAP Emarsys Customer Engagement) is the enterprise engagement platform: lifecycle programmes, AI-driven segmentation, tactical content. Connecting them properly means real-time customer and order data feeds the engagement programmes; consent state is respected; product context lets recommendations reflect what's actually in the catalogue. We design, build and support Shopify-to-Emarsys integrations as a Patchworks Partner Agency.
Flow shape
Customer + order sync: Shopify to Emarsys
Customers, orders and product context flow from Shopify into Emarsys on a real-time cadence, with consent state and segment logic enforced at the integration boundary.
- Trigger Shopify Customer / order event webhook
- Extract Patchworks Ingest event queue, dedupe
- Decision Patchworks Consented? channel-level opt-in
- Transform Patchworks Map to Emarsys contact, sales data, products
- Action Emarsys Push update via Suite API
- Writeback Shopify Tag synced for audit
Illustrative only. The diagram above shows how an integration of this shape works in concept. It is not a screenshot or export of the actual Patchworks process flow; the production flow has more nodes, more branches and more error handling than a marketing page can usefully render.
What we sync
2 synchronisations between Shopify and Emarsys.
Only the data flows that both platforms actually support. Each section below describes what’s in scope, the gotchas we watch for, and how the flow is shaped inside Patchworks.
- 01
Order sync
Shopify Emarsys
Orders raised in Shopify flow into Emarsys on creation, status change and edit. The flow normalises Shopify's order schema into the record shape Emarsys expects, including line-level discounts, taxes, gift cards, shipping methods and multi-currency. Partial cancellations and post-capture edits are handled with idempotent updates so Emarsys stays the system of record without double-counting. Edge cases that come up most often on this pair: backorders, pre-orders, subscription rebills and orders placed through guest checkout with no matching customer record on the destination side.
- 02
Customer sync
Shopify Emarsys
Customers created or updated in Shopify flow into Emarsys with a stable cross-system identifier so the same shopper isn't fragmented into duplicates across the estate. Addresses, marketing preferences, B2B account hierarchies, tax exemption flags and channel attribution are mapped explicitly rather than left to Emarsys's defaults. Where Emarsys is the customer system of record (CRM or ERP) we publish back into Shopify so storefront personalisation and segmentation reflect the canonical state. GDPR deletion and rectification are propagated across the integration in both directions.
Typical delivery
6 to 10 weeks for a standard delivery.
Up to 5× faster using PatchBuddy- Week 1 Discovery: contact schema, sales-data fields, product catalogue feed, consent model.
- Weeks 2 to 5 Build: contacts, orders, products, behavioural events, consent gates.
- Weeks 6 to 7 UAT with marketing automation team.
- Weeks 8 to 10 Cutover and hyper-care into retainer.
Patchworks delivery
How Patchworks shapes Shopify to Emarsys.
Emarsys's data model rewards integration discipline: clean contact schemas, structured order shapes, product feeds that arrive on cadence. Patchworks gives the merchant a controlled boundary between Shopify's flexible storefront and Emarsys's stricter expectations. Flows live in Patchworks with full audit trail, consent gates fire at the boundary, and the runbook documents every field that crosses the wire.
Got more connectors that need to live in this flow? A 3PL, a marketplace, returns, a PIM, anything. We can do it. Most live integrations end up larger than a pair, all built and supported as one estate. More on multi-platform estates →
Our Patchworks practiceQuestions
Common questions.
-
01 Can Emarsys triggers fire from Shopify events?
Yes. Patchworks normalises the Shopify event stream and pushes the relevant signals into Emarsys so lifecycle programmes fire on real customer behaviour rather than on a daily batch. -
02 How is consent state handled across channels?
Channel-level consent (email, SMS, push) is the gating signal; the integration honours each channel separately rather than treating consent as binary. Withdrawal suppresses the contact within minutes on the next cycle. -
03 What about product feed depth?
Emarsys's product feed accepts as much catalogue data as the merchant wants to push. We size the feed at discovery: enough to drive recommendations and content, not so much that maintenance becomes its own project. -
04 Do you support this under SLA after go-live?
Yes. Monitoring on every shipped flow, on-call cover, monthly health checks and tiered response SLAs from £750/month.
Get in touch
Tell us what you’re trying to connect.
And what’s in the way. We will tell you whether we are the right people to do it. Drop us a line below, or open the chat in the corner of the screen.
Direct: contact@ecirql.com
Message sent
Thanks. We’ll be in touch.
Your message is in our inbox. A human will read it and reply within a working day. For anything urgent, drop us a line at contact@ecirql.com or open the chat in the corner of the screen.