18.02.2027Regulation (EU) 2023/1542·Art. 77 + Annex XIII
Every battery you sell in the EU needs a passport.
DPP Studio turns the product data you already have into a compliant battery passport: validated against Annex XIII, published at a permanent QR address, registered with the EU registry.
Battery passports today · more product groups as the ESPR schedule lands
- Manufacturer
- Volta Cells GmbH
- Category
- EV battery
- Chemistry
- NMC 811
- Capacity
- 212 Ah
- Voltage
- 398 V
- CO₂ footprint
- 61.2 kg / kWh
- Recycled cobalt
- 12.4 %
- On market
- 2026-05
Scan for the full record
Four obligations. No grace period.
From 18 February 2027 a battery without a passport cannot legally be placed on the EU market. The requirements are already written down. The work is turning data spread across your BOM, LCA and quality systems into one record per battery.
- ART. 77 (1)
A passport per battery
Every industrial battery above 2 kWh, every LMT battery and every EV battery placed on the EU market carries its own electronic record. Not per model. Per unit.
- ART. 77 (3)
Reachable by QR code
The battery, its packaging or its documentation carries a QR code that resolves to the passport. The address has to keep working for as long as the battery does, and past it.
- ANNEX XIII
Around 90 data points
Carbon footprint, cathode and anode composition, recycled content, state of health, dismantling information, test reports. Sourced across your BOM, LCA and quality systems.
- ART. 77 (4)
Three audiences, one record
The public sees part of it, recyclers and other legitimate-interest actors see more, market surveillance authorities see all of it. From a single source of truth.
Four states. Each one closes before the next can open.
- DRAFT01 / 04
Bring your data in
Upload the Excel template filled from your BOM and LCA exports (10 000 rows import in about three seconds), or capture a single battery in the guided form. Model-level data is entered once and inherited by every unit.
Excel import · guided capture · API
- VALIDATED02 / 04
Check it before the regulator does
Every field is checked against the versioned Annex XIII schema: types, units, value ranges, required-by-tier. You see exactly which unit is missing which field, before anything is published.
Versioned schema · field-level errors
- PUBLISHED03 / 04
Give it a permanent address
The passport goes live at a short, permanent URL with its QR code, rendered mobile-first and JavaScript-free. Corrections publish as a new version: the address never changes, and every earlier version stays retrievable.
Permanent URL · QR · versioned corrections
- REGISTERED04 / 04
File it with the EU registry
The unique product identifier is transmitted to the EU product passport registry under your own operator registration, with idempotency keys and automatic retries. Failures are visible, not silent.
Your operator ID · retries · full audit trail
One record. Three depths of access.
The regulation does not ask for three documents; it asks for one passport that shows different depths to different readers. Access is filtered once, in a single place in the code, so a field can never leak into a tier it does not belong to.
Read the diagram as containment: the authority tier holds everything the two inside it hold.
Tier (c)Authorities
Market surveillance and the Commission
The complete record: everything the two tiers inside see, plus test reports, conformity results and the full technical file, exported as JSON and as PDF.
Every export logged with reason, recipient and timestamp.
Tier (b)Legitimate interest
Recyclers, remanufacturers, notified bodies
Everything the public sees, plus detailed material composition and the dismantling and disassembly information needed to take the battery apart safely.
Granted per actor after you verify them. Revocable in one click.
Tier (a)Public
Anyone who scans the code
Manufacturer, battery category, cell chemistry, capacity, carbon footprint, recycled content, safety and end-of-life information.
No login. Server-rendered, JavaScript-free.
The compliance work, without the compliance project.
Four numbers you can hold us to, measured on the product rather than promised in a brochure.
- ~3 sper 10 000 units
A production batch is an upload, not a project
Model data is entered once and inherited by every unit, so a whole batch is one spreadsheet. 10 000 rows import in about three seconds, with a per-row error report you can hand straight back to the plant.
- 91Annex XIII fields per unit
You find the gaps, not the inspector
Every unit is checked against the versioned Annex XIII schema before it can be published: 62 of those fields mandatory, with types, units and ranges enforced. You get a list of which unit is missing which field.
- 0reprints after a correction
Fixing data never means reprinting a label
The QR address is permanent. A correction publishes as a new version behind the same URL, and every earlier version stays retrievable, so the labels already on the packs stay valid.
- 3audiences, one dataset
One record instead of three sets of documents
Public, recyclers and authorities are views of the same data, cut by the tier on each field. Nothing to keep in sync, and every authority export is logged with reason, recipient and timestamp.
Pilot programme · 18.02.2027
Bring one battery model. Leave with a registered passport.
A pilot runs on your real data: we map one model, import a production batch, publish the passports and walk the registration path end to end. You keep everything that comes out of it.
Or write to pilot@dpp-studio.eu