Digital Product Passport Registry — What the Commission Published and What It Means

On 29 April 2026, the European Commission published the Draft Implementing Regulation for the EU Digital Product Passport (DPP) Registry, setting out the operational, technical, and governance framework for the registry required under the Ecodesign for Sustainable Products Regulation (ESPR). The public consultation closed on 27 May 2026.  The consultation page is available here.

What the Registry Actually Is
The architecture of the registry is one of the most important things to understand correctly, because it is frequently misread. The EU registry will not store product data. Its function is narrower and more specific: it will serve as a storage platform for two things only — a Unique Identifier assigned to each product, and a web address pointing to where the actual Digital Product Passport is hosted. The passport itself will be hosted and maintained by the manufacturer or a service provider of their choice. The EU registry is therefore an index, not a database of product information.

This distinction matters for anyone planning their DPP implementation. The compliance burden for data quality, data hosting, and data maintenance sits entirely with the manufacturer, not with the EU infrastructure. Companies will need to ensure that the web address registered with the EU registry remains live, accurate, and accessible for the product's entire lifecycle.

Why This Architecture Decision Matters
The decentralised model, where data hosting is the responsibility of the manufacturer and the EU registry holds only identifiers and pointers, has direct implications for how companies structure their product data systems. Organisations that build their product information infrastructure around a single, well-maintained data environment will find it easier to connect to this model than those relying on fragmented legacy systems across multiple platforms.

It also means that the EU registry itself will not be a single point of failure for product information access. If a manufacturer's hosted passport becomes unavailable, the identifier in the registry will remain, but the data behind it will not. Long-term data availability is therefore a manufacturer responsibility, not an EU infrastructure guarantee.

What Comes Next

The consultation has now closed. The Commission will review the feedback received and proceed to formal adoption of the Implementing Regulation. Once adopted, the registry will form the backbone of DPP compliance for all product categories brought into scope under ESPR delegated acts. The first delegated acts beyond batteries are expected to cover textiles and electronics, with further categories to follow on a rolling basis through the late 2020s.

Companies that have not yet mapped their exposure to ESPR and the DPP framework should treat the registry publication as a prompt to do so. The technical requirements are concrete: stable product identifiers, accessible data endpoints, and long-term hosting obligations. These need to be factored into product data strategies now, before the relevant delegated act for your product category enters into force.