EU DPP Registry: The Complete Operator Reference

The EU Digital Product Passport Registry went live on 20 July 2026. This page is a working reference for the people who have to operate it: how access works, what enrolment and verification actually demand, how registration is submitted, and what every error message means.

Everything below is taken from the European Commission’s DPP Registry User Guide for Economic Operators (version 1.01, published 28 July 2026), Commission Implementing Regulation (EU) 2026/1778, and Regulation (EU) 2024/1781. Where those documents do not answer a question, this page says so rather than estimating.

The one thing to know first: battery registration cannot yet succeed

The Registry is live and Batteries is the first product group in it. But the Commission’s own User Guide states, in section 6.2.1:

“Successful registration of DPPs for batteries is not currently available, as the semantic catalogue for this product group has not yet been defined. Currently, it is not possible to successfully register DPPs.”

Section 6.2.2 repeats the point, describing the semantic content for the product group as under development. A submission attempted today can return the validation error “Semantic validation failed due to its unavailability”.

Article 12 of Implementing Regulation (EU) 2026/1778 requires the Commission to establish and maintain a semantic repository. No completion date for the battery semantic catalogue appears in the User Guide, in that Regulation, or in the Commission’s launch announcement. Anyone quoting a date for it is not quoting a published source.

This does not mean there is nothing to do. Enrolment and organisation verification are open now and do not depend on the semantic catalogue. Verification is also the step with the longest external lead time, because it requires a qualified certificate from a third party.

Access

• Production Registry: registry.product-passport.ec.europa.eu
• Test environment: registry.acc.product-passport.ec.europa.eu
• Authentication is via EU Login, the central authentication service of the European institutions, which supports multifactor authentication. You are redirected to EU Login automatically and returned to the Registry’s Welcome page on success.

Enrolment and verification

Under Regulation (EU) 2024/1781, only verified economic operators may register and manage Digital Product Passports. Verification is not a form submission; it is an identity proof involving a qualified certificate.

The Commission locks the organisation data you enter into a PDF declaration and seals that document. You then countersign or counterseal it offline using a Qualified Electronic Signature or Qualified Electronic Seal from a Qualified Trust Service Provider, and upload it. The Registry checks the integrity, validity and authenticity of the file, the signature or seal, and the associated certificates.

The seven steps

1. Provide the legal representative’s information (first name, last name, email)
2. Request the sealed PDF declaration
3. Download the PDF declaration
4. Sign or seal the PDF declaration
5. Upload the signed or sealed declaration
6. Submit it
7. Check the status of the application in the Activity Dashboard

Certificate requirements

• Legal persons must use a Qualified Electronic Seal (QSeal). Natural persons must use a Qualified Electronic Signature (QES). Both are defined under eIDAS, Regulation (EU) No 910/2014.
• The seal must be embedded using one of the PAdES Baseline formats: B, T, LT or LTA. The User Guide states that other document formats or electronic signature containers shall not be accepted under the PDF-based verification procedure.
• The certificate Subject must contain organizationName (OID 2.5.4.10), countryName (OID 2.5.4.6) and organizationIdentifier (OID 2.5.4.97), and these must match what you entered on the organisation form.
• Exactly two signatures are expected on the submitted file: the Commission institutional seal and your countersignature or counterseal.
• After downloading the sealed declaration, the only permitted change is adding your signature or seal. Any other modification causes rejection.

Organisation identifiers

At enrolment you choose an identifier type. The accepted types are:

• LEI, the Legal Entity Identifier as specified in ISO 17442. Maximum 20 characters.
• VAT identification number, issued by national tax authorities. Maximum 15 characters.
• eID, the identifier associated with an electronic ID credential. Maximum 30 characters.
• Local definition, prefixed with a two-letter country code.

The identifier value itself has a maximum of 50 characters. Country of Registration is mandatory and determines the law governing the entity. On successful verification you become the Administrator of the organisation in the Registry, and the success report states the expiration day of your signature or seal.

Registration

Registration binds two identifiers. The Unique Product Identifier (UPI) is supplied by you: a URL-based identifier conforming to JTC 24 standards, maximum 50 characters, which must resolve to where your passport data is hosted. The Unique Registration Identifier (URI) is returned by the Registry on success and identifies the central record.

The registration record is that binding and little else. Your passport data is not stored in the Registry. The User Guide states DPP Data is created and stored by economic operators, held in the economic operator’s or a service provider’s database, and must be resolvable at all times. The economic operator has full control and responsibility for it. Using a service provider does not transfer that responsibility.

Granularity

Registration can be at Model, Batch or Item level. Model covers all items sharing the same specifications in a product family. Batch covers all items from one production run. Item applies solely to one specific unit.

For batteries, the User Guide states that only the item level is available and pre-selected, as it is the agreed and defined level for that product group. In practice that means one registration record per physical battery.

