The era of “we’ll figure out battery compliance later” is over. On 18 February 2027, EU Regulation 2023/1542 imposes the Battery Passport: every battery placed on the EU market with a capacity above 2 kWh, including every grid-connected BESS, will need a digital data record carrying supply chain provenance, carbon footprint, cycle history, and lifecycle events, accessible through a QR code tied to a persistent unique identifier. Ten months from now, a battery without a Passport cannot legally be placed on the EU market.

Ten months is not a long runway for the kind of data infrastructure this actually requires. The Passport is frequently framed as a compliance checkbox, a legal filing dressed up with new acronyms. That framing misses what is actually happening. The Battery Passport is the moment that BESS stops being a hardware asset with a datasheet and becomes a reportable, auditable data entity with a living record. The software systems to produce that record, to keep it current, and to make it queryable by third parties are not off-the-shelf products. They have to be built. The operators who have already started building are the ones whose fleet-management and market-access software will be production-ready when the deadline hits. The operators who are waiting for a vendor to ship a “Battery Passport module” are going to learn the same lesson that hardware OEMs learned about grid-integration firmware: you cannot retrofit compliance into systems that were never designed for it.

This piece breaks down what EU Regulation 2023/1542 actually requires of BESS operators, what the Passport’s data model looks like, where the supply chain due-diligence obligations will catch teams off guard, and what the software-engineering roadmap needs to look like right now. It is a companion to this sprint’s core whitepaper on the BESS software stack that determines profitability, and it sits next to an earlier April article on how European DSOs are building DER signaling infrastructure. Both reinforce the same underlying point: in Europe, the software layer has become the compliance layer.

EU Regulation 2023/1542 in Plain Language

Regulation (EU) 2023/1542 concerning batteries and waste batteries was adopted in July 2023 and entered into force on 18 February 2024. It replaces the older Batteries Directive (2006/66/EC) and covers the full lifecycle of every battery placed on the EU market, from portable cells to industrial BESS to EV packs. For grid-connected battery storage, five obligation streams matter, and they switch on at different dates.

Carbon footprint declaration for industrial batteries above 2 kWh begins phasing in from 18 February 2025, with performance-class thresholds arriving in 2028. Due diligence requirements on cobalt, lithium, natural graphite, and nickel apply from 18 August 2025. Collection, recycling, and recovered-content obligations ramp across 2025 to 2031. Removability and replaceability provisions apply from 2027. And the Battery Passport, the obligation that most forces BESS operators into a software build, switches on 18 February 2027 for industrial batteries above 2 kWh, EV batteries, and LMT (light means of transport) batteries.

Effective date Obligation Who it applies to What it requires
18 February 2024 Obligation: Regulation entry into force. Scope: All batteries placed on the EU market. Action: Governance framework and labeling baseline take effect; subsequent obligations phase in on dated milestones.
18 February 2025 Obligation: Carbon footprint declaration (phase 1). Scope: Industrial batteries > 2 kWh. Action: Each unit ships with a cradle-to-grave carbon footprint number.
18 August 2025 Obligation: Supply-chain due diligence. Scope: Economic operators placing industrial batteries > 2 kWh on the EU market. Action: OECD-aligned due-diligence policy on cobalt, lithium, natural graphite, and nickel; third-party verification.
2025–2031 Obligation: Collection, recycling, and recovered-content targets. Scope: Producers and recyclers across all battery categories. Action: Rising collection rates; mandatory recycled-content thresholds for cobalt, lithium, nickel, lead.
2027 (from 18 Feb) Obligation: Removability and replaceability. Scope: Portable batteries in appliances; LMT batteries. Action: Design obligations enabling end-user or professional removal and replacement.
18 February 2027 Obligation: Battery Passport mandate. Scope: Industrial batteries > 2 kWh, EV batteries, LMT batteries. Action: Persistent unique identifier (QR code) resolves to a structured digital record with tiered access.
2028 Obligation: Carbon footprint performance classes. Scope: Industrial and EV batteries. Action: Maximum-threshold carbon-footprint values for eligibility on the EU market.

