Short answer: Before you can register a Digital Product Passport in the EU registry, your company has to become a "verified economic operator" through an eIDAS identity check, usually with a qualified electronic seal. After that you register each passport through the registry website or its API, at the level your product law requires: model, batch or item. The registry checks the entry automatically and sends back a unique registration identifier and a sealed proof of registration. The rules come from Implementing Regulation (EU) 2026/1778, which entered into force on 6 August 2026. The first products that must be registered are batteries, from 18 February 2027.
What does the EU DPP registry store?
The registry doesn't store your passport; that data stays with you or your DPP service provider. What the registry holds is identifiers and links: which product identifier belongs to which operator, which commodity code applies, and where the passport and its backup copy can be found. Customs and market surveillance use it to check whether a product has a passport. We wrote about the launch on 20 July 2026 in the EU registry is live. This article is about the rules that have applied since.
Which products have to be registered?
Regulation 2026/1778 covers every product for which EU law requires a DPP and its registration:
- Batteries with a passport under Regulation (EU) 2023/1542: EV, LMT and industrial batteries above 2 kWh (from 18 February 2027, see our battery passport guide)
- Products covered by future ESPR delegated acts, such as steel, textiles, tyres and furniture
- Construction products, toys, and detergents and surfactants under their own regulations
Step 1: become a verified economic operator
Under Article 4, an economic operator has to prove its identity through eIDAS before it can register anything. Article 5 sets up a comparable verification for value chain actors such as repairers, refurbishers and recyclers. The accepted means depend on who you are:
| Type of operator | Accepted means |
|---|---|
| Company established in the EU | Qualified electronic seal or qualified electronic attestation of attributes |
| Company outside the EU | Qualified electronic seal or electronic attestation of attributes |
| Sole trader in the EU | Qualified electronic signature, eID at assurance level high, or electronic attestation of attributes |
| Sole trader outside the EU | Qualified electronic signature or electronic attestation of attributes |
Two details are worth knowing. Your verified status expires when your eIDAS credential does, and after three years at the latest, so put the renewal in the calendar. If your company is already verified in a comparable EU system, such as EPREL for energy labelling, you don't have to go through the check again.
Getting a qualified electronic seal from a trust service provider can take a few weeks. If you place batteries on the market, get started now.
Step 2: register the passport
You submit through the registry website or its API (Article 8). The registration follows the granularity your product law sets: model, batch or item. For batteries that means each individual battery. Through the website you fill in an online form for a single passport or upload a JSON or XML file. For automated registration, the API accepts 1 to 100 passports per call and returns a task ID; the result is read in the activity dashboard. If one passport in a submission is non-compliant, none of them is registered. The upload file carries the registration data; the passport itself must be reachable at its product identifier URL when you submit, and the registry requests it in JSON. Official JSON schemas exist so far only for batteries, and the published registry API (v1.0.0) so far specifies only the battery product group.
The registry then runs automated checks:
- Does the data structure match the semantic model for the product group?
- Is the granularity the one the law requires?
- Are the mandatory data coherent, where this applies?
- Is the commodity code valid?
- Is there a link to a backup copy held by a DPP service provider?
Recital 16 makes clear that passing these checks doesn't prove compliance. A passport can go through registration and still be incomplete or wrong, and that stays your responsibility.
Step 3: what you get back
After a successful submission, the registry issues a unique, persistent registration identifier. You can also download a proof of registration (Article 9) with the product identifier, commodity code, your identity, date and time, a cryptographic hash of the passport version and the Commission's qualified electronic seal and time stamp. The proof stays downloadable for 90 days and can be generated again later.
Can a DPP provider register passports for you?
A third party, such as your DPP provider, may act in the registry on your behalf where Union law provides for this, but only after completing its own verification (Article 19(4)). You stay fully liable for what it submits. If the company changes owners, merges or stops trading, registered passports can be transferred to another verified operator.
Registration data is deleted automatically after 10 years unless the product law sets another period. Member states have to name a national administrator for the registry by 18 February 2027.
A quick checklist
- Order a qualified electronic seal for your company, or check whether you're already verified via EPREL.
- Decide who registers: your own team through the web interface, or, where the applicable product law permits third-party registration, your DPP provider through the API.
- If your provider registers for you, confirm that it has completed its own registry verification and agree the liability terms in writing.
- Make sure your passports use identifiers that follow EN 18219 and data carriers that follow EN 18220 (see the harmonised standards).
- Keep a back-up copy of each passport with an independent DPP service provider (ESPR Art. 10(4)) and make sure you can supply the link the registry asks for.
"Registering itself is quick. What takes time is getting the qualified seal and deciding who in the company is responsible. Those aren't technical questions, which is why they tend to get pushed back."
Christian Hieronimi, CEO, dpp.cloud
How dpp.cloud fits
dpp.cloud generates the passport from your PIM or ERP data, at the level your product law requires and with persistent identifiers the registry can index. In a strategy session we work through the registry side with you: who registers (your team or a verified provider) and what that means for liability and the backup copy. If you're still deciding between an internal project and a platform, read our build-vs-buy comparison or book a strategy session.
Sources
- Commission Implementing Regulation (EU) 2026/1778, EUR-Lex: eur-lex.europa.eu
- European Commission, the Digital Product Passport Registry is now live (20 July 2026): single-market-economy.ec.europa.eu/news
- Regulation (EU) 2024/1781 (ESPR), EUR-Lex: eur-lex.europa.eu/eli/reg/2024/1781/oj
.jpeg)
.png)
.png)
.png)
.png)
.png)
.png)
.png)


