- EUR-Lex summarizes the wider Batteries Regulation context for components, recycled content, QR-code information, and passport obligations.
"battery components and recycled content"
Use this page to separate Article 77 passport scope from Annex XIII field groups before designing a battery passport data model.
The guide focuses on which batteries need a passport, which data is public or restricted, how the QR code and unique identifier work, and which fields are model-level or individual-battery data.
Structured answer sets in this page tree.
Cited legal and guidance references.
Article 77 of Regulation (EU) 2023/1542 does not require a passport for every battery category. From 18 February 2027, the electronic battery passport applies to each LMT battery, each industrial battery with a capacity greater than 2 kWh, and each electric vehicle battery that is placed on the market or put into service. Annex XIII then divides the passport content into model-level public data, model-level restricted data, authority-only compliance data, and individual-battery data for persons with a legitimate interest.
Start the field model with the battery category. Article 77 covers LMT batteries, industrial batteries above 2 kWh, and electric vehicle batteries. Portable batteries, SLI batteries, and smaller industrial batteries may still have labelling, QR-code, conformity, removability, or waste information duties elsewhere in the Regulation, but they are not the passport categories named in Article 77(1).
The economic operator placing the covered battery on the market must ensure that the passport information is accurate, complete, and up to date. The operator may authorise another operator in writing to act on its behalf, but the passport design should still preserve responsibility, update rights, and evidence of who supplied each data element.
Use this guide to separate public, restricted, authority-only, model-level, and individual-battery fields before building or reviewing a passport implementation.
Ask battery passport implementation questions against cited EU source material.
Review Article 77 scope, Annex XIII fields, and passport data ownership with Sorena.
Do not treat the passport as one public data dump. Article 77 and Annex XIII create access tiers. Some model information is public; some model information is restricted to persons with a legitimate interest and the Commission; test-report evidence is restricted to notified bodies, market surveillance authorities, and the Commission; individual-battery operational data is restricted to persons with a legitimate interest.
The passport must be accessible through the QR code referred to in Article 13(6). That QR code links to a unique identifier attributed by the economic operator placing the battery on the market. Article 78 adds technical controls: free access based on access rights, open and interoperable formats, restricted update rights, data integrity, security, privacy, and continued availability.
Annex XIII is the safest starting point for a passport field catalogue. It does not require every data point to be published to every actor. Build the catalogue by access group, then attach source systems, validation rules, and update triggers to each group.
For public model-level information, Annex XIII points back to Annex VI Part A and adds composition, carbon footprint, due diligence, recycled content, renewable content, capacity, voltage, power capability, lifetime, warranty, efficiency, resistance, c-rate, marking, EU declaration of conformity, and waste-prevention information. Treat those as field categories that may need subfields, not as a license to invent extra public fields.
A common implementation error is mixing model data and individual-battery telemetry in one flat table. Article 77 says the passport contains information relating to the battery model and information specific to the individual battery. Annex XIII then makes the split concrete: most public fields are model-level, while state of health, battery status, usage history, cycles, negative events, operating conditions, and state of charge are individual-battery fields with restricted access.
This distinction matters for architecture. Model-level fields can usually be versioned by product compliance, engineering, sustainability, supplier documentation, conformity assessment, and waste-information owners. Individual-battery fields need serial or unique-identifier linkage, controlled update rights, event capture, and access logic for allowed legitimate-interest purposes.
For implementation, build a catalogue that records the legal source, access tier, data owner, source system, validation rule, and update trigger for each Annex XIII field category. The catalogue should avoid unsupported extra field lists: add subfields only when they are needed to satisfy an Annex XIII category, an Article 77 technical requirement, a delegated or implementing act, or a verified source-of-record system.
Before publication, test three paths: a consumer scanning the QR code should see only the public model data; a repairer, remanufacturer, second-life operator or recycler should see only the legitimate-interest data they are allowed to access; and an authority or notified body should be able to access the compliance evidence reserved to that role.
"battery components and recycled content"
"consumers and especially professionals along the value chain"
"machine-readable, structured and searchable"