The EU's DPP Registry is the operational spine of every Digital Product Passport — spanning ESPR, batteries, construction products, toys and detergents. Today the consultation closes; here is what we asked the Commission to sharpen.
On 27 May 2026, the European Commission closed the public consultation on the draft Implementing Regulation for the EU Digital Product Passport Registry (Ares(2026)4424976). The Registry is the operational spine of every Digital Product Passport — the verification, lookup, and log infrastructure that holds together Europe's emerging product-data regime across ESPR delegated acts, batteries, construction products, toys, and detergents. Regen Studio and CircularTech Forum filed a joint submission with eleven sharpening asks. Here is what the Registry is, and what we asked the Commission to clarify before adoption.
What is the DPP Registry?
Under Article 13 of the Ecodesign for Sustainable Products Regulation (ESPR, Reg (EU) 2024/1781), the European Commission must establish a digital registry holding the unique identifier of every Digital Product Passport (DPP) placed on the EU market. The draft Implementing Regulation (Ares(2026)4424976) spells out how the Registry will actually work.
The Registry is horizontal infrastructure. One shared platform serves five distinct product-regulation regimes:
ESPR
+ sectoral DAs (textile, furniture, EV-charger)
Batteries
First DPP regime to apply
Construction Products
DPP via CPR
Toys
DPP via TSR
Detergents
DPP via DSR
For more on what a DPP is and how each of these regimes fits together, see our Digital Product Passports overview.
Plus a residual clause: any future EU regulation that mandates a DPP will plug into the same Registry. The architecture is deliberately decentralised — the Registry stores unique identifiers, verifications, semantic definitions, and audit logs, but the content of each DPP lives with the operator (or its DPP service provider), not on Commission servers. The Registry is the verification + lookup + log spine. It is not the storage of DPP content itself.
The Registry's nine components
Article 3 of the draft Implementing Regulation lists what the Registry consists of:
- A secure user interface (website)
- A registration API
- A verification platform
- A unique-identifier scheme
- A commodity-code store for customs release
- A reference list of DPP service providers
- A semantic repository (data models, vocabularies)
- A log system (audit trail)
- An identification and authorisation scheme for users
Together these nine components let an operator register a DPP, link it to a verified identity, expose it for customs and market-surveillance lookups, and leave a full audit trail of every change. The Registry is engineered to go live later in 2026, ahead of the first Battery Regulation DPP obligations on 18 February 2027, and ready to receive sectoral DPPs as Delegated Acts come into force progressively through 2030.
What we asked the Commission to sharpen
The architecture is sound. The asks below — eleven in total — are operational clarifications, all aimed at locking in specificity that downstream operators, particularly SMEs and non-EU producers, would otherwise pay for in administrative drag. We grouped them into four themes.
SME & non-EU friction reduction
- Make the registration API explicitly free of charge. The semantic repository is free under Art 12(7); the registration API is silent. SMEs and non-EU operators need cost-certainty.
- Extend the helpdesk envelope for customs and security incidents. Customs release-for-free-circulation runs continuously; the helpdesk's working-days-only scope leaves gaps an out-of-hours escalation channel would fix.
- Align verified-status validity with the underlying eIDAS instrument. A fixed 3-year cap forces re-verification disproportionate to security gain when the eID itself remains valid.
Access governance — a minimum horizontal role taxonomy
- Formalise the implicit role taxonomy in Art 3(i) and make it extendable. The IR already names actor categories across Articles 4–7 (verified operator, value-chain actor, competent authority, customs) and lists value-chain-actor sub-types in Recitals 4 and 8 (repairer, recycler, refurbisher, remanufacturer, service provider, authorised representative). What is missing is the canonical schema binding them, plus explicit extensibility so sectoral Delegated Acts can add product-specific roles within a stable horizontal vocabulary. Without this, the operator landscape fragments as each sectoral act invents its own roles.
Identity & cross-registry interoperability
- Clarify the EPREL credential-reuse model, and over time migrate both EPREL and the DPP Registry to a single eIDAS 2.0 Wallet attribute-attestation backbone. Recital 9's commitment to "double-verification avoidance" is welcome but operationally ambiguous.
- Broaden the cross-registry interoperability principle to ECHA's submission ecosystem. ECHA's REACH-IT infrastructure — single sign-on — already holds substance and substance-in-article data (REACH, CLP, SCIP) that overlaps directly with DPP substance-of-concern fields under textile, battery, and EV-charger DAs. Extending Recital 9's principle from EPREL to REACH-IT keeps the same operator from submitting the same data twice across two credentialed Commission-side systems. We scoped this ask deliberately: EU-level credentialed registries only — not 27 Member-State systems, not lookup-only systems, not role-mismatched alert systems. Speed of registry go-live matters.
Future-proofing the Registry's operational envelope
- Unbracket and design the user-notification duty (Art 17 / Recital 27). The duty sits in square brackets in the draft, signalling open Commission debate. Extend it to all users (not only operators), with a published notification channel, defined acknowledgement window, and clear consequences for failure to notify.
- Set a concrete milestone for the Cloud Sovereignty Framework. Recital 26 anchors the Registry's IT-Security Plan to the CSF "as soon as the relevant services become available" — operationally unenforceable. A defined target (e.g. CSF-compliant infrastructure within 24 months of CSF availability) plus quarterly readiness reporting would make this enforceable. Material for digital sovereignty and national security.
- Add a "unique item" checkbox to the registration UX. Recital 12 acknowledges that unique products (handmade goods, bespoke furniture) need no batch or model identifier. The Registry UI/API should support this directly, with random-audit governance to prevent abuse.
- Add a procedural fallback and dispute-resolution route for Member State non-compliance. Article 22 distributes responsibilities to Member States but the IR is silent on what happens when an MS fails to designate a national administrator, or when an MS-Commission processing dispute arises.
- Clarify how voluntary schemes can access the DPP system facilities. ESPR enables voluntary self-regulation alongside the mandatory regime, and voluntary schemes increasingly converge on DPP-style data structures. The Registry IR should offer read access to controlled vocabularies, an opt-in voluntary-DPP track that uses the registry infrastructure without triggering mandatory status, and typed cross-reference fields so voluntary attestations can be linked from within mandatory DPPs.
Why this matters now
The Registry is planned to go live later this year, in time for the Battery Regulation DPP obligations that kick in on 18 February 2027. From there, every sectoral Delegated Act that comes into force progressively through 2030 — textile, furniture, EV-charger, and more — will register its DPPs through this same infrastructure. The operational specifics being locked into the Implementing Regulation now will shape the daily friction every European product operator carries for the rest of the decade.
The architectural choices in the draft are good. The operational specificity is unfinished. The consultation window is the moment to lock in clarifications — not after operators have already started paying for the gaps.
See it in action
Want to see what a DPP system actually looks like?
Explore our interactive demo — tracking sustainable furniture from Brazilian forests through manufacturing, with UNTP verifiable credentials and ESPR-aligned compliance data threaded all the way through.
Explore the DPP System Demo →Submission reference: Ares(2026)4424976 / ISC/2026/02442 — joint submission by Regen Studio B.V. (NL) and CircularTech Forum (DE) to Have-your-say initiative #16052, which closed on 27 May 2026 23:59 Brussels.