EU Digital Product Passport (DPP)

What a Digital Product Passport actually is

A Digital Product Passport is a digital record tied to a specific product, usually reached by scanning a QR code or tapping an NFC tag. Where a printed label carries a handful of fixed claims, a passport carries structured information — materials, origin, production details, care and repair guidance, and supporting documents such as certifications or test reports.

The same record serves several audiences at once. A customer scanning in a shop sees provenance and care information. A recycler sees material composition and disassembly guidance. A market surveillance authority sees the compliance evidence behind a claim. What each audience sees can differ: brands typically publish high-level transparency while keeping sensitive supplier detail internal.

Three things separate a passport from a product page

• It is tied to an identifier. The record belongs to a product or batch, not to a marketing campaign, and the identifier is what makes it verifiable.
• It is structured. Fields rather than prose, so the data can be read by systems as well as people, and compared across products and suppliers.
• It is maintained after sale. Repairs happen, components get replaced, ownership changes, recalls occur. A passport is designed to reflect those updates while the scan destination stays the same.

What ESPR changes

The Ecodesign for Sustainable Products Regulation is a framework. It establishes that products placed on the EU market will carry passports, but it does not by itself specify which fields your product needs. Those requirements arrive through delegated acts, adopted product group by product group.

This is the single most important thing to understand about the rollout, and the reason the question “when does this apply to us?” has no universal answer. Batteries, textiles, electronics, construction products, furniture and plastics each follow their own timeline, and each will be told to carry a different set of data. The category timelines below reflect that.

Why the data work starts before the deadline

Publishing a passport is fast. Collecting the information that goes into it is not. Material composition, facility details and supplier certifications usually live across CSV exports, spreadsheets, email threads and legacy systems, often held by tier-two suppliers a brand has no direct relationship with. That collection work is measured in quarters, not weeks, and it is the part that cannot be compressed once a deadline is close.

The practical consequence is that waiting for your category’s delegated act to be finalised is the expensive path. A useful set of fields repeats across every product group published so far — product identifier, product name, materials, country of origin, and manufacturing facility. Those are safe to start structuring now, whatever your category’s final requirements turn out to be.

Starting without perfect data

Most teams begin with incomplete data, and that is a workable starting point. The approach that holds up is to map whatever exists today into a consistent structure, flag what is missing, then prioritise the gaps that carry real compliance or customer weight. That produces a usable passport without waiting on a perfect database.

Scope the first pass tightly: one product line, a defined set of fields, a simple scan experience. A pilot validates the data model, the supplier workflow and the scan experience together — and once those three are proven, scaling becomes a repeatable operational task rather than an open question. Ownership is usually cross-functional, with supply chain holding the truth about suppliers and materials, compliance holding the requirements, IT supporting integration, and brand owning what the customer sees. One accountable owner with a small working group across those teams tends to work better than a committee.