Understand / Practical guide
What is a Digital Product Passport?
A Digital Product Passport (DPP) connects an identified physical product to structured digital information that relevant people and systems can access. For EU compliance, its content, level of identification and access rules come from the legislation applicable to that product.
A product record with a purpose
A passport makes information usable beyond the organisation that created it. A repairer may need disassembly instructions; a recycler may need material information; a buyer may need verified product characteristics; an authority may need conformity evidence. These users need different views of the same identified product.
The EU objective is to make information support more sustainable products, circular use and compliance. A passport is an information mechanism. It does not, on its own, prove that a product is sustainable or replace performance requirements. See the Commission’s DPP overview.
How the physical and digital parts connect
| Component | Purpose | Example—not a prescribed design |
|---|---|---|
| Product | The object or group the record describes | A garment model, a manufacturing batch or an individual battery |
| Identifier | Keeps the record attached to the right object | A persistent product identifier; model, batch or item granularity |
| Data carrier | Makes the identifier accessible | A scannable code on an allowed physical location |
| Access service | Finds the appropriate information | A resolver or service that routes a request |
| Product data | Provides the content | Controlled records with provenance and update history |
| Permissions | Restricts protected content | Public repair guidance and authenticated authority access |
The familiar phone scan is only one access route. Business systems also need machine-readable exchanges. A public page can present a readable view without exposing every field.
A DPP is more than a product webpage
An ordinary product page can change address, omit source evidence and disappear when a product is discontinued. A credible passport design addresses identity persistence, structured data, access rights, changes and continued availability. A QR code is an entry point; the underlying records and operating processes do the work.
Traceability can supply events such as manufacturing, repair and reuse. It is related to the passport, but a passport is not necessarily a complete chain-of-custody ledger. Avoid collecting every supply-chain event before you know the actual information need.
An example to make the distinction useful
Imagine a repairer scanning a product. The public view explains safe repair options. After authentication, an authorised user can retrieve a restricted technical record. Both views resolve to the same product identity. If a component changes, an approved update changes the relevant record while preserving the earlier evidence. This is an illustrative architecture, not a universal legal specification.
Start with the applicable rule
Before buying a platform, identify your product category, market and operator role. The ESPR sets a framework; battery passports have their own rules. Do not assume a field list from a demonstration applies to your products. Read the requirements guide before turning an example passport into a procurement specification.
Sources for this guide
- European Commission: Digital Product Passport
- ESPR — Regulation (EU) 2024/1781
- European Commission: DPP questions and answers
Reviewed 4 October 2026. Check the current legal text and applicable product measures before acting.