.jpeg)
%201.png){kind=logo}
Create your digital product passports in no time and with minimal effort.
The European Commission switched on the EU's central Digital Product Passport Registry on 19 July 2026, together with a testing environment and the first User Guidelines. This is the piece of infrastructure Article 13 of the Ecodesign for Sustainable Products Regulation (Regulation (EU) 2024/1781) requires the Commission to build: a public index that records every registered passport and confirms it exists. It does not replace your own DPP hosting, and it does not make DPPs mandatory today. Here is what actually changed, and what to do about it.
What the Registry does, and what it does not do
The Registry is an index, not a database. When a company registers a product's passport, the Registry stores a pointer: the product identifier, a link to the economic operator, and a proof of registration. The actual passport data, material composition, repair instructions, carbon footprint, stays where it always lived, hosted by the manufacturer or its DPP service provider. That is a deliberate design choice under the ESPR: data sovereignty stays with the company that generated the data, and the Registry only attests that a valid, standards compliant passport was registered for a given product.
Alongside the Registry, the Commission also launched a dedicated Digital Product Passport web page on 17 July 2026, consolidating guidance, timelines, and FAQs for businesses and authorities in one place. Treat both launches as one signal: the DPP program is moving from legislation into operating infrastructure.
Does the Registry going live mean DPPs are mandatory now?
No. The Registry being operational and a product category being obligated to carry a DPP are two separate things. The obligation still follows the ESPR's delegated act schedule, category by category. Batteries are first, with a mandatory passport from 18 February 2027. Textiles, electronics, and other categories follow on their own dates as their delegated acts land. Full breakdown in our DPP timeline.
What the 19 July milestone did activate immediately: the ban on destroying unsold apparel and footwear for large companies, under Article 25 and Annex VII of the ESPR. That obligation runs independently of the passport requirement and applies now.
How registration will actually work
Each DPP gets registered with the central Registry through a standard compliant API, not a manual upload form. That connection now has a technical foundation: Commission Implementing Decision 2026/1736, published two days before the Registry launch, sets out the harmonised standards for data exchange protocols, unique identifiers, and the API itself. A passport built to those standards is presumed to meet the ESPR's registration requirements, which is exactly the kind of certainty that was missing while the standards were still in draft.
| Date | Milestone |
|---|---|
| 14 July 2026 | Harmonised DPP standards adopted by the Commission |
| 15 July 2026 | Standards published, Implementing Decision 2026/1736 enters into force |
| 17 July 2026 | New Commission DPP web page launched |
| 19 to 20 July 2026 | Central DPP Registry, testing environment, and User Guidelines go live |
| 18 February 2027 | First category obligation: battery passports mandatory |
What manufacturers should actually do this quarter
Nothing about the Registry launch creates an urgent task for most manufacturers today, unless you sell batteries in scope. Three things are worth doing now rather than waiting for your category's delegated act:
- Use the testing environment. If you already have a pilot passport running, this is the first point where you can test the registration flow against a real Commission system instead of guessing at the spec.
- Check your identifier strategy. The Registry indexes by unique product identifier, and GS1 Digital Link is emerging as the practical carrier standard. If your SKUs already carry GTINs, you are in good shape. See our GS1 Digital Link comparison for the platforms that support it today.
- Decide build or buy before your category's delegated act lands, not after. Registration, API compliance, and ongoing standards tracking are exactly the kind of maintenance burden that tips the decision toward a platform. We laid out the real cost comparison in DPP: build vs buy.
dpp.cloud tracks the Registry API and the harmonised standards on your behalf, so a passport built on our platform registers without your team writing a line of integration code. If your product data already lives in a PIM, implementation runs two to three weeks. See how that works in creating a DPP from PIM data.
Next step
If you want to know where your product data stands against the Registry's identifier and registration requirements, book a 30-minute strategy session. We will map your current data against what the Registry expects and give you a realistic timeline.
