All articles

The EU DPP Registry Is Live: What the Rulebook Actually Says

The EU DPP Registry went live on 20 July 2026 and Implementing Reg. (EU) 2026/1778 took effect on 6 August 2026. What it stores, how eIDAS verification works, and why registration is not proof of compliance.

LabelEU TeamAugust 19, 2026esprdppregistryregulation

The EU DPP Registry stopped being a deadline and started being infrastructure. It went live on 20 July 2026, and on 6 August 2026 the binding rulebook that governs it, Commission Implementing Regulation (EU) 2026/1778, entered into force. Anyone building Digital Product Passports now has something concrete to build against for the first time.

This post covers what the registry actually does, what the implementing regulation requires of you, and the one sentence in the ESPR that most vendors would rather you did not read.

20 Jul 2026

Registry went live

6 Aug 2026

IR (EU) 2026/1778 in force

27 Sep 2026

Green claims ban applies

18 Feb 2027

Battery passport binding

The registry exists. A passport obligation still does not.

These are two different things and they get conflated constantly. The registry being operational does not make a passport mandatory for anything. ESPR Art. 9(1) makes a passport mandatory only through an Art. 4 delegated act, and none has been adopted for any product group. The two binding passport dates that exist come from elsewhere: batteries on 18 February 2027 (Reg. (EU) 2023/1542 Art. 77) and toys on 1 August 2030 (Reg. (EU) 2025/2509 Art. 19).

What the registry is, and what it is not

It is an index, not a database of your product data. The registry stores unique identifiers and metadata about where a passport lives. The passport payload itself stays decentralised, held by the economic operator or by a DPP service provider acting for it. If you were expecting to upload your material compositions to Brussels, you were not reading the same regulation.

One registry serves several regimes at once: ESPR delegated-act products, batteries under Reg. (EU) 2023/1542, construction products under Reg. (EU) 2024/3110, toys under Reg. (EU) 2025/2509 and detergents under Reg. (EU) 2026/405 (IR 2026/1778 Art. 1(1)). For a platform, that means one integration covers many verticals. For a manufacturer with a mixed catalogue, it means one place to look.

What Implementing Regulation (EU) 2026/1778 requires

This is the part worth reading closely, because it is binding and specific.

  • Verification with an eIDAS seal (Arts. 4-5). A legal person verifies itself with a qualified electronic seal; a natural person uses a qualified electronic signature or a high-assurance eID. The verification is valid for at most three years, then it has to be redone.
  • Granularity is a first-class field (Art. 8). Registration happens at model, batch or item level, whichever the applicable law requires, with parent identifiers submitted where they exist. Battery passports are item level. Toy passports are model level. This is not a detail you can retrofit later.
  • Automatic validation (Art. 8(7)-(8)). The registry rejects submissions that fail semantic conformity, data coherence, granularity, commodity code or the link to your DPP service provider. You get a unique and persistent registration identifier back.
  • Proof of registration (Art. 9). Contains the unique product identifier, the commodity code, the verified operator identity, a timestamp, and a hash of the registered version of the passport, sealed under Art. 38 of Reg. (EU) No 910/2014. It is available for 90 days.
  • Ten-year deletion (Art. 10(3)). Registry records are deleted after ten years. Note that this is a registry retention rule, not a passport retention rule. There is no horizontal 10-year passport retention requirement in ESPR; Art. 9(2)(i) leaves the availability period to product-specific delegated acts, requiring only "at least the expected lifetime".

Registration is not proof of compliance

ESPR Art. 13(5) states it outright. Registering an identifier records that the identifier exists. It says nothing about whether your product meets any requirement, whether your data is accurate, or whether anybody has checked. Nor can any vendor certify it for you: the Art. 11 delegated act that would set requirements to become a DPP service provider, possibly with a certification scheme, has not been adopted. Nobody is a certified DPP service provider today, including us.

Who does the registering, and with whose identity

This is where a lot of platform marketing quietly overstates itself. Registration is the customer's own act, performed with the customer's eIDAS credential. A platform can prepare, structure and submit the data, and most manufacturers will never call the API by hand. But your legal identity is not something a SaaS can supply on your behalf, and whether a service provider may broker or hold those credentials at all is an open question that IR 2026/1778 does not resolve.

There is a related wrinkle for batteries. DG GROW has said that DPP service providers are not an actor in the battery regime. The mechanism there is a written authorisation under Art. 77(4) of the Battery Regulation for another operator to act on the responsible operator's behalf. Different regime, different contract wording.

The standards picture, honestly

On 15 July 2026 Commission Implementing Decision (EU) 2026/1736 cited EN 18216, 18219, 18220, 18221, 18222 and 18223:2026 in the Official Journal. Conformity with those gives a presumption of conformity with ESPR Arts. 10 and 11 under Art. 41(2). They cover data exchange protocols, identifiers, data carriers, storage and persistence, APIs and system interoperability.

Two standards are conspicuously not cited: EN 18239 on access rights, security and business confidentiality, and EN 18246 on data authentication, reliability and integrity. That means no presumption of conformity attaches to the access-control or integrity layer today. If you are choosing a platform, ask how adjustable its access tiers are, because that layer is still moving.

A caution on the carrier standards: EN 18219 and EN 18220 are paywalled. We have not bought the texts, so we make no claims about their specific requirements for symbology, error correction, quiet zones or RFID. Be sceptical of anyone who does without citing the clause.

The nearest binding date is not a passport date

