EU Battery Regulation 2023/1542: February 2027 Compliance Guide

Which batteries are in scope

Regulation (EU) 2023/1542 covers three categories where the passport is mandatory from February 2027: electric vehicle batteries, industrial batteries above 2 kWh capacity, and light means of transport batteries (e-bikes, e-scooters, e-mopeds). Portable batteries (consumer electronics) and SLI (starter, lighting, ignition) batteries remain outside the passport requirement for now, though other parts of the regulation — labelling, collection targets, recycled-content minimums — still apply.

What's in the mandatory fields

The passport is not a marketing datasheet. It's a structured dataset accessible via QR code on the physical product, with tiered access: public (anyone scanning), restricted (business partners and persons with legitimate interest), and authority (regulators, market surveillance). The mandatory fields map to the TracePass battery template as follows:

Which fields apply to your battery type

Not every Annex XIII point applies equally to all three in-scope categories. An EV battery, an LMT battery (e-bike, e-scooter, e-moped), and an industrial battery above 2 kWh each have a different applicability profile. A passport that legitimately leaves inapplicable points empty is correct — a battery passport is not required to contain data for a field that does not apply to its category.

The Annex XIII data structure for passports binds from 18 February 2027. Three substantive groups phase in separately: carbon footprint content (Art. 7, waiting for the Commission's methodology and format acts), recycled-content shares (Art. 8, from 18 August 2028 at the earliest; LMT from 18 August 2033), and the supply-chain due-diligence report (required in the passport from 18 August 2027). The Commission's data-point guidance defers all three at the February 2027 start, so a passport issued before a group's date leaves it out.

Where does the data actually come from?

Roughly half the battery passport — about 47 of all mandatory fields — originates outside your own company: supplier declarations, cell-maker datasheets, external PEF assessors, and certified recyclers. In practice, much of the required data already exists somewhere in the organisation; the citable gap is the supplier-sourced half.

Who is responsible

The economic operator — whoever places the battery on the EU market, which usually means the manufacturer or the importer. A distributor reselling batteries already carrying a passport does not create a new one; their obligation is to check that a passport exists before placing on the market. Where a component battery cell supplier provides the cells but the pack is assembled elsewhere, the pack manufacturer is the economic operator for the finished battery's passport.

Field walkthrough — what each section actually contains

The mandatory fields are clinically named in the regulation but ordinary in content. A few examples — the kind of thing your compliance team will trace through datasheets, IEC test reports, supplier declarations, and the PEF study — to anchor what "a battery passport field" actually means in practice:

• batteryUniqueIdentifier — a GS1 Digital Link URI that uniquely points at the specific battery unit (e.g. https://id.gs1.eu/01/<gtin>/21/<serial>). Source: your GS1 registration + serial-number generation. The single field that turns a passport from "per-model" to "per-individual".
• carbonFootprintRawMaterialAcquisition — kg CO₂e per kWh from the raw-materials phase of the lifecycle, calculated via PEF methodology. Source: the PEF study (€8K–€25K via an external assessor, 2–6 weeks). One field; six weeks of work upstream.
• recycledContentCobalt — percentage of cobalt in the cell that came from recycled sources, with chain-of-custody evidence required. Source: cell-supplier declaration backed by mass-balance accounting from a certified recycler. The first time you ask for this, expect a 4-week scramble.
• expectedLifetimeYears / expectedLifetimeFullCycles — manufacturer-stated lifespan with the test conditions that justify it. Source: your IEC 61960 / IEC 62619 test report. The field most often blocked because the test program ran on an earlier revision.
• dismantlingInformation — a URL pointing to a public PDF / video / instruction set explaining how the battery is removed from the host device for replacement or recycling. Source: your service-documentation team. Most teams realise they have repair instructions but not dismantling instructions; those are different documents.

Compliance-team mistakes and how to avoid them

Patterns I've watched repeat across battery-passport rollouts. None of these are deal-breakers; all of them cost weeks if you hit them late instead of planning around them:

• Starting the PEF study after design freeze. PEF takes 2–6 weeks via an external assessor and needs the bill-of-materials at the cell level. Teams that kick it off in the same week as type-approval submission lose 4–6 weeks they didn't budget. Start the PEF when you start the IEC test campaign.
• Mixing units in the supplier-data layer. Cell suppliers report capacity in Ah, energy in Wh, and resistance in mΩ. Pack-level data needs kWh, kg, and Ω. The unit conversion isn't hard but the version drift between supplier exports and your DPP template silently breaks the field. Pin units in the supplier portal and reject inconsistent inputs at intake, not at QA sweep.
• Using a stale SVHC list. The REACH SVHC candidate list updates twice a year (typically Jan and Jul). A passport published in February that lists "compliant per the 2024 SVHC list" is technically out of date by the time it's printed on the QR-code label. Auto-pull the current list at publish time, not at template-design time.
• Treating the passport as one-and-done. Once published, the passport must remain accurate for the battery's full lifetime. If you change cell chemistry mid-production, the passport for that production batch onward needs to update — and the older passports need to remain available for the units already in market. Most teams forget about the second part.
• Forgetting the GS1 setup until late. Without a registered GS1 GTIN + a Digital Link resolver, you literally cannot generate a valid passport URL. GS1 membership for a small EU manufacturer is €500–€1500/year (varies per country) and the registration process takes 1–4 weeks. Start that before the data-collection sprint, not after.

Cost ranges — what you'll actually spend

Indicative costs for a single battery model going through first-time DPP compliance. Numbers shift with model complexity, supplier responsiveness, and whether you're EU- or non-EU-based, but the order of magnitude is stable:

Where to start today

If you place batteries on the EU market and February 2027 is inside your product-development horizon, start by inventorying all mandatory fields against what your organisation already has. Most manufacturers find much of the data already exists — scattered across datasheets, supplier certificates, EPD reports, and internal QA documents. The gap is usually recycled-content percentages, per-kWh carbon footprint (requires a PEF calculation), and supply-chain due-diligence evidence. That gap is where you'll spend the next 18 months, and it's why a platform like TracePass exists: to collapse the last-mile data-wrangling step so your compliance team isn't still emailing suppliers in January 2027.

What a battery-compliance solution has to do

Choosing software or a service partner for battery passport compliance means checking whether it can handle all the structural requirements — not just data entry. A vendor-neutral list of what any capable solution needs to cover:

• Model the full Annex XIII data structure per battery type — distinguishing required, conditional and not-applicable for EV, LMT and industrial, and tracking the four access tiers (public, legitimate-interest, authority, notified-body) per field.
• Pull values from supplier datasheets, test reports and reference databases rather than requiring a human to retype them — AI-assisted extraction with a human approval step is the norm; nothing should auto-publish.
• Collect supplier-held data (origin of critical raw materials, Art. 52 due-diligence attestations) through a controlled supplier portal with reminders — without requiring the supplier to create an account.
• Issue a GS1 Digital Link QR code per unit that resolves to a tiered view of the passport, so a consumer scanning the label sees the public tier and an authority scanning the same code reaches the restricted data.
• Maintain an audit trail of who entered what, when, and from which source document — and keep the passport current through repurposing or second-life events without invalidating older units.
• Run a mechanical registry-readiness preflight to check whether the passport structure meets the EU DPP Registry submission gates, and export portable JSON-LD — without claiming registry conformance or acting as the economic operator's legal representative.

TracePass is one implementation of this: it models the full Annex XIII data structure per battery type, extracts from supplier datasheets and test reports with AI assistance, routes missing data through a token-based supplier portal, issues a GS1 Digital Link QR per battery unit, and runs a registry-readiness preflight before JSON-LD export — without claiming to submit the passport on your behalf.

Scan to open on your phone

Live demo

See a real Digital Product Passport.

An EV traction battery — the mandatory battery-passport fields populated and reviewer-approved. Scan the QR with your phone or open the link to see how a published passport renders to a customer.

View live demo passport