In most organisations, the Digital Product Passport arrives through the compliance or sustainability team, and digital product identity arrives through brand protection, supply chain or digital. They’re scoped separately, budgeted separately, and often bought from different vendors. Both teams then put something on the product, and both build a record of it.
The two are related but not the same. The passport is a regulated output: a defined set of information that must be accessible to defined audiences. Product identity is infrastructure: the identifier, carrier and record that a passport can be served from, and that also supports authentication, traceability and ownership. This comparison sets out where they overlap, where they differ, and how to sequence them.
The distinction matters most for premium goods. Clothing, footwear and leather goods accounted for 62% of seized counterfeits in the most recent OECD/EUIPO study, and fashion is among the first product groups in the EU’s passport working plan. For those brands, a passport that can’t prove authenticity solves half the problem on the same products.
Side by side
The simplest way to hold the difference: the passport answers questions about the product, and identity answers questions about the item. ‘What is this jacket made of, and how do I repair it?’ is a passport question. The answer is the same for every jacket of that model. ‘Is this jacket genuine, where was it sold, and who owned it before me?’ is an identity question. The answer is different for every single unit.
Both rely on something physical on the product that a phone can read, which is why they’re so often confused. But they were designed for different purposes, by different people, and they’re judged on different outcomes.
| Digital product identity | Digital Product Passport | |
|---|---|---|
| What it is | Infrastructure: identifier, carrier, record | A regulated information set and access model |
| Driven by | Business need: protection, traceability, engagement | ESPR and product-specific EU regulation |
| Granularity | Usually item-level | Model, batch or item, set per product group |
| Must prove authenticity? | Yes, if built for authentication | Not required |
| Records events after sale? | Yes: scans, transfers, resale | Not required beyond specified updates |
| Audience | Brand, partners, consumers, resellers | Consumers, authorities, recyclers, repairers |
| Deadline | None. Starts when you need it | Set by delegated acts per product group |
Where they overlap
Both need a unique identifier, a data carrier on the product, and a record that can be resolved from that carrier. That shared core is why a brand with product identity in place is most of the way to a passport: the passport becomes a view on data the brand already holds, with access rights attached.
In 2026 the EU recognised NFC as a compliant DPP data carrier (Implementing Decision (EU) 2026/1736, referencing EN 18220). An NFC tag deployed for authentication can therefore carry the passport link as well. One tag, one identity, two uses.
The overlap is also where cost sits. The carrier is the most expensive per-unit element, and application on the line is the most disruptive. Doing either twice, once for the passport and once for identity, is where separate projects waste money.
In practice the overlap plays out at the moment of the scan. A consumer taps or photographs the code on a product. The same address can open a page with materials, care and repair information (the passport view), confirm that the item is genuine (the identity view), and offer registration or ownership transfer. Which of these appears, and to whom, is decided by the platform behind the identifier, not by printing different codes for different purposes.
A repairer scanning the same item years later can see disassembly guidance and the item’s own service history. A market surveillance officer can see compliance information that isn’t public. The brand’s own teams see everything. One identity, several audiences, each with the access the regulation and the brand allow.
