The EU Digital Product Passport Registry is live — what it actually does
The registry went live on 20 July 2026. It is being widely misreported as a deadline for businesses. It is not — it was a deadline for the Commission.
The headline, correctly stated. On 20 July 2026 the European Commission launched the Digital Product Passport Registry and its testing environment. ESPR Article 13 required the Commission to set up the registry by 19 July 2026. That deadline was the Commission's, not yours. No merchant is required to register anything today.
What the registry actually stores
Article 13 is precise about this, and the precision matters: the registry "stores in a secure manner at least the unique identifiers". It stores identifiers, not passport content.
Concretely, it holds:
- Unique product identifiers, and unique operator and facility identifiers.
- The commodity code for goods entering under release for free circulation.
- Battery unique identifiers, explicitly cross-referenced to Article 77(3) of the Batteries Regulation.
The operator placing a product on the market uploads the identifier data, and the registry returns a unique registration identifier. Article 13 is explicit that this registration identifier is not proof of compliance — it confirms you registered, not that your passport is correct or complete.
Your actual passport data stays with you or your DPP service provider. There is no EU-hosted store of passport content, and this is a persistent misconception worth correcting whenever you meet it.
Why it exists: customs
The registry is best understood as a customs enforcement mechanism rather than a transparency one.
Article 15 requires anyone placing a covered product under release for free circulation to give customs the unique registration identifier. Customs release the goods only after verifying that the identifier and the commodity code match the registry. The registry is to be interconnected with EU CSW-CERTEX, the customs single window, within four years of the Article 13(5) implementing act entering into force.
That is the enforcement teeth. For a merchant importing goods, the practical consequence eventually is that unregistered products do not clear customs — a far more immediate constraint than any fine.
What launched on 20 July
- The registry itself, with both API and user-interface registration.
- A testing environment — genuinely useful, and the reason to look at this now rather than later.
- A free semantic repository of machine-readable data models, definitions and vocabulary. This is currently the best available reference for how the Commission expects passport data to be structured.
- Technical documentation, guidelines, webinars and a helpdesk.
Commission Implementing Regulation (EU) 2026/1778, adopted on 16 July 2026, sets the operating rules: who may register, eIDAS-verified operator identity, automated checks, proof of registration and retention.
When registration becomes mandatory for you
Product group by product group, as each delegated act applies. There is no general registration obligation and no single date.
The Commission's own announcement names the first hard deadline as 18 February 2027, for certain large battery types — consistent with the battery passport date in Article 77 of the Batteries Regulation. For everything else, registration follows your product group's delegated act, and no such act has been adopted for any group.
Watch for this misreporting. Several vendor and consultancy pages have presented 19 or 20 July 2026 as a business compliance deadline, some with urgency framing attached. It was the Commission's build deadline. If you receive a sales email telling you that you missed a DPP registration deadline this week, that is a false statement — and a reasonable signal about the vendor.
What a PrestaShop merchant should actually do
If you sell batteries
This is worth real attention now. 18 February 2027 is roughly seven months away, it is a firm statutory date, and the registry is the mechanism. Use the testing environment to understand the registration flow, and establish who in your supply chain will be doing the registering — if you import batteries yourself, it is likely to be you. See batteries.
If you sell anything else
Read the semantic repository. It costs nothing, and it is the clearest signal available about the data structures the Commission expects — considerably more informative than any vendor's data model. If you are designing passport storage in PrestaShop, aligning your schema to it now is cheap; doing so after you have loaded data is not.
Everyone
Note that the registry's existence does not change what your passport must contain. That still comes from a delegated act that, for every product group other than batteries, does not yet exist.
What is still missing
Two gaps worth tracking, because they affect architecture decisions:
- The Article 14 public web portal — for searching and comparing passport data — does not appear to have launched as a distinct service. The 20 July announcement describes the registry, not the comparison portal.
- The DPP service provider regime is not in place. Article 10(4) requires a back-up copy of your passport held by a service provider, and Article 11 empowers a delegated act setting requirements and a certification scheme for those providers. That act has not been adopted and is reportedly scheduled for 2027. So the back-up obligation currently exists without a certified provider regime behind it — which makes "we are a certified DPP service provider" a claim nobody can currently substantiate.
Questions
Do I have to register my products in the EU DPP Registry now?
Does the registry hold my passport data?
What is the registry actually for, then?
Is the semantic repository worth looking at now?
Sources
Keep reading
What is a DPP
The concept, in plain language — what it contains, how it is reached, and the four things people wrongly assume it is.
Required data fields
The fixed framework elements you can design against today, and the product-specific fields that do not exist yet.
QR codes & identifiers
What the standards actually permit, and the identifier decisions that are expensive to reverse.
Turn this into a plan for your catalogue
The readiness checklist walks your product groups one at a time and tells you what data to start collecting from suppliers now.