The EU registry: what's live, what's pending.
Article 13 of the Ecodesign for Sustainable Products Regulation (EU) 2024/1781 requires the European Commission to set up a central Digital Product Passport registry by 19 July 2026. It is one of the most misunderstood pieces of the DPP architecture — and one of the most misrepresented in vendor marketing. Here is what the registry actually is, what it is not, and exactly where it stands.
Last updated: · status statements are accurate as of this date
An index of identifiers — not a passport database
The EU Digital Product Passport registry is an index: it stores the unique identifiers of products, operators and facilities, together with data-carrier references, and resolves them to passports hosted elsewhere. It does not host passport data itself.
That design decision — written into ESPR's decentralised architecture — is the whole point. Passport data stays on infrastructure chosen by the economic operator (or their service provider), under their control; the registry maps a Unique Product Identifier to the exact URI where the passport lives. Market-surveillance authorities query the registry to find a passport; they read the passport from wherever it is hosted.
Two practical consequences follow. First, hosting and persistence remain the operator's obligation — the registry will not preserve your data for you (that duty is shaped by EN 18221; see the standards guide). Second, the identifier scheme matters more than ever: what you register must be exactly what your QR codes resolve (EN 18219, GS1 Digital Link).
Status as of June 2026
The legal deadline stands at 19 July 2026. The implementing regulation that defines how identifiers will actually be registered — formats, who registers, through which interface — was still in draft public consultation in May 2026 (the CIRPASS-2 project filed its consultation response on 27 May 2026). As of 12 June 2026, no public registration API for economic operators or their service providers is live.
What that means in plain terms: the registry can legally launch as an internal Commission system on time while the operator-facing onboarding mechanics arrive with the implementing regulation. Registration duties bind when product-specific rules apply — for the first products in scope (batteries, from 18 February 2027; see the battery passport guide), registration happens before placing the product on the market.
No vendor can be synchronising passports with the EU registry today, because the registration API does not exist yet. If a provider claims live registry integration in 2026, ask them which API they mean.
— The one due-diligence question that sorts the market (status as of June 2026)What "registry-ready" means at OpenDPP
OpenDPP is registry-ready, not registry-connected — and we say so deliberately. There is still no live Commission registration API. What exists today is everything the registry will index — plus a pointer projection we have proven, end to end, against the CIRPASS-2 reference implementation of that index: it registers, returns a cryptographically verifiable proof of registration, and is discoverable.
Concretely: every OpenDPP passport already carries a standards-shaped unique identifier (GS1 GTIN/GRAI product keys, GLN facility identifiers), is resolvable at a stable GS1 Digital Link URI, and stays resolvable through the retention window. We go a step beyond shape: OpenDPP projects each passport into the exact Article 13 pointer record — product identifier, responsible-operator id, facility GLNs, primary and backup resolution URLs, commodity code and granularity — and validates that record against the CIRPASS-2 mock EU registry's own schema. In our open interop harness we go further: that pointer is registered against the running CIRPASS-2 reference registry — which returns a cryptographically verifiable Proof-of-Registration — and its discovery keys resolve in the reference data-extractor; the schemas, the field mapping and a reproducible validator are published in our open interop kit, so anyone can check it without our source. CIRPASS-2 is an EU-funded reference project, not the Commission's production registry, and it grants no certification. The Commission's production registry is now live, though battery DPPs cannot yet be successfully registered there — the Batteries semantic catalogue is still pending. The registry also caps a registered Unique Product Identifier at 50 resolvable characters: every OpenDPP battery unit already meets it with a compact resolvable link, so when battery registration opens, registering is a submission step, not a re-architecture. That is the practical meaning of readiness: your identifiers and links are already in the shape the registry indexes.
Where these facts come from
Legal basis: Regulation (EU) 2024/1781, Article 13. Implementation status: the Commission's ESPR implementation hub and the CIRPASS-2 project (consultation response, 27 May 2026). Related reading: the EN 182xx standards guide and the ESPR timeline.
Be ready before registry day.
Issue passports whose identifiers, links and persistence already match what the registry will index.
Book a demoArticle 13 of ESPR (EU) 2024/1781 requires the European Commission to set up a central Digital Product Passport registry by 19 July 2026. The registry is an index, not a data host: it stores unique identifiers and data-carrier references and resolves them to passports hosted by economic operators or their providers. The implementing regulation that defines how identifiers are registered was still in draft public consultation in May 2026, and as of June 2026 no public registration API is live — which is why no vendor can truthfully claim live registry synchronisation today.
The EU DPP Registry: what’s live, what’s pending · Last reviewed