EU battery passports that resolve to auditable battery data

From 18 February 2027, each EV battery, LMT battery, and industrial battery above 2 kWh placed on the EU market needs an electronic passport. Connect the QR identifier to controlled model, material, production, compliance, and lifecycle records—not a manually maintained product page.

Check your battery scope Map your data

Classify the finished battery before collecting fields

Product category, capacity, market action, and economic-operator role determine the passport obligation. A component list alone cannot answer scope.

Passport required

Each electric-vehicle battery
Each light-means-of-transport battery
Each industrial battery with capacity greater than 2 kWh
Finished batteries placed on the EU market or put into service from 18 February 2027

Not automatically in scope

Portable batteries that are not another covered category
Starting, lighting, and ignition batteries
Industrial batteries at or below 2 kWh
Cells, modules, and materials not themselves placed as an in-scope finished battery

The responsible party is the economic operator placing the finished battery on the market or putting it into service. The Commission expressly distinguishes that operator from suppliers of individual components or modules. Import arrangements, rebranding, own-use imports, repurposing, and remanufacturing need role-specific review against the binding Regulation.

Write down the scope decision. Store battery category, rated energy, model, responsible operator, market action, placement date, destination market, evidence, reviewer, and rule version. That record is the first auditable input to the passport pipeline.

Annex XIII is a layered data product, not a flat public record

Separate model-level facts from individual-battery updates and public information from restricted evidence. Each field needs an owner, source, unit, applicability rule, version, and access class.

Public model information

Identity and responsible operator, manufacturer and plant, category, model or serial identification, weight, capacity, chemistry, relevant substances and critical raw materials, voltage and power parameters, expected lifetime, renewable share, conformity, and waste information.

PLM · ERP · MES · compliance files

Restricted model evidence

Detailed cathode, anode, and electrolyte composition; component and spare references; exploded views, disassembly sequences, fasteners and tools; safety measures; and compliance test reports.

Engineering · service · test repository

Individual lifecycle data

Capacity and power fade where applicable, internal resistance, state-of-health parameters by category, battery status, cycle count, negative events, operating temperature, and state of charge.

BMS · service events · owner/operator updates

February 2027 baseline

The Commission's version 2.0 preparation guide maps 71 data points and their applicability by EV, LMT, and industrial category. It is highly useful for a field matrix, but it states that it is non-authoritative and does not add legal requirements. Treat it as a maintained implementation aid beside the law, not as a substitute for it.

See the August 2026 data-point guide.

Mandatory or applicable

Build and validate by category for the February launch: identifiers, operator and manufacturer data, battery characteristics, lifecycle parameters, conformity and waste information, plus restricted engineering data.

Conditional or optional

Implement explicit applicability logic. A missing conditional value must say not applicable with a reason—not look like a broken feed.

Duplicated

Publish one canonical value and map all legal references to it. The Commission guide currently flags repeated composition and capacity entries.

Phased or pending

Keep schema slots and ownership ready, but do not manufacture values for fields whose legal timetable or reporting format has not yet applied.

Do not promise recycled cobalt, lithium, nickel, or lead shares in the February baseline merely because Annex XIII lists them. The Commission's current guide marks those recycled- content fields as not yet required for February 2027, tied instead to Article 8 and the relevant delegated act. It similarly phases responsible-sourcing information to August 2027 and awaits a format for carbon-footprint fields.

Build around a canonical battery record

The passport is a projection of governed source data. It should not become the place where engineering, production, supplier, and BMS facts are manually re-entered.

Supplier and material evidence

Receive versioned declarations, material descriptions, composition and quantity data, country and chain-of-custody evidence, verification reports, document hashes, validity periods, and affected material lots.

Model and production master

Join PLM/BOM definitions to ERP suppliers, MES batch and serial genealogy, manufacturing plant and date, chemistry, ratings, conformity evidence, repair data, and finished-battery identifiers.

Lifecycle event stream

Accept signed or authenticated BMS, service, repair, owner, repurposing, and waste-status updates without overwriting the model facts or the event history that produced the current state.

Passport policy and API

Evaluate category and date applicability, validate units and evidence, publish the correct public or restricted view, record consent and authorization decisions, and expose machine-readable versioned endpoints.

QR resolver and EU Registry

Resolve the ISO/IEC 15459-compatible unique identifier, keep the printed carrier stable, register required identifier metadata through the Registry UI or API, and route users to the decentralised passport service.

