The Battery Passport QR Code Is Ready, but the Source Records Are Not
A working QR code can hide an unversioned battery record. Follow one field from assembly through market entry and remanufacture to find the missing owner.
Signals to watch
- A QR-code or portal demonstration is ready, but data fields still come from unversioned files or unnamed systems
- Cell, pack, OEM, service-life or recycling participants disagree about who updates a record after a defined event
- The project has not assigned each field an access class even though the passport serves different authorised audiences
A working QR code does not make a battery passport ready. It proves that an identifier can open a page. Readiness begins when every required data item can be traced to a source, assigned to an accountable owner, refreshed after a defined event and served only to the access class allowed to see it. Without those records, the page is a demonstration with an attractive entrance and no dependable evidence behind it.
This distinction is useful to a battery-passport implementation consultancy business-development lead following authorised Telegram groups used by cell manufacturers, pack assemblers, vehicle original equipment manufacturers (OEMs), recyclers and product-data teams. “QR demo done” is weak demand. “QR demo done, but the pack file has no source version and nobody owns updates after remanufacture” is a bounded implementation problem. Seeing it after a supplier handoff or design freeze may mean the data contract has already been accepted without an owner for the next change.
Thursday’s review starts with one missing revision
Consider this composite Telegram exchange, created for illustration and not taken from a customer:
“Passport QR opens the staging page now. OEM review is next Thursday.”
“Pack capacity comes from the supplier workbook. Unsure which revision was loaded.”
“If a pack is remanufactured later, does our team update it or does the service partner create the next record?”
The thread does not identify a battery, operator, supplier, contract or actual compliance status. It reveals something narrower: the capacity shown on Thursday has no known workbook revision, and nobody has described what happens to that record after remanufacture. The useful follow-up is not “do you need a passport platform?” It is: “Which exact capacity record will the OEM review, who approved it, and which event makes it obsolete?”
If the team can answer with a battery identifier, source version, accountable operator and effective time, the discussion may be ordinary coordination. If the only answer is “whatever the staging page displays”, the source-record gap is concrete enough for an implementation review.
At assembly, the field needs an address
Start with capacity because the exchange names it; do not pretend that one field represents the whole passport. The pack assembler should be able to point to the controlled record that supplied the displayed value: for example, a versioned pack bill of materials, an approved test record or another named system of record. “Supplier workbook” is not an address until the file, revision, effective date and relationship to the individual battery are known.
This is where the legal definition matters. Under Articles 77 and 78 of Regulation (EU) 2023/1542, from 18 February 2027 each light means of transport (LMT) battery, each industrial battery with a capacity greater than 2 kWh and each electric vehicle battery must have an electronic battery passport. The passport is specific to the individual battery, linked to its unique identifier and accessible through the required QR code. The QR image is therefore an entrance to an identity-linked record, not the record itself.
Annex XIII and the applicable articles decide which information belongs in the passport. A consultancy should not invent a universal field count. Its immediate task is to prove that the field selected for Thursday’s review can be replayed from its approved source without relying on a person’s memory or an unversioned attachment.
At market entry, responsibility moves beyond the supplier
The economic operator placing the battery on the market must ensure that passport data are accurate, complete and up to date. It may authorise another economic operator to act on its behalf, but the mandate must not erase accountability. A cell maker can supply chemistry facts and a pack assembler can supply configuration facts; neither phrase answers which operator approves the finished passport record at market entry.
For the capacity example, record who is allowed to approve a correction, where that approval appears and when the corrected value takes effect. If an implementation provider loads the data, distinguish the party operating the service from the operator accountable under the Regulation. “The vendor owns the field” is not enough unless “owns” is unpacked into source, approval, correction and regulatory responsibility.
The data service also has technical constraints. Article 77(5), read with Article 78’s essential requirements, requires open standards and an interoperable, structured, searchable and machine-readable format without dependence on a proprietary vendor. That makes source lineage operational: the record must survive a system change, not merely render correctly in the first portal.
After remanufacture, do not overwrite the earlier battery story
The third message in the composite thread is the harder one. Repurposing and remanufacturing are not ordinary edits to a static product page. The Regulation addresses new passport and responsibility relationships after preparation for re-use, repurposing or remanufacturing, and the transfer of relevant information when a battery becomes waste.
Return to the same capacity field. A remanufactured pack may need a new measurement, a new effective time and a newly responsible operator. The implementation must preserve the connection to the earlier battery and passport instead of replacing the old value as though it had never existed. That is why the update trigger must name an event—pack reconfiguration, remanufacture or another defined transition—not “when someone notices the page is stale”.
The European Commission’s batteries policy page places the passport in a lifecycle that runs from sourcing and manufacture through use, collection and recycling. A Thursday demo exercises only the first display. The ownership test is whether the record still makes sense after the next lifecycle event.
The same value may not belong on every screen
The QR code can suggest that every reader receives one public payload. Article 77(2) instead distinguishes access rights. Some information is generally accessible; other information is available to notified bodies, market-surveillance authorities and the Commission, or to persons with a legitimate interest under the applicable rules.
A field can therefore be correct but exposed to the wrong audience. The implementation record for capacity should name its access class and the service that enforces it, rather than assuming that everything behind the QR code is public. Public product information, authority-only evidence and information for a legitimate service participant are different delivery decisions.
As of this review on 11 August 2026, Article 77(9) still points to an implementing-act deadline of 18 August 2026. Do not present future or unverified implementing details as settled access roles. Record what the binding Regulation establishes, what remains to be specified and which design assumption needs confirmation.
What makes the Telegram fragment commercially reviewable
The useful signal is the combination, not any single keyword: a dated OEM review, a capacity value from an unknown revision, and an unanswered remanufacturing handoff. Preserve those three statements with their source and time. Keep unknowns visible: the actual battery category, operator, contract, source file, access class and compliance status are all absent.
The review can close quickly if the team produces the controlled source, approval owner, update event and access decision. It becomes a bounded implementation need if one of those records genuinely does not exist. Neither outcome supports a claim that the battery is compliant or non-compliant.
For adjacent regulatory timing, see the analysis of the EU battery due-diligence postponement. For earlier market evidence around trials, compare the digital product passport pilot demand signal. The public pricing page is relevant only if a team later asks how authorised-group monitoring is packaged.
TOP Prospect can filter, merge, deduplicate and rank fragments from Telegram groups a user intentionally connects and is authorised to access, preserving original text, source and time for human review. It cannot read private systems, verify battery data, determine legal access rights, assign regulatory responsibility, contact participants or certify passport compliance.
FAQ
Which batteries need a passport from 18 February 2027?
Each LMT battery, each industrial battery with a capacity greater than 2 kWh and each EV battery, under Article 77.
Who is responsible for the data?
The economic operator placing the battery on the market must ensure accuracy, completeness and currency and may authorise another operator to act on its behalf. Responsibility can change at later lifecycle transitions specified by the Regulation.
Is a working QR code enough?
No. The data service also needs traceable sources, owners, update triggers, access classes and an open, interoperable, machine-readable format.
Should every field be public?
No. Access varies among generally accessible information, competent bodies and parties with a legitimate interest. The implementation must enforce the applicable rights rather than expose one universal payload.
Frequently asked questions
Which batteries need a battery passport from 18 February 2027?
Regulation (EU) 2023/1542 requires one for each light means of transport battery, each industrial battery with a capacity greater than 2 kWh and each electric vehicle battery.
Who is responsible for battery-passport data?
The economic operator placing the battery on the market must ensure the data are accurate, complete and up to date and may authorise another operator to act on its behalf. Responsibility can shift after preparation for re-use, repurposing or remanufacturing as the Regulation specifies.
Is a working QR code enough to show passport readiness?
No. The project also needs traceable sources, owners, update events, access classes and an interoperable machine-readable data service behind the identifier.
Should every passport field be public?
No. The Regulation separates generally accessible information from information available only to notified bodies, market-surveillance authorities, the Commission or parties with a legitimate interest, according to access rights.
Sources and further reading
How a Signal worth attention is found
See how Top Prospect finds and organizes Signals worth checking, keeps the original Telegram context, removes duplicates, and helps you decide what to review first. You decide whether to follow up and what to do next.
