The EU DPP Registry Is Live: What Economic Operators Need to Know

The European Commission's production Digital Product Passport Registry is now accessible, and economic operators can enrol their organisations. The Commission has published a dedicated official DPP Registry page with access to the production service, a separate testing environment and a detailed user guide.

This is an important operational milestone for the EU's Digital Product Passport infrastructure. It is also a moment for precision: the Registry is live, but DPP obligations and product registration are being introduced progressively by product group and applicable legislation.

What the DPP Registry does

The Registry is the EU-level indexing service for Digital Product Passports linked to products placed on the EU market. It stores unique identifiers, registration data and high-level metadata needed to identify, find and validate a passport. It will also support customs and market-surveillance authorities in checking registered DPPs.

The Registry does not store the full product passport. Detailed product, sustainability and compliance data remains in a decentralised system controlled by the responsible economic operator, or by a DPP service provider acting for it. The economic operator remains responsible for keeping that data accurate, available and updated throughout the passport's lifecycle.

Registry record versus full DPP

Registry record: the EU-level reference containing identifiers, registration metadata and the location of the passport.
Full DPP: the product-specific dataset hosted and maintained by the economic operator or its chosen service provider.
Connection between them: a Unique Product Identifier must resolve to the location where the full DPP data is hosted.

What is available now

Economic operators can access the production Registry using EU Login and begin the guided organisation-enrolment process. The Commission also provides a separate test environment where teams can explore enrolment and registration workflows without affecting production data.

Important: “live” does not mean every product passport can be successfully registered today. The Commission's operator guide states that DPP registration will be introduced progressively. Its 28 July 2026 edition says successful battery DPP registration is not yet available because the battery semantic catalogue is still being defined.

Companies should therefore separate two questions: whether they can enrol and verify their organisation now, and when the law and Registry are ready for their specific product group. The applicable EU legislation determines which products require a DPP, the required dataset, passport granularity and the date by which registration must occur.

How organisation enrolment works

Create or use an EU Login. Registry authentication is handled through the European Commission's EU Login service.
Enter the economic operator's legal details. The guided form supports both legal persons and natural persons and requests identification, address and compliance-contact information.
Verify the organisation. The Registry creates a Commission-sealed PDF declaration. A legal representative must sign or seal it with the appropriate qualified electronic signature or qualified electronic seal before it is uploaded.
Wait for verification. Only verified economic operators can register and manage DPPs. The user completing successful verification becomes the organisation administrator in the Registry.

Teams should confirm early who is legally authorised to represent the organisation and whether the required qualified signing or sealing certificate is ready. Those practical details can become a critical-path dependency.

What companies should prepare next

Assign Registry ownership. Name the team responsible for EU Login access, organisation verification, administrator continuity and support requests.
Validate legal identity data. Reconcile the organisation's registered name, address, official identifier and compliance contacts with the information in its qualified certificate.
Define the identifier and hosting model. Decide how Unique Product Identifiers will resolve reliably to DPP data and who will operate that hosting over the required lifecycle.
Keep the Registry record and DPP dataset separate. Build workflows that publish the minimal registration data to the EU service while maintaining the full, versioned passport in the company's governed data environment.
Use the testing environment. Rehearse enrolment, submission and error-handling processes without assuming that test records will migrate to production—they will not.
Track product-group readiness. Monitor the applicable delegated act or sector legislation and the Commission's official Registry updates before planning production registrations.

Why this matters

The launch moves DPP preparation from architecture alone into operational readiness. Legal identity, qualified signatures, administrator roles, identifiers, resolvable hosting and registration-quality data now need clear owners. Companies that test these workflows before a product-specific deadline will be better placed to avoid last-minute verification and data-validation problems.

Official EU links

Regulatory disclaimer. This article is general information, not legal advice. DPP requirements and Registry functionality are product-specific and continue to develop. Confirm the current Commission guidance, applicable legislation, product scope, operator role and implementation dates for your products.