dpp.cloud logo
HomeComplianceIntegrationPricing
Resources
BlogFAQ
Company
About usPartnerContact
Schedule a Call
EN
DE

Menu

  • Home
  • Compliance
  • how it works?
  • Pricing Plan
  • Partner
  • Blog
  • About
  • Faq
  • Contact
Schedule a call
GS1 solution partner - Sqanit

Battery Passport Access Rights: The Missing Implementing Act and What to Build Before February 2027

October 26, 2026
Sebastian Eberhardt
/
ESPR & EU Regulations

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?

LayerLegal basisStatus
Public dataAnnex XIII point 1Defined. 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, CommissionAnnex XIII point 3 (the Commission also has access under point 2)Defined. Build it now.
Passport deadlineArticle 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?

  1. 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).
  2. Finish the authority layer: access for market surveillance, notified bodies and the Commission, including test reports.
  3. 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.
  4. Name an owner for verification. Agree with your passport provider in writing who onboards and checks legitimate-interest users, and how fast.
  5. Log access. Record who accessed which restricted fields and when. You will want that record the first time someone disputes an access decision.
  6. 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

FAQ

What is Article 77(9) of the Batteries Regulation?

It requires the Commission to adopt an implementing act defining which persons have a legitimate interest in the restricted data of the battery passport, and how that data may be accessed. It was due on 18 August 2026.

Has the battery passport access rights act been adopted?

Not as of 29 September 2026. The deadline of 18 August 2026 was missed, and the Commission's DPP roadmap now lists the act for Q4 2026.

Does the delay postpone the battery passport?

No. The battery passport is still mandatory from 18 February 2027 for EV, LMT and industrial batteries above 2 kWh. Only the detailed access rules are late.

Who can see restricted battery passport data?

Annex XIII gives restricted access to notified bodies, market surveillance authorities and the Commission, and to persons with a legitimate interest, such as repairers, remanufacturers, second-life operators and recyclers. The exact definition of legitimate interest is set by the pending implementing act.

What is EN 18239?

EN 18239 is the European standard for Digital Product Passport access rights management, information system security and business confidentiality. It was ratified in 2026 but had not yet been cited in a Commission implementing decision by late September 2026.

Sebastian Eberhardt

Business Development, sqanit

Related Posts

Best EON Alternatives 2026: DPP Platforms for Fashion Brands
Manufacturers of physical goods are facing a double-edged challenge. On one hand, both consumers and legislators are demanding more transparency about a product’s origin, materials, and lifecycle. On the other hand, fragmented data and limited channels to reach end users make it difficult to meet those expectations effectively
Dinesh Parmar
Dinesh Parmar
May 26, 2026
Digital Product Passport with Akeneo: From PIM Attributes to Compliant DPP in 3 Weeks
Your Akeneo attributes already cover most of what ESPR requires. This guide shows the exact mapping, a real 3-week project timeline, typical data gaps, and what the integration costs.
Julian Sotek
Julian Sotek
July 16, 2026
Batteries Without a Passport Still Need a QR Code: Article 13(6) of the EU Batteries Regulation Explained
Most batteries will never get a battery passport, but from February 2027 they still need a QR code. We explain what it has to link to, who is affected and why it's a much smaller project than a full passport.
Benedikt Biallowons
Benedikt Biallowons
November 11, 2026
Tappr Alternatives 2026: 10 DPP Platforms Compared for Manufacturers Who Need More Than Compliance
Tappr wins on entry price. Alternatives win when you need unit-level passports, a service layer on the QR code, or a 2-week PIM-based rollout. Ten platforms compared with honest fit recommendations, including when to just stay with Tappr.
Julian Sotek
Julian Sotek
August 26, 2026
Digital Product Passport for Medical Devices: No ESPR Deadline, But a Head Start Nobody Uses
No, there is no MedTech DPP deadline. What exists: a UDI foundation under MDR that makes device-level passports a small step, an eIFU regulation that gives QR-linked device pages a legal basis today, and a service economy that pays for the passport before ESPR arrives.
Sebastian Eberhardt
Sebastian Eberhardt
August 3, 2026

Browse by Category

Platform comparisons
Implementation & Integration
Business Case & ROI
Industry-Deep-Dives
Company News
ESPR & EU Regulations
DPP Fundamentals

Browse by Authors

Sebastian Eberhardt
Julian Sotek
Benedikt Biallowons
Christian Hieronimi
Dinesh Parmar
Lisa Fauland
Simon Manz
Leopold Holverscheid
dpp.cloudsqanit.com
Create your digital product passports in no time and with minimal effort.
Member of Digital Product Passport ProMEMBERDIGITAL-PRODUCT-PASSPORT.PRO
Google walletGoogle payFORRESTER
Contact us
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
    HomeComplianceBlogPricingIntegrationPartner
        About UsFAQVisit sqanitContact usLegal
          © 2025 sqanit GmbH – All rights reserved.
          ‍