GET /v1/batteries/{uniqueIdentifier}/passport

{
  "battery": {
    "category": "industrial",
    "ratedEnergyKWh": 8.4,
    "modelId": "ESS-84",
    "serialNumber": "..."
  },
  "responsibleOperator": { "id": "...", "role": "manufacturer" },
  "materials": [{
    "material": "lithium",
    "quantityBasis": "active-material-mass",
    "sourceEvidence": ["evidence:sha256:..."]
  }],
  "lifecycle": {
    "status": "original",
    "observedAt": "2027-03-18T12:40:00Z"
  },
  "accessView": "public",
  "schemaVersion": "eu-battery-passport/2027-02"
}

Validation before publication

Scope decision exists and matches category and energy
Unique identifier has not been reused
Required fields are complete for this category and date
Units, value ranges, and controlled vocabularies validate
Source and evidence lineage resolve
Restricted data cannot appear in the public projection
Registry response and published passport version are retained

The EU Registry is now live with a testing environment and API, while detailed passport data remains decentralised. Implementing Regulation 2026/1778 also makes the Commission's semantic repository the authoritative machine-readable source for DPP data models and definitions. See the Registry Regulation.

Passport composition and due-diligence traceability are related—but not identical

Reuse one material and evidence graph, while keeping each legal purpose, scope test, access rule, and output separate.

Battery passport

Answers what this model and individual battery are: identity, chemistry and materials, ratings, performance, conformity, repair and dismantling information, dynamic condition, status, and end-of-life information—split by access tier.

Applies from 18 February 2027 to Article 77 battery categories

Chapter VII due diligence

Answers how covered cobalt, natural graphite, lithium, nickel, and relevant compounds were sourced and how social and environmental risks were identified, assessed, prevented, mitigated, verified, and disclosed.

Applies from 18 August 2027 to operators within Article 47 scope

Trace lots, not documents alone

Connect a declaration and verification report to the supplier, raw-material lot, transformation or transaction, incoming material, cell batch, pack batch, model, and finished serials it actually covers.

Preserve quantity logic

Record measurement basis, units, allocation method, mass balance where used, waste or post-consumer basis, validity window, calculation version, and unresolved gaps. Never turn unknown into zero.

Keep risk evidence actionable

Store country of origin and market transactions, supplier and upstream actors, verification state, identified risks, mitigation decisions, grievances, owners, due dates, and evidence of closure.

Article 49 requires an in-scope operator's traceability system to identify upstream actors and retain at least the raw-material description, direct supplier, country of origin and market transactions from extraction to the immediate supplier, quantity in the battery, and specified verification evidence. This is a much stronger evidence chain than a public passport field saying “contains lithium.” The application date was postponed to 18 August 2027 by Regulation 2025/1561.

Design ownership changes before the first QR code is printed

A passport has to survive product transfers, service events, operator failure, repurposing, waste treatment, and recycling. Availability is a lifecycle responsibility, not a launch task.

Place and register
Create the individual passport, assign the unique identifier, publish the correct views, register required identifier data, retain the accepted registry result, and verify the QR resolves.
Use and maintain
Ingest applicable state-of-health and operating data, preserve event provenance, expose the current state with its observation time, and keep history available for audit and diagnosis.
Reuse or transform
When a battery is prepared for reuse, repurposed, or remanufactured, create the legally required new passport where applicable and link it to the original passport or passports rather than rewriting origin history.
Waste and recycle
Transfer responsibility as Article 77 requires when status changes to waste, publish the status event, preserve controlled access for treatment actors, and end the passport after the battery is recycled.

Continuity controls

Versioned exports, escrow or successor-host arrangements, documented responsibility transfer, restore tests, monitoring, stable identifiers, and a vendor exit path protect access if a provider or operator changes.

Access controls

Separate public and restricted projections, authenticate actors, authorize per purpose and field, log access and export, minimize commercial data, expire permissions, and test that public caches cannot serve a restricted response.

A useful pilot publishes real passports from real source systems

Start with one battery category and model family. Prove the hardest ownership, access, and update paths before scaling the connector across a portfolio.