Submission methods

• Online form, for a single DPP. You supply the UPI, and optionally a Model Identifier and Batch Identifier.
• File upload, for one DPP or a batch. Files must be XML or JSON, with a downloadable template for each format.

Batch limits: a maximum of 100 DPPs per file and a maximum file size of 1 GB. Critically, if a single DPP in a submission has an error, every DPP in that submission is rejected. Validating before you submit matters more than it would with per-record handling.

Each request receives a correlation ID and an estimated validation time, and appears in the Activity Dashboard as PROCESSING, SUCCESS or FAILURE. A successful request shows the UPI, the URI and the product group per DPP. A failed one shows the UPI, the product group and a specific error per DPP, exportable as CSV.

Error reference

The Registry returns errors in four families. The remediation notes below follow the User Guide’s own guidance.

Organisation information errors

• “Some values do not match expected formats.” A field was supplied in an unexpected format, such as an email without an @ or a phone number containing letters.
• “Some required information is missing.” One or more mandatory fields were not supplied. The Save button only enables once all mandatory information is present.

Verification errors

• “The document does not contain the required number of signatures.” Exactly two are expected: the Commission institutional seal and your countersignature or counterseal.
• “The countersigned document does not match the original declaration sealed by the Commission.” Either the sealed PDF was modified after sealing, or a different document was signed. Counterseal the original, unmodified file.
• “The Commission institutional seal is missing from the document.” The submitted file is not the declaration the Commission generated and sealed.
• Commission seal validation failures. A family of errors covering a seal that cannot be validated, an identity mismatch, a seal below QSeal level, an undeterminable qualification level, PAdES non-conformance, an invalid seal status, or an untrusted or revoked certificate. All indicate the submitted declaration is not the one the Commission sealed, or the file was modified or corrupted. Restart verification.
• “The organisation’s seal does not meet the required Qualified Electronic Seal (QSeal) level.” A legal person sealed with a non-qualified seal.
• “The organisation’s signature does not meet the required Qualified Electronic Signature (QES) level.” A natural person signed with a non-qualified signature.
• “The required qualification level for the organisation’s signature or seal could not be determined.” The certificate lacks the eIDAS-qualified attributes. Contact your Qualified Trust Service Provider.
• “The certificate used for the organisation’s signature or seal is not trusted, has been revoked, or could not be verified.” Use a valid, trusted certificate and resubmit.

Submission errors

• “The file exceeds the maximum allowed size of 1 GB.” Reduce the file or split it.
• “The file name contains unsupported characters.” Allowed characters are a to z, A to Z, 0 to 9, plus dot, underscore and hyphen. Spaces, slashes and path navigation characters are rejected.
• “Invalid URL format. Enter a URL starting with https://.” The URL is malformed or not HTTPS.

Validation errors

• “The submitted file does not conform to the required schema.” The XML or JSON does not match the applicable DPP schema.
• “The same unique identifier has been used for more than one DPP in the same registration request.” Duplicate identifiers within one submission are not allowed.
• “The UPI URL is invalid.” Malformed, unsupported protocol, disallowed domain, or a non-permitted network port.
• “The submitted file exceeds the maximum of 100 registration requests.” Split into multiple files.
• “Semantic validation failed due to its unavailability.” The semantic validation service is not yet available. This is the error that currently blocks battery registration.
• “The system is unable to process your request at this time.” Possible causes given are excessive URL redirects, redirects to a less secure protocol, or an oversized response from the referenced resource.

Test environment

The Registry has a sandbox for rehearsing enrolment and registration. It requires a different EU Login from production. Nothing created there migrates to production, and objects may be removed by a data cleaning routine. The test site carries a different logo; the production site is identified as such in its footer.

The verification process in test is the same as in production and requires valid organisation data and real signatures or seals, so it genuinely rehearses the qualified certificate step. It cannot demonstrate a completed battery registration, for the reason at the top of this page.

Support

The Commission operates a helpdesk for the Registry at EC-HELPDESK-DPP@ec.europa.eu and +32 22960431, Monday to Friday, 08:00 to 20:00 CET. The Help Center inside the Registry provides user documentation, helpdesk contacts, the DPP FAQ and a link to the test environment.

Official sources

• DPP Registry User Guide for Economic Operators, version 1.01, 28 July 2026
• The Digital Product Passport Registry is now live, European Commission, 20 July 2026
• Commission Implementing Regulation (EU) 2026/1778
• Regulation (EU) 2024/1781 (ESPR)
• Regulation (EU) 2023/1542 (Batteries)

Related reading

• The EU Central DPP Registry, what it is and the ESPR Article 13 basis
• Implementing Regulation (EU) 2026/1778, the registry’s legal operating rules
• EU Battery Regulation 2023/1542, including the Article 77 passport obligation
• DPP access rights and who may see which fields