Integration combo
Salsify to Shopify integration
Salsify treats commerce experience management as a discipline: structured product data, multi-channel publishing, enrichment as a first-class workflow. Shopify is one publication destination among several. The integration moves product master data, variants and channel-ready content from Salsify into Shopify on publish so the storefront receives the canonical content without merchandising duplicating work. Built and supported as a Patchworks Partner Agency.
Flow shape
Product sync: Salsify to Shopify
Products publish from Salsify into Shopify with the right variant tree, media, metafields and category mappings on each channel publish event.
- Trigger Salsify Channel publish Salsify Channel event
- Extract Patchworks Ingest product queue, dedupe
- Transform Patchworks Map to Shopify variants, metafields, media
- Decision Patchworks Exists in Shopify? lookup by SKU
- Action Shopify Create or update via Admin API
- Writeback Salsify Mark synced with Shopify ID
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 Shopify.
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 Shopify
Product master data syncs from Salsify to Shopify on publish, with channel-aware enrichment so Shopify 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 Shopify 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 Shopify
Channel-ready product feeds from Salsify push to Shopify 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
5 to 8 weeks for a standard delivery.
Up to 5× faster using PatchBuddy- Week 1 Discovery: Salsify Channel setup, variant model, metafield use, media.
- Weeks 2 to 4 Build: products, variants, media, metafields, publication gate.
- Week 5 Integration testing against staging Shopify.
- Weeks 6 to 8 Cutover and hyper-care into retainer.
Patchworks delivery
How Patchworks shapes Salsify to Shopify.
Salsify publishes via its Channel mechanism; Shopify's data model needs careful translation around variants, metafields and media. Patchworks gives the merchant a controlled boundary: Salsify owns the master data, Shopify receives the storefront-ready shape, and merchandising never edits product data in two systems. Flows version in Patchworks against the merchant's release process and the runbook covers the cases where Shopify rejects payloads Salsify considers valid.
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 How are Salsify Channels and Shopify publications related?
Each Shopify channel (Online Store, Point of Sale, Hydrogen, etc.) can map to a Salsify Channel if needed. Most merchants publish via a single Shopify-bound Channel; we model multi-channel at scoping where it's needed. -
02 What about variants and Shopify's three-option limit?
Where Salsify carries more variant axes than Shopify's three-option model allows, we collapse the least-significant axes into metafields. We document the trade-off explicitly so merchandising knows what's going where. -
03 How does this handle Salsify enrichment workflows?
Salsify's workflow state is the gating signal. Products only publish to Shopify when the relevant readiness state is reached, so partially-enriched records don't leak onto the storefront. -
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.