Aller au contenu principal
← Regulations/EU Registry
Article 13 · Regulation (EU) 2024/1781

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. Its opening is targeted for mid-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.

D‑
days until the EU Central Registry19.07.2026 · ESPR Implementing Reg.

Deadline targeted by Article 13 of the ESPR for the opening of the central registry. The exact date will be confirmed by the implementing regulation.

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, the leading European provider of Digital Product Passports with 3.4M+ passports already deployed, is a DPP Service Provider operating an infrastructure designed for this registration, today.

The registry at a glance

Legal basis
Article 13, ESPR
Targeted opening
19 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

Who

Economic operators placing a product on the EU market — manufacturers first, through their DPP Service Provider.

When

Following the ESPR timeline per product category: first categories from 2027 (batteries, textiles), then ramping up through 2030.

How long

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: in production since 2018, across 40+ markets, 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 register each DPP with the central registry following the standardised CEN 18222 API. No re-keying, no custom development on the brand side.

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.

Going further: the Compliance Engine validates compliance before publishing, and our deep dive into the decentralised DPP architecture details how the registry works.

Frequently asked questions about the EU DPP registry

What is the EU Digital Product Passport registry?
It is the European Union's central registry established by Article 13 of the ESPR (Regulation EU 2024/1781). Operated by the European Commission, it records the digital product passports placed on the market and provides a verifiable proof of registration for each product. Its opening is targeted for mid-2026 (the text targets 19 July 2026).
Does the registry store my DPP data?
No. The central registry keeps a proof of registration (references, identifiers, timestamp), not the passport content. The DPP data stays hosted by the economic operator or its DPP Service Provider, which retains data sovereignty. This is a decentralised architecture: a public index, with data that remains with the issuer.
Do I need to register my products, and from when?
The obligation follows the ESPR timeline per product category (first categories affected from 2027). Each DPP will need to be registered with the central registry through a standard-compliant API. The proof of registration is retained for 10 years.
What is a “DPP Service Provider”?
It is a category of actor recognised by the ESPR implementing regulation (Art. 3.f): a provider that creates, hosts and registers digital product passports on behalf of economic operators. Arianee is a DPP Service Provider, in production since 2018 with 3.4M+ DPPs deployed.
How does Arianee handle registration with the registry?
Through a registry-ready infrastructure: our APIs register each DPP with the central registry following the standardised API (CEN 18222), with legally-binding proof of registration (eIDAS archiving) and 10-year retention. You keep sovereignty over your data; we handle registry compliance.
Does the registry replace the product passport?
No. The registry is an index and a proof of registration; the DPP itself — the structured data and the scannable data carrier (QR code, NFC) — remains the object that consumers, repairers and market surveillance authorities consult.

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 registration