Scope and field matrix
Classify roles and battery families; map each applicable legal data point to owner, source, access tier, unit, timing, evidence, validation, and current readiness.
Canonical model and adapters
Implement the battery identity, model, material, evidence, production, and lifecycle schemas plus focused adapters for PLM, ERP, MES, supplier exchange, test systems, and BMS feeds.
Passport, QR, and Registry
Ship public and protected API views, resolver, stable QR identifiers, registry test integration, signed publication history, authorization policy, and monitoring.
Evidence and operations
Run completeness and leakage tests, reconcile sample batteries to source evidence, exercise lifecycle transitions and provider exit, document runbooks, and hand over a gap backlog for later acts.

Pilot input

One battery category and model family, representative serials, source-system access, current data dictionary, supplier samples, QR constraints, and named legal/data owners.

Pilot output

Working source-to-passport pipeline, field matrix, validated public/restricted views, Registry adapter, QR resolver, lifecycle event path, audit export, tests, and gap register.

Go-live gate

Required February fields complete, restricted-data leakage tests pass, identifiers and Registry calls reconcile, operational ownership is accepted, restore/exit is tested, and pending-act assumptions are documented.

Commission Implementing Decision 2026/1736 now references six harmonised DPP standards. The Commission's current timeline places the remaining two standards in September 2026 and the battery- specific access-rights implementing act in Q4 2026. Those planned dates are implementation status, not a reason to defer the canonical data model, registry adapter, or February baseline. See the harmonised-standards decision and Commission battery-passport page.

Compare the general DPP track See another traceability architecture

EU battery passport FAQ

Which batteries need an EU battery passport?

From 18 February 2027, each electric-vehicle battery, each light-means-of-transport battery, and each industrial battery with a capacity greater than 2 kWh placed on the EU market or put into service needs a battery passport. Portable batteries, starting-lighting-ignition batteries, and industrial batteries at or below 2 kWh are not brought into passport scope merely because they are batteries; another category may still apply, so classify the finished battery under Article 3.

Who is responsible for creating the battery passport?

The economic operator placing the finished battery on the market or putting it into service is responsible. Cell, material, component, BMS, and pack suppliers still have to provide dependable upstream data, but supplying a component does not by itself make that supplier the passport owner for the finished battery.

Must every one of the Commission guide's 71 data points be live in February 2027?

No. The Commission's August 2026 guidance classifies data by battery category and marks some points mandatory, conditional, optional, duplicated, or not yet required for display in February 2027. For example, its current preparation view defers carbon-footprint fields pending an implementing format, responsible-sourcing information until the August 2027 due-diligence date, and recycled-content shares until the relevant Article 8 timetable and act apply. The guidance is non-binding and must be checked against the Regulation and later acts.

Is the battery passport the same as raw-material supply-chain due diligence?

No. The passport is a product and lifecycle information record. Chapter VII due diligence is a separate management, traceability, risk, verification, and disclosure regime for covered raw materials and in-scope operators. It applies from 18 August 2027 after Regulation (EU) 2025/1561; Article 47 excludes an operator below the EUR 40 million turnover threshold when it is not in a group exceeding that threshold. Confirm group and fact-specific scope with counsel.

Does the EU host the complete battery passport database?

No. The detailed passport operates as a decentralised system maintained by or for the responsible economic operator. The EU DPP Registry stores required identifiers and registry metadata and provides user-interface and API registration. A connector therefore needs both a passport data service and a registry adapter; registering an identifier is not the same as uploading the full passport dataset.

Can the QR code expose one public JSON document for everyone?

It should not. Article 77 and Annex XIII define public, authority-only, and legitimate-interest information. The public resolver may start at the QR code, but restricted composition, dismantling, test, and state-of-health data need policy-enforced access. The battery-specific access-rights implementing act is scheduled by the Commission for Q4 2026, so keep the authorization model configurable until the final act is published.

Does the Batteries Regulation require blockchain?

No. It requires open standards, interoperability, machine-readable structured and searchable data, availability, integrity, security, and operation without vendor lock-in. A conventional signed event log and evidence store can meet those software objectives. Use distributed-ledger technology only when a separately justified trust model requires it.

Primary sources and legal status

Reviewed 4 September 2026. Regulations 2023/1542, 2025/1561, and 2026/1778 and Implementing Decision 2026/1736 are binding EU acts within their scope. The Commission's battery-passport site, implementation timeline, and version 2.0 field guide assist preparation; the guide expressly says it is non-authoritative and introduces no additional legal duties. Yarify's system boundaries, canonical model, APIs, evidence graph, validation, and rollout gates are implementation recommendations, not legal or conformity-assessment advice.