product-guide
Is the Battery Passport Done Once the Battery Ships?
No — for EV and LMT batteries the passport is a living record that accumulates state-of-health, repair, repurposing, and recycling events over the unit's life. Here's what that changes operationally.
The short answer
No. Shipping the unit closes the manufacturing chapter of the passport, not the passport. For EV and LMT batteries specifically, the regulation expects degradation data over time — how the unit's capacity evolves against its rated figures — and the record must reflect lifecycle transitions: repaired, repurposed, recycled. A battery passport is closer to a vehicle service history than to a spec sheet.
Why the regulation wants a living record
The passport exists to make circularity work, and circularity happens after sale. Three moments depend on post-shipment data:
- Resale and warranty — a used EV or e-bike battery's value is its state of health. Serious buyers already distinguish warranties with a capacity-retention floor (typically ≥70% over a defined term, e.g. 8 years/160,000 km for EVs) from failure-only warranties; the passport makes the SoH trail per unit inspectable rather than asserted.
- Second life — a pack retired from a vehicle at 75% capacity is a stationary-storage asset, but only if its history travels with it. Without live data, second-life buyers must re-test from scratch — cost that comes out of the battery's residual value.
- Recycling — the end-of-life operator scanning the code needs current status and composition, sometimes a decade after manufacture, from a passport that has outlived your customer relationship, possibly the vehicle, and occasionally the brand that sold it.
Where the data comes from
The good news: the measurement layer largely exists. Modern BMS platforms in the industrial and LMT space already export state-of-health and state-of-charge analytics, with remote monitoring and fleet APIs — procurement guides now list telemetry schema documentation among mandatory RFP items. The gap is the connection: BMS telemetry flows into fleet dashboards today, not into passport records. The operational question for 2027 is which SoH snapshots, at which cadence, get written to the unit's passport — not how to measure them.
What this changes about your architecture
A write-once passport generator — export data, mint records, done — satisfies launch day and fails the first service event. The publishing layer needs, at minimum: per-unit records that accept appended events after publication, an ingestion path for periodic SoH updates (manual at low volume, API at fleet scale), and status transitions that downstream actors like recyclers can read and trust. If you're evaluating tooling, "what does updating 10,000 live records look like?" separates real answers from demos faster than any feature list.
What this means for your team
Plan the passport as a record with a lifecycle, not a label with extra steps. Decide now who in your organization owns post-sale updates — service? quality? — because the obligation doesn't expire at the loading dock, and retrofitting an update process in 2028 is far more painful than designing for one in 2026.