What Is the EU DPP Registry? (And What It Isn't)
The EU's central DPP Registry is now operational. It's an index, not a database — and it doesn't make passports mandatory. What it actually is, and what changes now.
As of 19 July 2026, the European Commission’s central Digital Product Passport Registry is required to be operational — the deadline set by Article 13 of the Ecodesign for Sustainable Products Regulation (ESPR, 2024/1781). If you’ve seen headlines suggesting this means Digital Product Passports are now mandatory, they’re wrong in a specific and important way, and the distinction matters for anyone planning compliance work.
The short definition
The EU DPP Registry is a central index maintained by the European Commission that stores unique product identifiers and registration data for Digital Product Passports. Given a product’s identifier, the registry returns where that product’s passport data can be found. It does not host the passport data itself, and its launch does not make passports mandatory for any product category.
What the registry is not
It’s not a giant EU database of product data. The passport data itself stays with economic operators and their service providers. The registry is a directory — it resolves an identifier to a location, the way a phone book maps a name to a number without containing the conversation.
Its launch is not a compliance deadline. A product needs a DPP only when a product-specific delegated act or sector law requires it. As of the registry’s launch, no ESPR product-specific delegated act is yet in force — the only fixed statutory passport date is batteries, on 18 February 2027, under the Battery Regulation. Textiles, electronics, and other categories follow later, on their own timelines.
It doesn’t do the hard work for you. The registry accepts identifiers and registration data. Producing a defensible passport — resolved product identity, complete structured attributes, evidence behind every claim — remains entirely the operator’s problem.
What actually changes now
The infrastructure switch-on matters for one practical reason: the machinery the first passports will run through now exists, and the battery deadline is the next fixed milestone. For distributors and manufacturers with battery-containing products, the seven months between registry launch and passport obligation is the window in which catalog data either gets passport-ready or doesn’t.
And “passport-ready” is a data condition, not a software purchase: one resolved identity per product (a registry entry pointing at a passport built on a duplicated record is a liability), machine-readable structured attributes rather than PDF datasheets, and evidence traceable to a source for every claim the passport makes. The registry indexes the passport. Everything that makes the passport defensible happens upstream, in your product data.
For the wider framework the registry sits inside, see what is a Digital Product Passport.
Battery-containing products in your catalog and a February 2027 deadline approaching? Book a 30-minute call.
Related reading
Glossary
What Is the EU Battery Passport?
The first fixed statutory Digital Product Passport deadline, and what battery teams need to prepare.
Glossary
What Is a Digital Product Passport?
The broader product-data framework that the EU DPP Registry supports.
FAQ
What is the EU DPP Registry?
A central index maintained by the European Commission, operational per the ESPR Article 13 deadline of 19 July 2026, that stores unique product identifiers and registration data for Digital Product Passports and resolves an identifier to the location of the passport data. It does not host the passport data itself.
Does the DPP Registry launch mean Digital Product Passports are now mandatory?
No. A product needs a DPP only when a product-specific delegated act or sector law requires it. The first fixed statutory passport date is for batteries, on 18 February 2027, under Regulation (EU) 2023/1542.
Claro
Stop maintaining this by hand
Claro keeps product and supplier data trusted as catalogs change — matching, deduplication, enrichment, and validated write-back into the systems you already run.
Book a demo