On 27 September 2026, five weeks from now, Directive (EU) 2024/825 applies. It inserts into UCPD Annex I a ban on displaying a sustainability label that is not based on a certification scheme or established by public authorities (point 2a), a ban on generic environmental claims (4a), on whole-product claims derived from one aspect (4b), on offsetting-based climate-neutrality claims (4c), and on presenting legally required features as a distinctive advantage (10a).

A public passport page is a commercial communication aimed at consumers. If your passport tool stamps a green "compliant" badge on that page based on its own score, that badge becomes an unfair commercial practice in September. LabelEU does not put a self-issued compliance badge on the passports it hosts. Details are in our green claims explainer.

And while we are correcting the record: the separate Green Claims Directive proposal, COM(2023) 166, is not law. The Commission announced its intention to withdraw it on 20 June 2025 and we cannot verify that the withdrawal was formally completed. Either way there is nothing there to comply with. Do not let a vendor sell you a product against it.

Where the dates actually sit

15 July 2026

Harmonised standards cited in the OJ

Implementing Decision (EU) 2026/1736 cites EN 18216, 18219, 18220, 18221, 18222 and 18223:2026. EN 18239 and EN 18246 are not cited.

20 July 2026

EU DPP Registry goes live

Operational, with an acceptance environment, technical documentation, user guides and a free semantic repository.

6 August 2026

Registry rulebook in force

Implementing Reg. (EU) 2026/1778: eIDAS verification, granularity, automatic validation, unique registration identifier, sealed 90-day proof of registration, 10-year deletion.

27 September 2026

Empowering Consumers Directive applies

Directive (EU) 2024/825. The nearest binding date for anyone publishing a consumer-facing passport page.

18 February 2027

Battery passport binding

Reg. (EU) 2023/1542 Art. 77(1), for EV, LMT and industrial batteries above 2 kWh, at item level, with the identifier uploaded to the registry under Art. 77(10).

1 August 2030

Toy passport binding

Reg. (EU) 2025/2509 Art. 19. Model level, 14 Annex VI Part I data points, Safety Gate Portal link on access.

For textiles, furniture and electronics there is still no adopted rule at all. The full picture, with sources, is in our deadline timeline.

What to do now that the registry is real

  1. Decide your granularity before you generate identifiers. Model, batch or item is a structural choice, and the registry validates it. Batteries are item level, one passport per physical battery. Toys are model level. Getting this wrong means reissuing identifiers.
  2. Sort out your eIDAS credential. A qualified electronic seal for your legal entity is a procurement task with a lead time, and it expires after three years. Start it before the month you need it.
  3. Structure the product data. Material composition, origin, recycled content and supplier documentation are still the slow part, and no registry change makes that faster.
  4. Audit your passport page against the September ban. Uncertified badges, "eco-friendly" phrasing, offset-based neutrality claims and legally required features dressed up as advantages all become unfair commercial practices on 27 September 2026.

Frequently asked questions

What is the EU DPP Registry?

A central register run by the European Commission that stores unique product identifiers and metadata about where each Digital Product Passport lives. It does not store the passport content: that stays decentralised with the economic operator or its DPP service provider. It went live on 20 July 2026, with a separate acceptance environment for testing.

What are the binding rules for the registry?

Commission Implementing Regulation (EU) 2026/1778, in force since 6 August 2026. It covers verification of operators with an eIDAS qualified electronic seal valid for at most three years (Arts. 4-5), registration at model, batch or item granularity with automatic validation (Art. 8), a unique registration identifier, a sealed proof of registration valid 90 days (Art. 9), and deletion of registry records after 10 years (Art. 10(3)).

Does registering in the registry mean my product is compliant?

No. ESPR Art. 13(5) says registration 'shall not be deemed proof of compliance'. The registry records that an identifier exists; it makes no statement about your product or your data. There is currently no universal third-party certification obligation for passport information either.

Can my passport platform register on my behalf?

Partly. The registration is verified with an eIDAS qualified electronic seal belonging to your legal entity, or a QES or high-assurance eID for a natural person. A platform can prepare and submit the data, but it cannot manufacture your identity. Whether a service provider may hold or broker those credentials is an open question the text does not settle.

Is a Digital Product Passport mandatory yet?

Not under ESPR, for any product. Art. 9(1) makes a passport mandatory only through an Art. 4 delegated act and none has been adopted. Two binding passport obligations exist outside ESPR: battery passports from 18 February 2027 (Reg. (EU) 2023/1542 Art. 77) and toy passports from 1 August 2030 (Reg. (EU) 2025/2509 Art. 19).

What does the registry store?

Unique product identifiers, operator identity, the customs commodity code, granularity level and parent identifiers where they exist, and the link to the DPP service provider holding the back-up copy. Submissions that fail semantic, coherence, granularity, commodity-code or service-provider-link validation are rejected (IR 2026/1778 Art. 8(7)-(8)).

Does the registry cover more than ESPR products?

Yes. One registry serves ESPR delegated-act products, batteries under Reg. (EU) 2023/1542, construction products under Reg. (EU) 2024/3110, toys under Reg. (EU) 2025/2509 and detergents under Reg. (EU) 2026/405 (IR 2026/1778 Art. 1(1)). One integration, several verticals.

Can I use a PDF as a Digital Product Passport?

No. A passport has to be reachable through a data carrier linked to a persistent unique identifier, machine-readable and structured (ESPR Art. 10). A static PDF gives you none of that and cannot carry a registry identifier.

Get your product data registry-ready

LabelEU builds passports on a persistent identifier and a fixed URL, and tells you which fields the law requires and which are our recommendation. Start free with up to 3 drafts, no card required.

We use cookies

LabelEU uses essential cookies for sign-in and security. With your permission, we may also use optional analytics cookies to improve the product.

Learn more