DPP Agent docs

The EU DPP Registry — what exists today, and what to do about it

Written 11 August 2026. Every statement here comes from the Registry itself or from its Helpdesk, and the sources are named so you can check them.

There is a lot of noise about Digital Product Passports. This page is the unglamorous version: what the Commission's Registry can actually do this morning, what it cannot, and which of it you can usefully get out of the way now.

Where the Registry stands

The DPP Registry is live at product-passport.ec.europa.eu, with a test environment alongside it. Asked directly on 11 August 2026, the DPP Helpdesk answered:

"The current version of the DPP Registry supports the onboarding and verification of economic operators only. API access and semantic conformity checks are not yet available. The DPP Registry APIs and semantic validation assets are planned to be released in Q4 2026 … comprehensive documentation will be published at that time."

The Registry's own user guide says the same about registering a passport, in a boxed note:

"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."

So: no product passport can be registered by anyone today. Not by hand, not by API. If a supplier tells you they have registered your passports with the EU, ask which correlation ID it succeeded under.

What you can do today

One thing, and it is worth doing: enrol your company as an economic operator and get it verified.

This is a real, completable process with a real outcome — the Registry marks your organisation verified and opens DPP registration for the day it starts working. It is also the part with a lead time you do not control, because it depends on a certificate you have to buy.

It is not difficult, but it is unforgiving. The steps that catch people:

You need a qualified electronic seal, not a signature. The declaration must be sealed by your company as a legal person. A qualified electronic signature identifying a named individual — which is what most e-signing services sell, and what a DocuSign or mobile-BankID style product issues — is rejected. You need a certificate whose service type is QCert for ESeal on the EU Trusted List. Not every qualified trust service provider issues them.

The certificate must match your Registry entry character for character. The comparison covers company name, country and organisation identifier, and the Helpdesk was explicit: "Both sides must have the exact characters in order to match." A capital letter in the wrong place means a rejected verification and, if the certificate is what is wrong, a reissue rather than an edit.

So read the certificate first, then fill in the form. The identifier in the certificate is an ETSI-formatted string, not the registration number as you normally write it. Doing this in the wrong order is the most common way to lose a week.

Do not open the declaration PDF. It arrives already sealed by the Commission. Anything that re-saves the file — a preview, a PDF reader, an editor — invalidates that seal, and the upload is rejected with an error that does not tell you why.

What arrives in Q4 2026

Per the Helpdesk: the Registry APIs, the semantic validation assets, and the documentation covering available operations, technical specifications and integration requirements.

Until that documentation exists, nobody can build a conformant integration — only a guess at one. That includes us, and it includes anyone claiming otherwise.

"Verified DPP service provider" does not exist yet

You will meet vendors describing themselves as verified, approved or listed DPP service providers. As of August 2026, none of that is possible. The Helpdesk is unambiguous:

"At this stage, a list of verified DPP service providers is not yet in place, nor a formal process for organisations to be recognised as DPP service providers."

Nor can a provider register a passport for you. That capability arrives "in a later phase in 2027", with a delegated act expected in Q1 2027 describing how, and a second act around Q2 2027 setting the requirements, criteria and permitted actions for the role.

Two consequences worth holding on to:

Registration is yours to do. Until 2027, only a verified economic operator can register, and that verification is an act your legal entity performs with its own qualified seal. No supplier, agency or platform can stand in for you — including us.

For batteries it may never apply. DPP service providers are not a defined actor under the Battery Regulation at all; the role exists only under ESPR. Since batteries are the first passports to go live, in February 2027, the earliest obligations fall entirely on the economic operator.

None of this affects who hosts your passport data, which is a commercial choice you are free to make today. It affects only who is allowed to file the entry in the Commission's registry.

Why the timing is tighter than it looks

The Battery Regulation (EU) 2023/1542 requires a battery passport from 18 February 2027 for LMT batteries, industrial batteries above 2 kWh and EV batteries. Portable batteries and SLI starter batteries are outside that obligation.

Set that against a Q4 2026 specification release, and the window between "we finally know the interface" and "the obligation applies" is roughly one quarter — during which everyone subject to it will be integrating at the same time.

For textiles, footwear and the other ESPR product groups under Regulation (EU) 2024/1781, the delegated acts land later and the Registry does not yet offer the product group at all. There is no deadline pressure this year, but also no way to register early even if you wanted to.

What to do now

Get the operator verification done. It is available, it has a procurement lead time, and it is a prerequisite for everything that follows. Doing it in a quiet quarter is materially easier than doing it alongside an integration deadline.

Get your product data into shape. The Registry stores identifiers and points at your passport; it holds no product data of its own. The substance — materials, durability, chemicals, supply chain, certificates — has to be correct and maintained wherever your passport is published. That work is entirely independent of the Registry's timetable and is where the real effort sits.

Be careful about what you are promised. Registration cannot succeed today. Anyone offering to do it now is describing something that will be possible later.

Sources

  • DPP Registry, product-passport.ec.europa.eu, and its test environment at registry.acc.product-passport.ec.europa.eu
  • DPP Registry User Guide for Economic Operators, chapters 6 and 10
  • DPP Helpdesk, EC-HELPDESK-DPP@ec.europa.eu, reply of 11 August 2026
  • Regulation (EU) 2023/1542 (batteries), Article 77
  • Regulation (EU) 2024/1781 (ESPR)

We have taken an organisation through enrolment and verification ourselves, and submitted test registrations, which is where the specific failure modes above come from rather than from reading the guide. Happy to walk anyone through it.