EU DPP Registry: How to Register a Digital Product Passport

The new EU DPP Registry is live — with one important limitation

Since 20 July 2026, companies can access the European Commission’s official DPP Registry, sign in through EU Login and verify their organisation. The EU has also published a 51-page guide for economic operators.

The Registry launch is also not a new blanket compliance deadline for every company. Whether and when a Digital Product Passport (DPP) must be registered depends on the relevant product group and applicable EU law. See the overview of DPP product groups and timelines.

What is the DPP Registry — and what is it not?

The EU Registry is the central index in a decentralised DPP architecture. It does not store the complete product, sustainability and compliance dataset. That information remains with the responsible economic operator or an appointed DPP software and hosting provider. The Registry instead stores identifiers, registration data, metadata and references that allow authorities and technical systems to locate and verify the correct passport.

Who must register a Digital Product Passport?

Under the new implementing regulation, registration is generally performed by the verified economic operator placing the covered product on the EU market or putting it into service. Depending on the applicable product law and market role, this may be a manufacturer, authorised representative, importer, distributor, dealer or fulfilment service provider. The key question is not who prints the QR code, but who is legally responsible for the product and its DPP.

The obligation only arises once the relevant EU law for the product group requires a DPP and its registration. The implementing regulation covers products under ESPR measures, batteries, construction products, toys, detergents and surfactants, and future EU passport regimes.

Where EU law permits representation, a verified third party may act on the economic operator’s behalf. Responsibility for product data and compliance does not disappear. Define roles and approvals early in your DPP implementation roadmap.

Prerequisites before registration

• EU Login for the person operating the Registry
• Legal organisation data and a reliable business identifier
• Name and email of the legal representative
• QSeal for legal persons or QES for natural persons/sole traders
• Completed and hosted DPP under the applicable product-specific data model
• Unique Product Identifier (UPI) resolving to the DPP over HTTPS
• Correct granularity: model, batch or item
• Model and batch identifiers where required for item- or batch-level passports
• Commodity code and DPP backup reference where applicable
• Ownership for updates, availability and error resolution

If the data model is not ready, start with a DPP example structure and template, then validate mandatory fields against the product-specific legal act and semantic repository.

Step 1: Create an EU Login and open the Registry

The DPP Registry uses the EU’s central authentication service. Existing EU Login users can sign in directly. Otherwise, use the EU Login registration page. After confirming the email, the production Registry redirects to authentication and then to the welcome page.

Step 2: Enrol a company or sole trader

Select “Enrol New Organisation” and indicate whether the economic operator is a legal or natural person. This choice determines the fields, accepted identifiers and verification route.

Legal person

• Registered legal name, not merely a trading name
• Official registered address and country of registration
• Preferably a National Trade Register number (NTR); alternatively LEI, VAT, eID or local identifier
• Non-public compliance email and telephone number for authority contact

Natural person / sole trader

• First and last name plus official address
• Preferably tax identification number (TIN); alternatively personal number, eID, identity card, passport or local identifier
• Compliance email and telephone number

The EU says these contact details are not displayed publicly. Review every value carefully: changing organisation data after verification begins restarts the process.

Step 3: Verify the organisation with QSeal or QES

Only verified economic operators may register DPPs and manage existing records. The applicant does not have to be the legal representative, so the form asks for the name and email of the person who will actually sign or seal the declaration.

1. Enter the legal representative’s details.
2. Request the European Commission-sealed PDF declaration.
3. Download the Commission-sealed PDF without modifying it.
4. Legal person: countersign with a qualified electronic seal (QSeal).
5. Natural person/sole trader: sign with a qualified electronic signature (QES).
6. Upload the same PDF and select “Verify your Organisation”.
7. Review status in the Activity Dashboard; SUCCESS makes the applicant organisation administrator.

QES and QSeal must come from a qualified trust service provider. Use the official eIDAS Trusted List to find one. The PDF declaration is currently available only in English.

Step 4: Create, host and expose the Digital Product Passport

The organisation may now register, but the DPP itself is still created outside the EU Registry. It must contain the data required by the product-specific legal act and its data model. The economic operator or an appointed DPP service provider stores and maintains that content throughout the lifecycle.

The Unique Product Identifier (UPI) connects the Registry, data carrier and passport. It must resolve persistently and securely over HTTPS to the DPP data. In practice, a QR code alone is not a DPP, and a Registry entry does not replace hosting or data maintenance. Align the technical implementation with DPP requirements and timelines and the published semantic model for the product group.

When is a DPP publicly available?

Publicly available does not mean that every field is open. The data carrier or UPI must make the passport reliably accessible. Product-specific law determines which fields consumers see, which are limited to market surveillance or customs, and which actors may add updates. The Registry is the index; role-based delivery remains part of the DPP solution.

For the technical connection between UPI, carrier and hosted passport, the guide to Digital Product Passport QR codes and GS1 Digital Link explains direct URIs, resolvers and access rights.

Step 5: Register by form, file or API

Once the semantic model for the relevant product group is enabled and the DPP is ready, select “DPP Registration” from the side menu. The Registry provides three routes:

Granularity: model, batch or item

Granularity is not a convenience choice. The applicable legal act determines whether the passport exists at model, batch or individual item level. If several rules require different levels for the same product, the implementing regulation requires the most granular level.

• Model: one DPP for products sharing the relevant specifications.
• Batch: one DPP for a defined production run; link the model identifier where it exists.
• Item: one DPP for an individual unit; link model and batch identifiers where those levels exist.

What the Registry validates and what proof you receive

After submission, the Commission automatically reads the accessible DPP data and checks its structure, semantic conformity, mandatory values, granularity and, where relevant, commodity code and backup reference. This does not validate the substantive truth of every claim; that remains the responsibility of the economic operator and market surveillance.

After successful validation, the Registry generates a unique persistent registration identifier and returns it through the same channel, interface or API. The economic operator may also generate electronic proof of registration for one or more DPPs. It contains the UPI, commodity code where relevant, responsible operator, timestamp and hash of the registered DPP version. It is protected by a qualified electronic seal and remains available for 90 days after generation; it can be regenerated later.

Common verification and DPP registration errors

The Activity Dashboard shows PROCESSING, SUCCESS or FAILURE. Detail reports can be reviewed, and registration errors exported as CSV. Build the same traceability into your DPP software and operating architecture so correlation IDs, submissions, versions and corrections remain auditable.

What companies should do now

1. Use the EU test Registry with a separate EU Login to rehearse organisation and registration workflows.
2. Obtain QSeal or QES early and designate the responsible person.
3. Map relevant product groups and timelines to the product portfolio.
4. Define UPI, model, batch and item identifiers consistently.
5. Prepare the DPP data model, hosting and update process using the implementation roadmap.
6. Test manual registration for pilot volumes and plan API integration for scale.
7. Integrate proofs of registration, versions and error reports into compliance processes.

The authoritative reference remains the Implementing Regulation (EU) 2026/1778, the EU user guide v1.0 and the applicable product-specific legislation. The European Commission information page brings together the Registry, test environment, guide and help desk.