The EU registry for Digital Product Passports
Article 13 of the ESPR creates a central EU registry for Digital Product Passports, operated by the European Commission. It has been live since 20 July 2026. The key point: this registry does not host your data — it records the proof of it. Understanding this architecture is understanding how to prepare without losing data sovereignty.
Webinar in English · 14 October 2026, 11:30 CEST · Stéphane Delecroix
EU DPP Registry: how does it actually work? Register for the webinar →The central registry has been live since 20 July 2026 and its operating rules have applied since 6 August 2026 (Implementing Regulation (EU) 2026/1778). The countdown now runs to the next firm deadline: the Battery Pass obligation of 18 February 2027.
What is the EU central registry for DPPs?
The central registry is the single entry point established by Article 13 of the ESPR (Regulation EU 2024/1781). Operated by the European Commission, it records the digital passports placed on the EU market and provides a verifiable proof of registration for each product.
Its role is not to store the passports, but to index them: it links a product identifier to its economic operator and attests to its registration. Market surveillance authorities rely on it to verify that a product has a compliant DPP.
Arianee — co-leader of ABI Research's ranking of DPP providers, with 4M+ passports already deployed — is a DPP Service Provider and operates an infrastructure designed for this registration, today.
The registry at a glance
- Legal basis
- Article 13, ESPR
- Live since
- 20 July 2026
- Operated by
- EU Commission
- Data stored
- No · proof
- Retention
- 10 years
- Registration API
- CEN 18222
What the registry records — and what it does not store
This is the key to the European DPP architecture: the central registry is an index, not a product database. It keeps the proof of registration; the passport content stays with the operator or its DPP Service Provider. Your data does not flow into a centralised silo.
Recorded in the registry
- Unique product and passport identifier
- Reference of the responsible economic operator
- Product category and classification data
- Timestamp and proof of registration (eIDAS)
Kept with the operator (not in the registry)
- The detailed passport content (durability, composition, compliance…)
- Confidential data subject to access rights
- The lifecycle history (repairs, transfers, recycling)
Who must register, when, and for how long
Economic operators placing a product on the EU market — manufacturers first, through their DPP Service Provider.
Following the ESPR timeline per product category: first categories from 2027 (batteries, textiles), then ramping up through 2030.
The proof of registration is retained for 10 years, with timestamping and eIDAS guarantees.
The detailed obligations per category are set by the delegated acts — see our ESPR & Digital Product Passport guide.
The role of the “DPP Service Provider”
The ESPR implementing regulation recognises a dedicated category of actor: the DPP Service Provider (Art. 3.f). It is the provider that creates, hosts and registers passports with the central registry on behalf of economic operators.
This recognition validates the open infrastructure approach: a network of interoperable providers, with no single silo, where data stays portable and passport persistence is guaranteed beyond the issuer.
Arianee is a DPP Service Provider within the meaning of this article and performs this role for its clients: in production since 2018, for 50+ brands. The CEN/CENELEC standardisation work — notably standard 18222, which specifies the registry registration API — confirms this architecture.
“Registry-ready” is not a marketing claim.
It is a technical capability: registering each DPP with the central registry via the standardised API, archiving the proof with legal value, and retaining all of it for 10 years — without your data ever leaving your perimeter.
How Arianee makes your DPPs registry-ready
Registration with the central registry is just one step of a complete DPP setup. Arianee provides the infrastructure that makes it automatic and compliant.
Automated registration
Our APIs are ready to register each DPP with the central registry following the standardised CEN 18222 API — no re-keying, no custom development on the brand side. Enrolling your organisation with the registry remains your own step.
Legally-binding proof
The proof of registration is legally archived (eIDAS, Arkhineo partner / NF Z42-013) — a DPP that holds up in court.
10-year retention
Archiving of the proof of registration covers the retention period required by the regulation, with no effort on your part.
Sovereign data
The registry only stores a proof. Your passport data stays with you, portable and auditable — no vendor lock-in.
Open infrastructure
Built on the open-source Arianee protocol: decentralised identifiers, persistence beyond the issuer, guaranteed interoperability.
Multi-regulatory
The same DPP covers ESPR registration and the Battery Pass, WEEE and AGEC/CSRD requirements — one euro invested covers several regulations.
Frequently asked questions about the EU DPP registry
What is the EU Digital Product Passport registry?
Does the registry store my DPP data?
Do I need to register my products, and from when?
What is a “DPP Service Provider”?
How does Arianee handle registration with the registry?
Does the registry replace the product passport?
Official sources
Every requirement stated on this page comes from the following primary texts.
- Regulation (EU) 2024/1781 establishing the ecodesign framework (ESPR)
Official Journal of the European Union
Legal basis of the registry: Article 13 establishes the central registry of digital product passports. Article 12 covers unique identifiers, Article 15 the customs controls that rely on the registry.
- Implementing Regulation (EU) 2026/1778 on the DPP registry
Official Journal of the European Union
Operational framework of the registry: access management, user verification, data registration, storage requirements and technical architecture. This is the text to consult for the application date of each rule — EUR-Lex is authoritative, not our pages.
- DPP Registry — the Commission's official page
European Commission — DG GROW
Reference page for the registry. It is the source for the registry being the indexing service for all DPPs placed on the EU market, and for the fact that it does not store the full passport data.
- DPP Registry User Guide for Economic Operators (v1.02, 24 August 2026)
European Commission — DG GROW Digital Solutions
Operational guide: organisation enrolment and verification (EU Login, NTR/LEI/VAT/eID identifier, eIDAS qualified seal or signature), the Registration Record / DPP Data split, the UPI as a URL compliant with JTC 24 standards, Model/Batch/Item granularity. A versioned document: check the version in force.
- "The Digital Product Passport Registry is now live" — announcement of 20 July 2026
European Commission — DG GROW
The source for the registry's actual go-live date, 20 July 2026, alongside its testing environment. Not to be confused with 19 July 2026, which is the legal deadline set for the Commission by Article 13(1) of the ESPR ("by" that date).
- DPP Registry — production environment and sandbox
European Commission
The registry itself. The test environment sits at registry.acc.product-passport.ec.europa.eu and requires the same qualified seals as production.
- Digital Product Passport — the Commission's topic page
European Commission — DG GROW
Application timetable by product group and the list of sectoral regulations that mandate a passport in their own right, beyond the ESPR.
Ready for the EU registry?
Our compliance experts show you how to register your DPPs with the central registry — without losing control of your data.
Prepare my registry registrationAre your DPPs registry-ready?
Assess your DPP compliance in 10 questions — instant personalised result.