A battery passport that nobody else can read is not a passport.
Regulation (EU) 2023/1542 requires a battery passport from 18 February 2027, but the value of that record depends on something the legal text alone cannot deliver: whether a recycler in Poland, a customs officer in Rotterdam and a second-life integrator in Spain can all open the same passport and understand the same fields. That is interoperability — carrier, identifier, data model and lookup working together — and it is where most battery data projects quietly fail.
Last updated:
In one line: interoperability means one QR code resolving to one machine-readable record, using standard identifiers and a shared data model, so every downstream actor — recycler, regulator, customs, second-life operator — reads the same battery the same way.
Why interoperability is the whole point
A battery passport is not a document you file once. Over a battery's life it is read by parties who never met your engineers: market-surveillance authorities checking compliance, customs officers deciding whether a shipment moves, repairers and second-life operators assessing whether a pack is worth reusing, and recyclers who need to know what is inside before they open it.
Each of those readers uses different systems. If your passport lives only inside a supplier portal, behind a login, in a bespoke spreadsheet schema, the data technically exists and practically does not. Interoperability is what turns roughly 110 data points into something the ecosystem can act on — and it is the difference between a compliance artefact and an asset.
The standards layer, from label to lookup
The carrier. A GS1 Digital Link QR code or Data Matrix on the battery. Digital Link matters because the code is itself a web address containing standard identifiers, so a single scan resolves for a human (a web page) and a machine (structured data) without a proprietary app.
The identifiers. Globally unique, standards-based product and item identifiers rather than internal part numbers, so the same battery is unambiguous across company boundaries.
The data model. A shared semantic vocabulary — agreed field names, units and value lists — so "state of health" or "recycled cobalt content" mean the same thing to sender and receiver. DIN DKE SPEC 99100 is the widely referenced guidance for battery passport content.
The serialisation. JSON and linked-data representations, delivered over a documented API, so systems consume the passport directly instead of scraping a page.
The lookup index. The EU DPP Registry, which opened for registration on 19 July 2026, provides the authoritative pointer from identifier to passport.
Data spaces and consortia — useful, but not the law
Two names come up constantly in battery data discussions. Catena-X is an automotive data-space initiative building shared standards and infrastructure for supply-chain data exchange. The Battery Pass consortium is an industry project that has published detailed content and technical guidance for battery passports.
Be precise about their status: these are industry and consortium initiatives, not legal requirements. Your legal obligation comes from Regulation (EU) 2023/1542 and its implementing measures — nothing more. Aligning with data-space conventions can be commercially sensible, particularly if your OEM customers already work that way, but no supplier can tell you that joining a specific consortium is how you become compliant. Treat those alignments as customer requirements to be negotiated, not statutes to be obeyed.
What to demand from any passport platform
Open export. Full structured export of your passport data, on demand, in a standard format. If you cannot get your data out, you do not own it.
Standard identifiers and carriers. GS1 Digital Link QR generation, not a proprietary code that only one vendor resolves.
A documented, machine-readable API. So your ERP, PLM and customers' systems can read and write without manual re-keying.
No lock-in. Clear answers on what happens to live QR codes on batteries already in the field if you change vendor — passports must stay accessible for the product's regulated lifetime, up to fifteen years, so ask about backup custody.
Registry filing. Handled for you, against the EU registry, not left as your homework.
PassPer is built to those answers: GS1 Digital Link QR, EU registry filing, eIDAS qualified sealing (QTSP onboarding in its final stage), EU-sovereign hosting and structured export. Run a free readiness check to see where your battery data stands today.
Frequently asked questions
Is Catena-X membership required for battery passport compliance?
No. Catena-X is an industry data-space initiative, not a legal requirement. Your battery passport obligations come from Regulation (EU) 2023/1542. Alignment with Catena-X may be demanded contractually by automotive customers, but that is a commercial requirement, not a regulatory one.
What does the Battery Pass consortium actually provide?
It is an industry consortium that has published content and technical guidance on what a battery passport should contain and how it can be exchanged. It is a useful reference for implementers, but it does not create obligations — treat its outputs as guidance alongside sources such as DIN DKE SPEC 99100.
Why does GS1 Digital Link matter more than a plain QR code?
A plain QR code is just a link somebody chose. A GS1 Digital Link QR encodes standard identifiers inside a web address, so the same scan can serve a human-readable page and a machine-readable data response, and any system that understands the standard can interpret it without your app.
How do I avoid vendor lock-in with battery passport data?
Insist on full structured export, standard identifiers, a documented API, and a written answer on what happens to QR codes already printed on batteries if you leave. Passports must remain accessible for the regulated lifetime of the product, so continuity and backup custody are contractual questions, not technical afterthoughts.