Integration combo
Salsify to Mirakl integration
Salsify holds the canonical product master data. Mirakl operators each have their own attribute requirements, category trees and listing rules. The integration moves product data from Salsify into Mirakl operators with each operator's specific rules enforced at the boundary so the merchandising team works in one system rather than reconciling spreadsheets per operator. Built and supported as a Patchworks Partner Agency.
Flow shape
Product sync: Salsify to Mirakl
Salsify product master data publishes onto each Mirakl operator with the operator-specific attribute set, category and listing rules enforced at the integration boundary.
- Trigger Salsify Channel publish per-operator channel
- Extract Patchworks Ingest product queue, dedupe
- Transform Patchworks Map to operator attribute set, category, media
- Decision Patchworks Validates? operator-specific rules
- Action Mirakl Publish listing OF24, OF25 endpoints
- Writeback Salsify Mark synced with operator + SKU
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 Salsify and Mirakl.
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
Product sync
Salsify Mirakl
Product master data syncs from Salsify to Mirakl on publish, with channel-aware enrichment so Mirakl only receives the attributes it can act on. Variants, option sets, media, locale-specific copy, category mappings and metafield or extension data are handled explicitly. New SKUs flow in; deprecated SKUs are flagged rather than hard-deleted so historical orders stay intact. Where Mirakl has channel-specific requirements that Salsify does not natively model (typing rules, required attributes, image dimensions), the integration enforces them at the boundary rather than asking the merchandising team to.
- 02
Product syndication
Salsify Mirakl
Channel-ready product feeds from Salsify push to Mirakl respecting each channel's category taxonomy, required attributes, image requirements and compliance fields (origin country, hazmat flags, age restrictions). Locale-specific copy and pricing variants are sent through together so the channel listing is shippable on arrival rather than needing manual cleanup. New product launches and re-launches use the same flow as routine updates, with a publication-state field gating visibility until the merchandising team explicitly green-lights the listing.
Typical delivery
6 to 10 weeks for a standard delivery.
Up to 5× faster using PatchBuddy- Week 1 Discovery: operator landscape, attribute mapping, category trees, media.
- Weeks 2 to 4 Build: per-operator transforms, validation rules, publish flows.
- Weeks 5 to 7 Integration testing against operator UAT sandboxes.
- Weeks 8 to 10 Cutover and hyper-care into retainer.
Patchworks delivery
How Patchworks shapes Salsify to Mirakl.
This is one of the integrations Patchworks is best suited to: many-to-many mapping between Salsify's canonical product shape and the per-operator Mirakl requirements. We build operator-aware transforms in Patchworks, each one a versioned canvas, and the merchandising team manages overrides centrally rather than operator-by-operator. Runbooks cover the cases Mirakl's exception reports surface at month-end.
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 We list on five operators. Does that mean five integrations?
One integration, five operator transforms. The Patchworks canvases are operator-aware; adding a sixth is a configuration exercise, not a rebuild. -
02 How are operator-specific category trees handled?
Each operator's category tree maps to Salsify's master taxonomy via per-operator translation tables. Mapping changes happen in one place; downstream operators inherit the updates. -
03 What about operator-specific image and content rules?
Enforced at the integration boundary. Image dimensions, alt-text length, attribute formatting and content-tag rules are validated before publish; rejected payloads land in a queue for merchandising review rather than blocking the rest of the catalogue. -
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.