A battery passport backed by a history of use

Battery passport software with operational evidence. Bring product information and reported battery performance into one record. Adaptr Cloud helps operators preserve the evidence behind a battery’s condition, from day-to-day use to resale and second-life assessment.

For organisations managing battery records. Hardware and data coverage are reviewed during onboarding. Request a demo, or Read the requirements first.

Keep the facts and the evidence together.

What the pilot does, in three parts.

01 · Record — Capture what the battery reports

Keep timestamped observations and their reporting source. Review charge, temperature, voltage, current and health where the connected source provides them. Missing readings remain visible as gaps.

02 · Maintain — Manage passport information

Maintain battery and model information, review completeness, and track passport field changes with an audit trail. Model-level values can be inherited by individual batteries.

03 · Share — Provide a public QR entry point

Link a physical battery to its public passport page. The public view exposes a limited set of information, while the back office provides authenticated access to the operational record.

Start with a battery record somebody needs to trust.

Where it helps. A BESS operator investigating degradation, a fleet owner preparing warranty evidence, or a buyer reviewing a used battery needs more than today’s headline figure.

Adaptr Cloud gives the reviewer recorded observations and the context available from the source. A history can support an investigation; it does not prove a warranty claim, guarantee resale value or replace an independent assessment.

Evidence support, with explicit limits.

Know the boundary.

• No automatic compliance guarantee. A QR page and telemetry history do not establish compliance with the EU Batteries Regulation. Required product and supply-chain information must still be obtained, checked and maintained.
• No automatic EU registry submission. The pilot does not submit records to the EU DPP Registry. Registration and conformity arrangements need to be handled separately.
• No safety or second-life certification. Telemetry supports a qualified assessment. It does not certify that a battery is safe or suitable for a new application.
• Integration depends on the source. Available fields and update frequency depend on the hardware and integration. Health may be reported or estimated; neither should be presented as an independent capacity test.

Four questions, answered with sources.

Regulatory guides.

• What must a battery passport contain? Scope, responsibility, information and how to prepare.
• What happens on 18 Feb 2027? What the deadline requires, what it does not, and what is worth doing first.
• Does a UK battery need a passport? Great Britain, Northern Ireland and supplying the EU are three different answers.
• What does a finished passport look like? A worked example with sample data — observed history, faults, declared figures, and what the public does not see.
• What must the QR code resolve to? The code is how a passport is reached, not the passport itself.

By category: EV traction batteries · LMT — e-bikes, e-scooters, e-mopeds · industrial and storage batteries

A practical first step

Bring your hardware and the question you need to answer. Tell us the battery types you manage, how their data can be accessed and who needs the record. We’ll review whether the pilot fits before setting up access.

Request a demo · Understand the EU requirements →