The EU DPP Registry: An Index, Not a Warehouse
One big misconception has grown up around the EU registry for Digital Product Passports (DPPs): that it will be a central database of all product data. It is not. This article explains what the registry really is and what that means for your company.
What the DPP registry is
The DPP registry is an EU indexing and verification layer. It holds product identifiers, related registration metadata and — where relevant — commodity codes. What it does not hold is the full content of passports.
You can compare it to a library catalogue: it tells you that an item exists and where to find it, but the content of the "book" itself stays elsewhere. This distinction is key to understanding the whole architecture.
Where the actual data lives
The actual passport data stays decentralised — with the economic operator or its DPP service provider. That is where the layers on composition, environment or traceability sit, the ones the data carrier on the product points to.
This split means the company keeps control of its data and how it is hosted. The registry merely confirms the identity and existence of a passport; it does not collect its content.
Why an index, not a warehouse
Decentralising the data is a deliberate design choice, not a temporary state. It has several practical reasons:
- reducing the risk of a single point of failure for the whole market,
- control by the economic operator over its own data,
- scalability — the registry need not carry the weight of full passports,
- technological flexibility on the side of companies and providers.
If all data flowed into one database, it would become both a bottleneck and a target for attacks. We expand on this comparison in Central registry versus decentralised data.
What the registry does in practice
The registry serves several functions that do not require storing full data. It lets you verify that a passport exists and is linked to the right operator. It also supports market-surveillance authorities and customs processes by providing a reference point for checks.
That is precisely why the registry connects to the EU customs Single Window. Border control is meant to be risk- and system-driven, not mass scanning of QR codes at the border.
When the registry goes live
The registry framework is being introduced gradually. The production environment is expected from mid-2026, together with the entry into force of the relevant implementing rules. It is worth verifying exact dates at the source, because the rollout is spread over time.
For companies this means registration will become part of placing a product on the market — alongside building the passport itself.
What this means for your company
Because the data stays on your side, its hosting, continuity and exportability become critical. The registry does not remove responsibility for the passport's content — that stays with the manufacturer or importer.
So it is worth choosing solutions that ensure data portability and backups. We cover this in Backups and continuity of DPP data.
What the registry verifies, and what it does not
Verification in the registry is often misunderstood. It is not an assessment of quality or a certification of the passport's content. It is an identity and access check — confirming that an operator is who it claims to be and that a passport is linked to it.
The accuracy and completeness of the data itself remain the economic operator's responsibility. The registry does not "approve" a passport on the merits, so a registry entry does not remove responsibility for the content.
The registry and EPREL: two different registries
It is worth not confusing the DPP registry with the existing EPREL database for energy labels. EPREL holds full records within its scope, whereas the DPP registry stays an index of identifiers and metadata.
These are two distinct tools with different roles. Work is under way to link such registries and reduce double reporting, but that does not change the basic difference: the DPP does not gather full data in one place.
The registry and border checks
Linking the registry to the EU customs Single Window has a practical purpose: to enable risk-driven checks. Instead of mass scanning of codes at the border, systems can flag cases that need attention.
For an importer this means consistency between the passport, the registry and the customs declaration becomes important. Inconsistencies can raise the risk of goods being held for clarification.
Common misconceptions about the registry
A few myths circulate around the registry:
- that it is a central database of all product data — it is not,
- that a registry entry confirms passport quality — it confirms identity,
- that the registry will keep your data if you lose it — it will not,
- that registration replaces the duty to maintain the data — it does not.
Clearing up these misconceptions makes it easier to plan your own duties around the passport.
Key takeaways
- The EU DPP registry is an index and verification layer, not a central store of full passports.
- It holds identifiers and metadata; the actual data stays decentralised.
- Decentralisation is a deliberate choice that limits the risk of a single point of failure.
- The registry connects to the EU customs Single Window, supporting risk-driven checks.
- The production environment is expected from mid-2026.
See how CyfroPass builds the passport and prepares your data for registration in the EU DPP registry. Visit cyfropass.pl and keep control of your data.