Shopify Salsify integration

Retail and your own store. The same data.For brands that send their product data to retail partners and want to use the same maintained version in their own Shopify store.

When the combination pays off

Salsify usually comes from a different direction than classic PIM projects: brands use it to deliver product data to retail partners and marketplaces, in their formats and with their mandatory fields. Your own Shopify store is then one more channel, and it benefits from the fact that the data is fully maintained anyway.

That is exactly where the value of the combination lies: you maintain once, for retail and for your own channel. The catch is that retail data looks different from store data. Mandatory fields for retailers are rarely good product copy for end customers. That translation belongs in the integration, not in hope.

Which objects run in which direction

Shopify is one of several output channels here. Transactional data stays entirely in the store.

Object	Direction	Leading system	Note
Products	→ Shopify	Salsify	Approved product data per channel, with its own field selection for the store.
Media	→ Shopify	Salsify	Images and data sheets from the central media library.
Prices	→ Shopify	Split by field	Only when no ERP leads. Otherwise the price stays with the ERP.
Inventory	no sync	-	Stock belongs in the ERP or the warehouse system.
Orders	no sync	-	Orders bypass Salsify entirely.
Customers	no sync	-	Customer data does not belong in a PIM.

Which integration pattern holds up

Shopify as its own channel
Salsify thinks in channels with their own field selection. Setting Shopify up as its own channel is the clean route: you decide exactly which fields go into the store, without bending the retail formats out of shape.
iPaaS between PIM, ERP and store
Worth it as soon as prices and stock levels from an ERP come into play. The integration platform makes sure two sources do not write the same Shopify field and that the order of runs stays traceable.
Custom middleware
The route when retail data first has to become sellable store content: combining fields, converting units, choosing texts. Rules like these belong in code, where they can be checked.

Common pitfalls

Retail fields passed to the store unfiltered
Mandatory entries for retail partners are often unreadable for end customers. Without a separate field selection for the Shopify channel, technical labels and codes land directly on the product page.
Two sources for one field
If the ERP and Salsify both write titles or prices, the last run wins. Responsibility per field has to be settled beforehand, otherwise product pages change their content without anyone noticing.
Media without rules
Data sheets, packaging shots and cut-out images play different roles in retail than in the store. Without a defined order and selection, the wrong image ends up first on the product page.

Frequently asked questions

Is Salsify worth it if we only run Shopify?

Usually not. Its strength lies in supplying retail partners and marketplaces in their own formats. For pure direct-to-consumer selling without any retail connection, leaner PIM tools or Shopify itself are the more pragmatic route. Salsify only pays off once trading partners are part of the picture.

Which fields belong in the Shopify channel?

Only the ones a product page actually needs: title, description, selling points, dimensions, media and filterable properties. Mandatory fields that exist for retail partners stay in their own channels, otherwise the product page becomes unreadable for the people you are selling to.

How do attributes arrive in Shopify?

As metafields with a fixed definition. That is the precondition for properties being rendered in templates, used for filters and provided in structured data in a machine-readable form. Free text in the description gives you none of those three things.

Which system leads on prices and stock?

In almost all cases the ERP or the warehouse system, not the PIM. Salsify describes products, it does not calculate availability. If no ERP exists, that is the real gap in the setup, not a missing field in the PIM.

How are translations handled?

Translations come from the PIM if they are maintained there for retail anyway. What matters is that Shopify translations are not overwritten on every run. Which language comes from which source has to be decided beforehand, not discovered after the first sync.

Shopify Akeneo integrationFor brands with many attributes, languages or channels that no longer want to maintain product information twice, in the Shopify admin and in spreadsheets.View integration Shopify Plytix integrationFor smaller brands outgrowing spreadsheets that want to maintain product data in a structured way, without introducing an enterprise PIM.View integration Shopify Pimcore integrationFor companies that model their product data in Pimcore and put Shopify in front as the sales channel instead of running their own store.View integration

System integration: patterns and data ownershipThe overarching view of ERP, PIM, WMS and middleware.