Brands running Salsify already think in channels: the same product content flows to Amazon, retail partners, and their own shop, each with its own format requirements. The Digital Product Passport fits that mental model precisely. It is one more destination for content you already manage, with a format defined by EU law instead of a retailer. Here is how the connection works and what is specific about the Salsify case.

The DPP as another syndication target

The Ecodesign for Sustainable Products Regulation (Regulation (EU) 2024/1781) requires product data to be publicly accessible via a data carrier on the product, with category-specific requirements arriving through delegated acts. The EU's central DPP registry has been live since 19 July 2026. In Salsify terms: a new channel with a fixed schema, a validation step, and a registry submission.

The difference from a retail channel is what happens after publication. A DPP is not a listing that gets replaced next season. It stays resolvable for the product's lifetime, it can carry service functions, and for some categories it will need batch or item granularity that no retail channel asks for.

How the integration works

dpp.cloud connects to Salsify's REST API. The pattern matches our other PIM integrations, documented in creating a DPP from PIM data:

1. Sync: product changes flow from Salsify via API, on save or on a schedule
2. Mapping: Salsify properties map to DPP fields. Composition, care, certifications, origin: most of it exists because retailers already demanded it
3. Validation: products missing required DPP fields get flagged in a work list
4. QR generation: each product gets a stable QR code, written back to a Salsify property if you want it in your artwork workflow

Salsify users have one structural advantage worth naming: years of retailer syndication tend to enforce data completeness. Brands that survive Amazon and major grocery onboarding usually have their composition and compliance properties in better shape than the average PIM user. The gaps we see are the same as everywhere, in circularity data: recyclability, take-back, repairability. Three to five new properties usually close them.

One catch: category timelines differ

Salsify's customer base leans toward consumer goods, and the ESPR timeline is category-specific. Textiles and apparel are in the first working plan wave, with the obligation realistically landing in late 2028 or 2029. Food is out of ESPR scope entirely. Consumer electronics is not in the first wave. Before planning a rollout, check where your categories actually sit on the DPP timeline. For large companies selling apparel, one obligation already applies: the ban on destroying unsold clothing and footwear, in force since 19 July 2026.

Compliance data in, service channel out

Publishing compliance data is the mandatory half. The QR code on the product is also a channel that belongs to you rather than a retailer, which is a rare thing for brands that sell mostly through third parties. A scan can open care guidance, registration, spare parts, or a support conversation, and with item-level passports each unit carries its own history. For brands whose customer relationships are otherwise mediated by retailers, that direct line is arguably worth more than the compliance checkbox. We ran the revenue numbers in turning QR scans into after-sales revenue.

Timeline and cost

A Salsify integration follows our standard PIM schedule: two to three weeks from kickoff to a validated pilot product, then rollout. Pricing is flat, 10,500 euros per year for Growth or 17,500 euros for Professional, with no per-SKU fees. The platform comparison is in the DPP software buyer's guide.

Next step

If you run Salsify and want to know which of your properties map straight to the DPP schema and where your gaps are, book a 30-minute strategy session. Bring a property export and we will give you a concrete gap list in the call.

Book your strategy session