Regulation · DPP Registry

EU Digital Product Passport Registry: what it is and how it works

Article 13 of the ESPR regulation (EU) 2024/1781 requires the European Commission to set up a digital registry storing the unique identifier of every Digital Product Passport placed on the EU market. The Registry, its testing environment and the operator guidelines have been live since 20 July 2026.

Architecture

A decentralised registry, not a central product database

The Registry doesn’t host DPP content. It stores the unique identifier of every passport, customs codes for imported products, and verification logs — while the actual product data stays hosted by the manufacturer or chosen service provider, accessible via the data carrier (QR, NFC or RFID) attached to the physical product. It’s the same principle MyLime already uses to separate public on-chain hashes from product data held on European servers.

How it works

The registration flow

  1. 01

    The operator submits DPP data via the Registry’s API or the Commission’s secure interface.

  2. 02

    The system checks the semantic conformity of the data and the declared granularity level — model, batch or single item.

  3. 03

    For imported products, the associated customs code is also validated.

  4. 04

    The system checks the link to the passport data, hosted outside the Registry.

  5. 05

    Once checks pass, a unique registration identifier is issued for the product.

Description based on information published by the European Commission on the Registry’s architecture; operational details (interfaces, formats, onboarding timelines) may evolve — always refer to the latest official guidelines.

FAQ

Frequently asked questions about the EU Registry

Does the EU Registry replace my Digital Product Passport?
No. The architecture is deliberately decentralised: the Registry only stores the unique identifier of each DPP (plus customs codes for imported products), not the full data. The actual data stays hosted by the manufacturer or their chosen service provider — in MyLime’s case, on our European servers — and is accessible via the product’s data carrier (QR, NFC or RFID).
Do I need to register even if my industry doesn’t have a delegated act yet?
No. The registration obligation starts once the delegated act for your product group becomes applicable. Until then, the DPP — and registration — remains voluntary. See the ESPR guide for expected dates by product group.
What does the Commission check before issuing a registration identifier?
Based on information published by the Commission, the system verifies the semantic conformity of the submitted data, the correct granularity level (model, batch or single item), the validity of the customs code for imported products, and the link to the passport data hosted elsewhere, before issuing a unique registration identifier.
Since when has the Registry been active?
Article 13 of the ESPR (EU) 2024/1781 requires the Commission to set it up by 19 July 2026. The Registry, testing environment and operator guidelines have been live since 20 July 2026.
How does MyLime fit into this?
MyLime already structures DPP data in a way that’s compatible with the Registry’s decentralised architecture: a unique identifier per product, full data hosted on MyLime’s infrastructure, access via QR/NFC. Direct submission to the Registry follows your industry’s delegated act timeline — talk to the team to understand what applies to your specific case.

Get ready to register

Structure your data to be ready for the EU Registry.

A free 15-minute call with our team to understand how to connect your DPP to the Registry once your industry becomes obligated.

Book a free call →