Four facts to remember
- The Registry launched on 20 July 2026 with a testing environment and technical resources.
- Each DPP subject to registration is connected to unique identifiers and associated metadata.
- Complete product data remains decentralised under the responsibility of economic operators and the services that expose it.
- Registration is available through a secure interface or API, with an electronic proof of registration available.
What is the EU DPP Registry?
The Registry is the infrastructure established under the Ecodesign for Sustainable Products Regulation to make the existence of a Digital Product Passport verifiable and to connect that passport to the required identifiers. Operational arrangements are set by Commission Implementing Regulation (EU) 2026/1778 of 16 July 2026, published in the Official Journal on 17 July.
The Commission describes it as secure infrastructure for registering unique product identifiers and associated metadata. It supports checks, access management and interoperability without becoming one central database containing every technical document, commercial detail or sustainability record for the product.
The decisive distinction
Registering a DPP does not mean uploading all passport data into the Registry. The business still needs a service that stores, exposes and updates complete information for the required period.
What goes into the Registry?
The exact registration dataset depends on the legal framework and product category. Operationally, the Registry manages information required to identify the passport, the operator and the registration. Complete data—such as composition, performance, documents, instructions, circularity information or restricted fields—remains in decentralised systems connected to the DPP.
| Registry layer | Decentralised DPP service |
|---|---|
| Unique identifiers and required registration metadata | Complete datasets defined by product legislation |
| Information supporting registration and access verification | Documents, evidence, versions and role-specific views |
| Registry architecture logs and functions | Collection, approval, publication and update workflows |
| Electronic proof of registration where requested | Service continuity and product-lifecycle availability |
Interface, API and proof of registration
The Commission identifies two registration routes: a secure user interface and an API. The user interface can support limited volumes and early testing; the API is important when a company registers many passports, integrates with business systems or needs to reduce manual activity.
An economic operator can also request proof of registration in the form of a secure electronic document. This evidence can become part of the product compliance file and B2B acceptance workflow.
What a business should prepare
- Identifiers. Decide whether the DPP identifies a model, batch or item as required and align product, operator and facility identifiers.
- Data carrier and resolution. Connect QR, NFC or another carrier to the correct identifier and a stable address.
- Decentralised dataset. Store complete data, enforce access rights and ensure availability, integrity and updates.
- Registration workflow. Define who prepares, checks, submits and reviews the registration result.
- Error management. Plan corrections, versions, withdrawal and reconciliation across systems.
- Evidence. Keep logs and registration proof with the product file.
How NexusDPP connects to the Registry
NexusDPP separates product-data governance from the Registry connector. A passport is built through category templates, supplier collection, controls, approvals, access levels and versions. The registration module uses approved identifiers, sends the required metadata and retains the transaction status and returned evidence.
This separation reduces the risk that a technical interface change forces a redesign of the entire data workflow. It also supports testing before registration becomes mandatory for the product category.
A live Registry does not create an immediate duty for every product
The Registry is a common component of the DPP system, but the obligation to create and register a passport depends on the legislation applying to the product category. The first fixed deadline highlighted by the Commission is 18 February 2027 for specified battery types. Other products will follow the dates and requirements set by the relevant acts.
Technical readiness should therefore be separated from the legal publication deadline. Testing identifiers, data, APIs and workflows now can reduce supply-chain pressure later.
Official sources
- European Commission — The Digital Product Passport Registry is now live20 July 2026 announcement covering the testing environment, APIs, proof of registration and decentralised model.
- Commission Implementing Regulation (EU) 2026/1778Implementation arrangements for the Digital Product Passport Registry.
- Regulation (EU) 2024/1781 — ESPRGeneral ecodesign and Digital Product Passport framework.
Information updated on 24 July 2026. Applicable duties must be checked against the product category and legislation in force.