The EU Digital Product Passport Registry Is Live: What It Is and What It Stores

Almost everything written about the EU Digital Product Passport focuses on product deadlines: batteries in February 2027, iron and steel and textiles after that. But none of those deadlines work without a single piece of shared infrastructure underneath them: a central registry. Article 13 of the Ecodesign for Sustainable Products Regulation (ESPR) required the European Commission to have it operational by 19 July 2026, and it opened on 20 July 2026, together with a testing environment.

Updated 23 September 2026. This article was written before the launch. It now reflects the registry going live on 20 July 2026 and the rules for using it, Implementing Regulation (EU) 2026/1778, in force since 6 August 2026.

The registry is the lookup backbone of the entire DPP system, the thing that connects a physical product to its digital passport and lets a regulator, a customs officer, or a recycler find the right data from a scanned code. It is not, by itself, a mandate on any specific product. It is the rail the product-specific mandates run on.

This article explains what the registry is, what it actually stores, how a lookup and a customs check work, what changed when it went live, and what it means for manufacturers. If you already understand the registry and want the practical sequence for getting your data ready, skip ahead to our guide to preparing product data for the DPP registry.

What the EU DPP Registry Actually Is

The most common misconception is that the registry is a giant database holding every product's passport data. It isn't. The registry is an index: a directory that points to where each passport lives, not a store of the passports themselves.

The DPP system is deliberately decentralized. Manufacturers (or the certified service providers they appoint) host the actual passport data in their own systems. The Commission's registry holds only the minimum needed to find a passport and confirm it exists. That design keeps the EU out of the business of hosting commercial product data, and it means the registry can stay small and fast while passport content scales across millions of products.

What the Registry Stores

Under Article 13, the registry securely stores a small set of identifiers for every product that carries a passport, plus a commodity code for goods crossing the EU border:

Notice what is not on that list: chemical composition, carbon footprint, test results, declarations. None of your real product data goes into the registry. It goes into the passport you host; the registry just knows where to find it.

How a Passport Lookup Works

Every passport begins with a unique product identifier, in practice a GS1 GTIN built on ISO/IEC 15459, encoded in a data carrier physically present on the product, its packaging, or its documentation. QR codes are the expected primary carrier; NFC and RFID also qualify.

The carrier uses GS1 Digital Link, a URI syntax that embeds the identifier in a web URL. When someone scans it, a resolver service uses the registry to direct them to the correct passport, and can return different views to different audiences from the same code. A consumer sees recycling and care information; a regulator sees compliance data; a recycler sees disassembly and material data. Those access rights are set per product group in the ESPR delegated acts. The Commission will also run a public web portal where stakeholders can search and compare passport data within their access rights.

The standards that formalize which identifiers and data structures are valid in the EU system were developed with CEN-CENELEC. Eight harmonised standards underpin the system's interoperability, and when the registry launched the Commission reported six of them published, covering unique identifiers, interoperability, data carriers, APIs, data exchange protocols and data storage.

The Customs Connection: Why the Registry Has Teeth

The registry isn't a passive lookup tool. It is wired into EU border control through the EU Single Window Environment for Customs. When a product subject to a DPP requirement is declared for release into free circulation, its registration identifier must be provided, and customs and market surveillance authorities can electronically verify that the identifier exists in the registry and matches the declared goods.

The practical consequence: for an in-scope product, a missing or mismatched registry entry is not a paperwork footnote. It is a reason a shipment can be held at the border. That is what turns the registry from infrastructure into an enforcement lever, and it is why getting identifiers and structured data right ahead of each product deadline matters.

It Is Live. What Happens Next

The registry opened on 20 July 2026, and Implementing Regulation (EU) 2026/1778, which sets the rules for access, operator verification and registering identifiers, entered into force on 6 August 2026. Registration runs through a user interface or an API, and an economic operator can request a proof of registration to show a business customer. These are milestones for the infrastructure; neither, on its own, makes a passport mandatory for any product. The product-specific obligations follow on their own timelines, and each one relies on the registry being in place first:

Batteries are the forcing function: the battery passport becomes mandatory in February 2027, making it the first DPP that has to resolve through the registry. Iron and steel are first-wave ESPR products, with a delegated act the Commission indicates for adoption in Q4 2026, and construction products follow under the revised CPR. A minimum 18-month transition applies between a delegated act's adoption and its obligations taking effect, so the registry is in place well before most product passports are due.

Where the Real Work Sits: Preparing the Data

The registry indexes where a passport lives; it assumes you arrive with the passport content already structured. That is where most manufacturers are least ready: a passport needs your spec sheets, mill certificates, and test reports turned into clean, machine-readable, auditable fields, and today that data is almost always trapped in PDFs and DOCX files.

Closing that gap is the layer SpecMake occupies. SpecMake is the data preparation layer for DPP: it extracts, audits and structures the fields a passport needs, as JSON-LD ready to map into the DPP platform you choose. Pair it with that platform for hosting, data carriers, and registry submission.

What This Means for Manufacturers

The registry going live did not make a product passport due for anyone. The first deadline it serves is 18 February 2027, for certain large batteries. What you should be doing now is the groundwork that every in-scope product will need: secure GS1 identifiers, and get the data that will populate your passports out of unstructured documents and into a structured, machine-readable, auditable format. Both take longer than teams expect, and both are independent of which exact month your product's delegated act lands.

Our five-step guide to preparing product data for the DPP registry walks through the full sequence. The fastest way to see where your own documentation stands is to run a DPP readiness check. Upload a spec sheet and see which DPP fields you already have and what's missing, in under a minute and with no account needed.

Key Dates

The registry indexes where your passport lives; SpecMake gets your product data ready to live there. Run a DPP readiness check on one of your spec sheets, or read the broader overview of Digital Product Passports and technical documentation.