The European Commission's Digital Product Passport Registry, Explained

The European Commission's Digital Product Passport registry is a central database, built and operated at EU level, that holds the unique identifier and basic administrative metadata for every product carrying a digital product passport — battery passports included. It is not the passport itself. It is the index that lets a market surveillance authority, a customs officer or a national administrator confirm a given identifier is real, look up which economic operator is responsible for it, and route access requests correctly.

Most pages covering the Digital Product Passport describe this registry in the abstract, because the instrument that actually built it is only weeks old. Here is what it says, precisely, with the citation attached to every claim.

The implementing act that created the registry

Commission Implementing Regulation (EU) 2026/1778 of 16 July 2026 (OJ L, 2026/1778, 17.7.2026; CELEX 32026R1778) lays down the implementation arrangements for the digital product passport registry. Its legal basis is Article 13 of the Ecodesign for Sustainable Products Regulation, Regulation (EU) 2024/1781 — specifically Article 13(5), second and third subparagraphs — not Article 12, which is a mix-up worth avoiding since it points at the wrong empowerment entirely.

Article 1 of the implementing act sets the scope, and it names batteries expressly:

"(a) products covered by delegated acts adopted pursuant to Article 4 of Regulation (EU) 2024/1781; (b) batteries covered by Article 77 of Regulation (EU) 2023/1542; (c) construction products covered by Article 76 of Regulation (EU) 2024/3110; (d) toys …; (e) detergents …"

So the registry is not a battery-specific system. It is the shared ESPR-wide infrastructure, and the Batteries Regulation opts in explicitly at point (b).

Registry, or passport — these are not the same thing

The registry doesn't carry your battery's chemistry, state of health or dismantling instructions — that data lives in the passport itself, hosted by the responsible operator, exactly as before. What the registry adds is a single, Commission-run place where the identifier for that passport is recorded and can be checked.

What operators must upload, and when

The link between the two systems sits in a paragraph of the Batteries Regulation that is easy to miss: the consolidated text carries a corrigendum (flagged ▼C2) absent from the original 2023 Official Journal PDF. Article 77(10) reads:

"The economic operator placing the battery on the market or putting it into service shall upload the unique identifier in the registry referred to in Article 13(1) of Regulation (EU) 2024/1781."

Anyone still working from the original 2023 OJ text will not see this obligation at all. Combined with Impl. Reg. 2026/1778, it means: from the point the battery passport obligation applies, the operator responsible for the passport must also register the battery's unique identifier centrally with the Commission's registry — not just publish it in the passport.

1. 16–17 July 2026In force

   Registry implementing act adopted and published

   Impl. Reg. (EU) 2026/1778 signed 16 July, published in the Official Journal 17 July 2026.

2. 6 August 2026Due

   Impl. Reg. (EU) 2026/1778 enters into force

   Twenty days after OJ publication, per Article 24 of the Regulation.

3. 18 August 2026Due

   Statutory deadline for the Article 77(9) access-rights act

   Governs who may see legitimate-interest data and how. No draft has been published.

4. Q4 2026 (Commission's own target)Expected

   Commission roadmap slot for the Article 77(9) act

   The Commission's published DPP roadmap places this act after its own statutory deadline.

5. 18 February 2027Due

   National administrators appointed; battery uploads begin

   The same date the battery passport obligation itself starts applying.

Two deadlines land on the same day for a reason. Article 77(1) of the Batteries Regulation requires every LMT battery, every industrial battery above 2 kWh, and every EV battery placed on the market or put into service to carry a battery passport from 18 February 2027. Article 7(1) of Impl. Reg. 2026/1778 requires each Member State to appoint a national registry administrator "at the latest by" that same date. Registration and passport go live together, by design.

The national registry administrators

Article 7(1) of Impl. Reg. 2026/1778 is specific about what each Member State owes the system:

"At the latest by 18 February 2027, Member States shall appoint a designated national administrator who shall act as the single official contact point for the Commission for the purposes of managing registry access rights for that Member State."

In practice, this administrator is the plumbing behind "who gets to see what." The Commission runs the central registry; each Member State's administrator manages access rights on its own side of it. Neither role is a substitute for the operator's own passport-hosting obligation under Article 77(4) — uploading the identifier to the registry does not relieve the operator of maintaining the passport data itself, or of the requirement that the passport "remain available" after the operator ceases to exist or ceases activity in the Union (Article 78(e)).

What the Commission has not delivered yet

The registry itself is built. What is missing is the piece that governs one specific access tier inside the battery passport: who counts as a "person with a legitimate interest," and what they may see.

Article 77(9) of the Batteries Regulation requires the Commission to adopt, by 18 August 2026, an implementing act specifying which persons qualify as having a "legitimate interest" under Annex XIII points 2 and 4, and to what extent they may access, download, share or re-use that data. As of July 2026 that act has no CELEX number, because it does not exist. Until it does, the legitimate-interest access tier of the battery passport — detailed composition, spare-part sources, dismantling information, state of health, usage history — has no operational access rule behind it, even though the registry that will help enforce access rights is already in force.

It is worth being precise about which acts this is, and is not. Implementing Regulation (EU) 2025/2289 of 13 November 2025 (CELEX 32025R2289) is the only implementing regulation actually adopted under the Batteries Regulation to date, and it concerns waste-battery reporting formats under Article 76(5) — a different subject entirely. And Impl. Reg. 2026/1778, covered above, is the ESPR-wide registry act, not the battery-specific access-rights act. All three numbers circulate in searches about "the DPP registry implementing act"; only 2026/1778 is that act.

What this means if you place batteries on the market

Three things are now fixed enough to plan against, and one is genuinely open:

• Build the upload into your passport workflow, not alongside it. Article 77(10) makes registry upload of the unique identifier a distinct obligation from publishing the passport itself. Treat it as a second integration point against the same identifier scheme.
• Do not wait on a national administrator to tell you the process. Member States have until 18 February 2027 to appoint theirs — the same day your passport obligation starts. There is no guarantee that process will be live with lead time to spare.
• The registry going live does not resolve access control. The central plumbing exists from 6 August 2026; the rule for who is a legitimate-interest party under Article 77(9) does not, and is on track to miss its own 18 August 2026 deadline. Do not build an access-control implementation against a definition that has not been published.
• The open question is timing, not existence. The registry exists; the access-rights act is the piece to keep watching.

For the fuller Digital Product Passport picture beyond the registry, see the Digital Product Passport pillar guide. For the full battery passport data model and who can see each field, see data requirements; for the obligation calendar this fits into, see compliance; and for the questions teams ask before they start, see the FAQ.