The Regulation applies to any economic operator that places a battery on the EU market, irrespective of where the battery was manufactured. A US-headquartered BESS OEM selling into Germany is covered. A Korean cell manufacturer shipping modules into France is covered. A Polish integrator commissioning a utility-scale asset in Italy is covered. The obligations attach to the placer (the operator who first makes the battery available for distribution or use in the EU), and they flow upstream through supplier due-diligence requirements that the placer is responsible for enforcing. There is no way to outsource the Passport to a cell vendor and walk away; the ultimate accountability sits with whoever’s name is on the CE marking.

The Battery Passport — Data Model, Access, and QR Code

The Battery Passport is a structured digital record for each individual battery, accessible through a unique identifier that is physically printed as a QR code on the battery and preserved across its operational life. Behind that QR code sits a tiered data structure, with different data fields visible to different audiences, governed by a data access framework that is still being defined in secondary legislation but whose shape is now clear enough to architect against.

Data category Representative fields Source system Access tier Update frequency
General information Fields: Manufacturer identity, model, chemistry, rated capacity, CE conformity, manufacture date. Source: Manufacturer master data. Access: Public. Cadence: Set at placement, immutable.
Compliance & labeling Fields: Carbon footprint class, due-diligence status, recycled-content percentages, hazardous substances declaration. Source: Compliance pipeline; supplier data. Access: Anyone with QR code. Cadence: Updated on regulatory milestone or supplier disclosure.
Performance & durability Fields: State of health, expected lifetime, round-trip efficiency, internal resistance history, degradation curve. Source: BMS + lifecycle event registry. Access: Persons with legitimate interest (repairers, second-life operators, recyclers). Cadence: Continuous or periodic (operator-defined).
Lifecycle events Fields: Operational cycles, maintenance events, repair history, ownership transfers, end-of-life events. Source: Fleet management + operations systems. Access: Sharpens over service life; regulators and recyclers gain access. Cadence: Event-driven, append-only.

Four broad data categories live in the Passport. General battery and manufacturer information (model, chemistry, capacity, manufacturer identity, CE conformity) is publicly visible. Compliance and labeling information (carbon footprint class, due-diligence compliance, recycled-content percentages, hazardous substances) is visible to anyone with the QR code. Performance and durability information (state of health, expected lifetime, round-trip efficiency, degradation curve, internal resistance history) is visible to persons with legitimate interest (repairers, second-life operators, recyclers) under defined access terms. Lifecycle events (operational cycles, maintenance events, repair history, end-of-life events) accumulate over the battery’s life, and access rights sharpen over time as the battery moves through its service life.

Three operational realities follow from this structure. First, the Passport is dynamic. Values like state of health and cycle count change over the battery’s life, which means the Passport cannot be a one-time manufacturing record. It has to be a live system pushing updates to a persistent identifier, reachable over the network, for a decade or more. Second, the access framework is multi-party. Repairers, second-life assessors, recyclers, and regulators will each query different subsets of the Passport under different authorization paths. Third, the data has to flow in from multiple upstream systems: the BMS, the fleet management platform, the market-operations layer, the supply-chain audit records, and the financial/commercial systems that track ownership and resale. The Passport is, functionally, a federated read layer over all of them.

Due Diligence and Carbon Footprint — the Supply Chain Audit Nobody’s Ready For

The obligation that will surprise the most BESS teams is due diligence. From 18 August 2025, every economic operator placing industrial batteries above 2 kWh in the EU has to operate a due-diligence policy covering cobalt, lithium, natural graphite, and nickel, aligned with OECD guidance on responsible sourcing. The policy must identify and assess supply-chain risks (environmental, human rights, labor, community impact), act on those risks, and report on them. Third-party verification is required. The Carbon Footprint Declaration is a related but distinct obligation: each industrial battery must ship with a cradle-to-grave carbon footprint number, and from 2028 those numbers will be graded into performance classes with minimum standards that batteries must meet to remain legally placeable.

For most BESS operators today, the raw data needed to produce these disclosures sits inside cell and module suppliers’ internal systems, partially visible at best. Consolidating that upstream data into a defensible, auditable record is a software-engineering problem before it is a legal one. A BESS operator buying LFP cells from a tier-one supplier typically receives a datasheet. Converting a datasheet into a cradle-to-grave carbon footprint requires upstream mining data, cell-manufacturing energy mix data, transport data, pack-assembly data, and end-of-life data. Each layer lives in a different database owned by a different organization.

