Battery Passport Overview
A Battery Passport is an electronic record tied to a specific battery. It is designed to carry standardized information about the battery model and the individual unit across its lifecycle. In the EU, the Battery Passport is established under Regulation (EU) 2023/1542 and becomes mandatory for specified battery categories starting 18 February 2027.
Here is an example Battery Passport mockup.
Key facts
| Item | Answer |
|---|---|
| Legal basis | Regulation (EU) 2023/1542, Chapter IX, Article 77 (Battery passport). |
| Mandatory start date | From 18 February 2027 for LMT batteries, EV batteries, and industrial batteries > 2 kWh placed on the EU market or put into service. |
| What it is | An electronic record (battery passport¯) containing model-level and unit-level information, including lifecycle updates. |
| How it is accessed | Via a unique identifier and a QR code that provides access to the passport record. |
| Who is responsible | The economic operator placing the battery on the market is responsible for establishing, verifying, updating, and storing the passport information (implementation details evolve via acts and guidance). |
| What information is in it | Information is defined in Annex XIII (model information, individual battery information, and certain use-phase updates). |
Which batteries are in scope
The EU battery passport requirement applies to:
| Battery category | In scope for passport | Notes |
|---|---|---|
| Electric vehicle (EV) batteries | Yes | Placed on the EU market or put into service from 18 February 2027. |
| Industrial & BESS batteries | Yes, if capacity > 2 kWh | Includes many non-road applications when placed on the EU market. |
| LMT batteries | Yes | Light means of transport (e-bikes, e-scooters, etc.), from 18 February 2027. |
If you are unsure, treat placing on the market¯ as the trigger question. If you sell into the EU, import into the EU, or place branded batteries on the EU market, assume you are in scope until proven otherwise.
What information is required
The regulation defines the passport contents in Annex XIII. At a high level, the passport must carry:
| Data area | What it covers | Why it is hard |
|---|---|---|
| Identity and serialization | Battery model identity and unit identity (unique identifier), linked to a QR code. | Requires stable identifiers across manufacturing, service, reuse, and EOL. |
| Materials and composition | Key materials and chemistry information (model-level), plus information that supports circularity and EOL decisions. | Multi-tier supplier disclosure and revision control are the bottlenecks. |
| Sustainability and performance | Carbon-related and performance-related information defined by the regulation and related acts and methods. | Requires consistent methodology and auditable data sources. |
| Safety, handling, and EOL support | Information intended to help safe handling, repurposing, and recycling. | Needs to stay aligned to real-world pack changes and incidents. |
| Lifecycle updates | Selected fields may be updated by actors involved in repair, repurpose, or EOL processing. | Access rights, responsibility boundaries, and update workflows must be defined. |
Why companies are struggling right now
| Failure mode | What it looks like | Root cause |
|---|---|---|
| Supplier data is not structured | PDF letters, partial declarations, inconsistent units, no revision control. | Legacy compliance workflows were built for static declarations, not continuous digital records. |
| Ownership is unclear | No single owner for passport truth¯ across engineering, procurement, compliance, and IT. | Passport is cross-functional and lifecycle-based, not a single department deliverable. |
| Identifiers do not survive reality | Pack revisions, module swaps, refurb, second-life conversions break identity continuity. | Identity strategy was not designed for reuse and multi-actor updates. |
| Public vs restricted data is not decided | Teams over-share (IP risk) or under-share (noncompliance risk). | Access rights and confidentiality patterns are still being operationalized in implementations. |
How to get ready
| Step | What to do | Output |
|---|---|---|
| 1 | Confirm scope by battery category and where you place products on the EU market. | Scope statement and in-scope SKU list. |
| 2 | Define identity strategy: model ID, unit ID, QR code placement, and change rules. | Identifier policy and marking plan. |
| 3 | Map required data fields to the systems that own them (PLM, ERP, test labs, suppliers). | Data ownership map and source-of-truth list. |
| 4 | Start supplier data acquisition early, focusing on the hardest materials and subassemblies. | Supplier request pack and gap register. |
| 5 | Design update workflow for repair, reuse, and EOL so the passport stays current. | Lifecycle update procedure and roles. |
Where to go next
Use these pages to drill down.
| Topic | Recommended page |
|---|---|
| Key dates and phased obligations | Battery Passport Timeline & Dates |
| Scope decision logic | Which Batteries Are in Scope |
| Data categories and structure | Battery Passport Data Requirements |
| Identity and QR code mechanics | Battery ID, Serialization & QR Codes |
| Legal responsibility and economic operators | Who Is Legally Responsible |
| Interactions with other regulations | RoHS, REACH, Transport, Recycling |
| Answers to common questions | Battery Passport FAQs |
Disclaimer. Informational guidance only. Not legal advice. Validate requirements against your jurisdiction and the latest published regulation text and standards.