Short answer: Article 77(9) of the Batteries Regulation required the Commission to define, by 18 August 2026, who has a "legitimate interest" in the restricted parts of the battery passport. That act didn't arrive on time and is now scheduled for Q4 2026. The passport deadline of 18 February 2027 hasn't moved, so you still have to launch with a working access layer without knowing who will finally get in. Our advice: build the public and authority layers now and keep the legitimate-interest layer configurable.
What is missing from the battery passport access rules?
The Batteries Regulation already says which data is public and which is restricted. What it left to an implementing act is the detail: which persons count as having a legitimate interest, how they prove it, and what they may do with the data once they have it. Until that act exists, nobody can say with legal certainty who belongs to that group.
There's a technical gap as well. Of the eight CEN-CENELEC standards for the DPP system, six were cited in the Official Journal in July 2026 through Implementing Decision 2026/1736 (see our explainer). The two that matter most here, EN 18239 on access rights management, information security and business confidentiality, and EN 18246 on data authentication and integrity, were ratified in August with texts scheduled for mid-September. Until a Commission decision cites them, following them doesn't give you a presumption of conformity.
What is already decided?
| Layer | Legal basis | Status |
|---|---|---|
| Public data | Annex XIII point 1 | Defined. Build it now. |
| Legitimate interest (repair, second life, recycling) | Annex XIII points 2 and 4, Article 77(9) | Data fields defined, eligible persons not yet defined |
| Test reports for notified bodies, market surveillance, Commission | Annex XIII point 3 (the Commission also has access under point 2) | Defined. Build it now. |
| Passport deadline | Article 77(1) | 18 February 2027, unchanged |
The EU registry itself has had fixed rules since Implementing Regulation 2026/1778 entered into force on 6 August 2026. They only cover who may register passports, though, not who may read the restricted data inside them. We explain the registry side in how to register a DPP in the EU registry.
Why does the delay matter?
Three months between final rules and a hard deadline is short for anything involving identity checks. Before a repair shop in Lyon or a recycler in Poland sees cell chemistry details or dismantling instructions, somebody has to check that they are who they claim to be. The regulation doesn't say whether that check is done by the manufacturer, the passport provider, or a central scheme. If the implementing act lands in December, most teams will have only a few weeks to adjust.
Separately, when the registry itself retrieves a protected passport, the host checks a registry-issued token and its own authorisation rules before returning protected data (DPP Registry Self-Hosted Authentication Guide, 30 October 2026). The Commission's battery schemas already split the passport into a public view and three restricted views (RES1 to RES3) with overlapping audiences; they do not map one-to-one to the simplified layers above.
The information behind the restricted layer is also commercially sensitive. Competitors and grey-market sellers would like to see detailed composition and part numbers. If you get access control wrong, you have a compliance problem and a confidentiality problem at once.
What should you build before February 2027?
- Finish the public layer: the public fields that apply from February 2027, reachable through the QR code, without login. Later fields such as carbon footprint and recycled content follow the Commission guidance (version 3.2 of 19 October 2026).
- Finish the authority layer: access for market surveillance, notified bodies and the Commission, including test reports.
- Set up the legitimate-interest layer as a role rather than a hard-coded list. Define the data fields now, keep the rule for who qualifies configurable, so a change in the implementing act only means adjusting settings.
- Name an owner for verification. Agree with your passport provider in writing who onboards and checks legitimate-interest users, and how fast.
- Log access. Record who accessed which restricted fields and when. You will want that record the first time someone disputes an access decision.
- Watch the Official Journal. The Article 77(9) act and the citation of EN 18239 and EN 18246 are the two items to track until February.
Because the battery passport is item-level, every access decision concerns one specific battery's record rather than a catalogue page. That's another reason the underlying data model needs a persistent identity per battery, as we explain in our battery passport guide.
"I'd build the access layer today so that roles can be adjusted later through configuration. We already know which fields are protected. Who exactly gets to look at them will come with the implementing act, and you want to be ready for that without having to rebuild everything."
Benedikt Biallowons, CTO, dpp.cloud
How dpp.cloud fits
With dpp.cloud, every individual product gets its own passport, and the source data stays in your PIM or ERP. In a strategy session we map your Annex XIII fields to the three access layers and show you where the open points of the implementing act sit in your setup. Book a strategy session, or see our DPP software buyer's guide if you're still comparing providers.
Sources
- Regulation (EU) 2023/1542, Article 77 and Annex XIII, EUR-Lex: eur-lex.europa.eu/eli/reg/2023/1542/oj
- European Commission, Digital Product Passport roadmap: single-market-economy.ec.europa.eu
- CEN-CENELEC, Digital Product Passport standards: cencenelec.eu
.png)
.png)
.jpeg)
.png)
.png)
.png)
.png)
.png)


