A digital product passport is a structured digital record attached to a product, accessible via a data carrier (typically a QR code on the pack or label), that carries the product's identity, composition, origin, compliance and sustainability data. Different audiences see different views: a consumer sees ingredients and disposal guidance, a regulator sees the compliance evidence, a recycler sees the material breakdown.

The crucial point is that a passport isn't a document. It's a query interface over product data, which means it can only ever be as good as the data underneath it. A PDF with a QR code pointing at it is not a passport.

The Ecodesign for Sustainable Products Regulation entered into force in 2024 and is the framework under which product passports arrive. It doesn't impose passports on every product at once. Instead, the European Commission sets requirements product group by product group through delegated acts, each with its own data requirements and timeline. Textiles and iron and steel are among the first in scope, with chemicals-related and consumer product groups following through the working plan.

For cosmetics and chemicals businesses, the honest position is: the exact data fields aren't final for your category yet, but the direction is fixed and the lead time on product data is measured in years, not months. The businesses that will comply cheaply are the ones getting their composition, supplier and batch data into order now, before a delegated act names their category.

Take the plausible contents of a passport for a formulated product: the full composition with substance identifiers, the origin and chain of custody of key raw materials, the compliance status per market, the batch and manufacturing history, the safety documentation, and the end-of-life handling. Now ask where each of those lives in your business today.

In most cosmetics and chemicals companies the answer spans a formulation spreadsheet, an ERP, a shared drive of supplier PDFs, a regulatory consultant's files and someone's inbox. That patchwork is the real obstacle to the passport, and no passport tool fixes it, because the tool can only publish what it can read. This is the same fragmentation problem that sits underneath every other systems failure in this sector.

A standalone passport platform sells you the front half: the data carrier, the consumer-facing page, the registry connection. It assumes the back half (clean, current, structured product data) already exists. Where it doesn't, the passport tool becomes another system someone populates by hand, and every product change becomes a passport update someone has to remember to make.

The working arrangement is the inverse: fix the record first, then let the passport be generated from it. When the composition changes, the passport view changes, because there was never a separate copy to update. That's the same principle behind specification management that doesn't drift applied to a regulated, public output.

Three moves cover most of the distance. First, get composition and substance data out of spreadsheets and into a structured record with versions and approvals. Second, attach supplier documentation to the materials it certifies rather than to an inbox. Third, connect batch history to the product it produced, so chain of custody is a query rather than an archaeology project.

None of these is a passport project. All of them pay back before a single delegated act lands, in faster dossiers, cleaner audits and fewer surprises. The passport, when your category is named, becomes a formatting exercise rather than a data rescue. See what Worldover is for the record this sits on, and PLM for cosmetics manufacturers for the product-definition layer in practice.