EU Digital Product Passport vs UNTP DPP: What Is the Difference and Can They Work Together?

The EU and UNTP both use the phrase “Digital Product Passport”, but they are describing different layers. One is a legal information system created by European product law. The other is an emerging interoperability protocol for exchanging verifiable supply-chain credentials.

The short answer: same words, different jobs

The confusion starts because “DPP” sounds like one standard object. It is not.

In the EU, the DPP is part of a regulatory system. The Ecodesign for Sustainable Products Regulation establishes the framework, while product-group rules and other sector legislation determine the actual data obligation for a given product.

In UNTP, the DPP is one credential type inside a wider interoperability protocol. Its purpose is to make product information portable and machine-verifiable across supply chains and jurisdictions.

So the right comparison is not “Which DPP wins?” It is “Which layer is doing which job?”

EU DPP vs UNTP DPP

The table makes the central point visible: EU DPP is a regulatory outcome; UNTP DPP is an interoperability mechanism.

Who defines and requires each one

The EU DPP gets its authority from law. Under ESPR, the Commission can set product-specific DPP requirements through delegated acts. Sector laws can also establish their own passport requirements. The economic operator responsible for placing the product on the market has to satisfy the applicable legal requirements, not a generic industry interpretation of “DPP”.

UNTP has a different authority model. UN/CEFACT develops the protocol and its technical specification. An organisation can choose to issue or consume a UNTP credential because a trading partner, industry programme or interoperability architecture finds it useful.

That difference is why a UNTP credential cannot make an EU obligation disappear. A technically elegant credential is still only useful for EU compliance if its data, identifiers, access controls, availability and governance meet the actual EU requirements for the product in question.

For the UNTP architecture itself, see what the UN Transparency Protocol is and how it works.

Data, hosting and the EU Registry

The current EU architecture is decentralised in a specific way. The Commission's DPP Registry went live in July 2026. It registers identifiers and required metadata used by the EU system, while the product-passport data itself remains outside the central Registry.

That is not the same thing as saying “there is no central infrastructure”. There is a central Registry function. It simply does not become the universal database for every product field.

UNTP is also decentralised, but for a different reason. It is explicitly designed as a protocol over multiple platforms. Credentials can be held by issuers or service providers and discovered through identifiers and resolvers. There is no requirement to place every credential into one UNTP-owned database.

Those two decentralised models can coexist. An organisation might keep its governed product data in its own systems, publish a legally required EU DPP through its chosen service architecture and also issue a UNTP credential for cross-company exchange.

For the EU architecture in detail, use where Digital Product Passport data lives and the EU DPP Registry enrolment guide.

Identity and trust: eIDAS is not the same as DID

The identity difference is easy to miss because both systems use strong-sounding digital identity language.

For the current EU Registry, Commission Implementing Regulation (EU) 2026/1778 sets operator-verification methods rooted in Union trust and identity mechanisms. Those include qualified electronic signatures or seals, high-assurance electronic identification and qualifying electronic attestations under Union law.

UNTP uses W3C decentralised identifiers and an emerging Digital Identity Anchor pattern to connect digital identifiers with authoritative identity evidence.

These approaches can be mapped or connected in an implementation, but they are not legally interchangeable by default. Control of a DID does not, on its own, satisfy the current EU Registry verification rule. Equally, completing EU Registry identity verification does not automatically give an organisation the credential architecture needed for every UNTP exchange.

The underlying trust question is covered in what a verifiable credential actually proves.

How UNTP can feed an EU DPP

The most useful relationship is upstream interoperability.

Imagine a manufacturer receives conformity evidence, facility information and traceability events from several suppliers. Without a common exchange model, every supplier connection can become a bespoke integration. UNTP offers a way for those upstream parties to issue structured credentials that the manufacturer can verify and map into its governed product record.

That product record can then feed the EU DPP output required for the relevant product group.

A practical flow looks like this:

1. A supplier or assessment body issues a credential containing a defined product, facility or conformity claim.
2. The receiving business verifies the credential and evaluates whether the issuer and evidence are acceptable for its purpose.
3. Accepted facts are mapped into the business's governed product record with provenance and granularity intact.
4. The EU DPP publishing process selects the fields, identifiers and access treatment required by the applicable EU rules.
5. The responsible economic operator completes the EU Registry and publication steps required for that product.

In that model, UNTP is useful because it reduces translation friction before the EU DPP is assembled. It does not become the law or the compliance decision.

What UNTP cannot replace

A UNTP DPP cannot replace the parts of the EU system that get their authority from EU law.

It cannot, by itself:

• decide whether a product is in scope of an EU DPP obligation
• define the legally required product data or granularity
• create the statutory access-right matrix for a product group
• verify an economic operator for the EU Registry under the current legal method
• complete EU Registry registration requirements
• turn an unsupported product claim into compliant evidence
• prove that the physical product carrying a code is authentic
• guarantee that a product satisfies every applicable EU conformity requirement.

The EU Registry also performs specified automated technical, semantic and coherence checks. Passing those checks is not a universal truth test for every product claim. The legal and evidential responsibility remains wider than successful data submission.

For the current European horizontal standards position, use the DPP standards status page rather than treating UNTP as the owner of that question.

A practical architecture for supporting both

Businesses do not need to choose one master “passport format” and force every system around it.

A stronger architecture has a governed internal record at the centre:

Source systems and evidence → governed product record → channel-specific outputs

The internal record decides which fact is current, what evidence supports it, where it came from and at what level it applies. From there, the business can generate:

• the EU DPP presentation and data services required for a regulated product
• UNTP credentials for partners that use the protocol
• retailer, marketplace or customer feeds
• internal compliance and evidence views.

This keeps the legal obligation and the interoperability protocol in their proper places. It also avoids a common failure mode: making an emerging exchange profile the only place where the business knows what is true about its own product.

What would change this page

The comparison should be rechecked when product-specific EU DPP delegated acts establish more detailed mandatory schemas or access requirements, when the EU Registry identity or technical rules change or when UN/CEFACT publishes a stable UNTP release with stronger conformance and production evidence.

None of those changes would erase the basic law-versus-protocol distinction, but they could make the integration between the two more specific.

Sources

• Regulation (EU) 2024/1781, Ecodesign for Sustainable Products Regulation, EUR-Lex
  EU law
• Commission Implementing Regulation (EU) 2026/1778, EUR-Lex
  Delegated act
• Digital Product Passport Registry now live, European Commission
  European Commission
• UNTP Digital Product Passport specification, UNECE / UN/CEFACT
• UNTP Documentation Versions, UNECE / UN/CEFACT
• UNTP Technical Specifications, UNECE / UN/CEFACT
• UNTP Digital Identity Anchor, UNECE / UN/CEFACT
• Decentralized Identifiers (DIDs) v1.0, W3C