The operators who are ahead on this have already accepted a structural truth: they cannot trust their suppliers to deliver compliant data on time, and they cannot bolt together the data pipeline in Q1 2027. They are building the pipeline now, in 2026, because the due-diligence and carbon-footprint obligations take effect first (2025 and phased through 2028) and because the data architecture for those obligations is the same architecture the Battery Passport will extend in 2027. What counts as “good enough” for August 2025 due diligence is the foundation for what will have to be live and queryable for Battery Passport on 18 February 2027.

What Software Teams Must Build Now

For a platform engineering team at a BESS operator, a VPP aggregator, or a utility-facing storage integrator, the practical software build divides into four concurrent streams that need to be under way in 2026, not 2027.

The Passport API and persistent identifier layer. Each battery needs a unique identifier that persists from manufacture through end of life. The API that resolves that identifier has to be production-grade: versioned, rate-limited, authenticated, with a data model that conforms to the EU Battery Passport specification once secondary legislation finalizes it. Because the spec is still partially draft, the smart move is to architect against the published data schema and keep the adapter layer flexible for the remaining fields. Teams that have already built protocol integration layers for grid-services signaling recognize this pattern: a stable internal model with pluggable adapters that absorb regulatory detail changes without breaking the core.

The lifecycle event registry. Operational events (cycles, depth-of-discharge excursions, temperature excursions, maintenance actions, repairs, ownership transfers) have to be captured, timestamped, attributed, and persisted for the full service life of the battery. The registry is where the Passport’s “dynamic” attributes (state of health, cycle count, degradation curve) are computed from raw operational data and pushed into the Passport view. For operators with existing battery management platforms, the question is whether those platforms already emit the event stream the registry needs, at the cadence the Passport expects.

The due-diligence and carbon-footprint data pipeline. Supplier data (mining origin, cell-manufacturing carbon intensity, transport footprint, recycled content) has to flow into operator systems on a schedule that supports August 2025 due-diligence reporting and 2028 carbon-footprint performance classes. This pipeline is a federated ETL problem: pulling data from cell suppliers, mining certifications, transport logs, and recycling counterparties, normalizing it against a standard schema, and exposing it both to the Passport layer and to the internal regulatory compliance workflow.

The BMS and fleet-management integration points. The Passport is downstream of the BMS. If the BMS does not expose the right signals (cell-level voltages, temperatures, state-of-charge estimates, fault events) over a stable interface, the lifecycle registry cannot be populated. Fleet-management platforms that aggregate across multiple sites need to consolidate those signals into per-battery records rather than per-site rollups. Teams with integrated commercial and industrial battery management implementations already have the data model half-built; the Passport obligation forces the other half to ship.

These four streams are not separable projects. They are one architecture with four user interfaces. Operators who try to run them as independent workstreams in parallel will spend 2027 wiring them together under regulatory pressure. Operators who architect them as one system now have ten months of runway.

Compliance Infrastructure Is Now Product Infrastructure

The instinct in 2026 is to treat EU Regulation 2023/1542 as a legal problem with a software implementation. That instinct will cost teams a year. The Passport, the due-diligence obligation, and the carbon-footprint disclosure are not three compliance artifacts attached to a pre-existing product. They are structural changes to what a battery is, as a commercial object, in the European market.

The winners in this regulatory cycle are the operators whose platforms were designed to emit compliant data as a core feature, not as an export. Their BMS surfaces cell-level telemetry in a format the lifecycle registry consumes without transformation. Their fleet management carries per-battery identity from commissioning through second life. Their supply-chain systems resolve cell provenance in minutes, not months. Their due-diligence records reconcile automatically against the carbon-footprint pipeline. And their Passport API returns the right data to the right audience under the right authorization path, every time.

For teams still scoping the work, 18 February 2027 is not the deadline. It is the visibility event. The real deadline is August 2025 for due diligence, 2028 for carbon-footprint performance classes, and every operational day between now and end-of-life for the rest of it. The European market is shaping up to reward the operators who internalized that early, and to penalize the ones who did not. Codibly has been building this class of platform infrastructure for European operators for years. Ten months is enough, if the architecture starts today.

Software-Defined BESS whitepaper promo - Codibly