DPP BUYER GUIDES
Battery Passport Software: A Practical Shortlist for EU Manufacturers
The EU battery passport deadline makes software selection an implementation decision, not a QR-code experiment. Start with the battery categories you place on the EU market, then test whether a platform connects each field to its source, owner and access rule. This guide compares four vendors’ published capabilities; it does not certify regulatory compliance.
Start with the legal scope and the data work
Article 77 of Regulation (EU) 2023/1542 applies from 18 February 2027 to batteries for light means of transport (LMT), electric-vehicle batteries, and industrial batteries with a capacity above 2 kWh that are placed on the market or put into service. The passport combines model-level and battery-specific information, including information generated through use. Confirm how the law classifies each product and battery before counting records: “all batteries” is not the Article 77 scope.
A battery passport is a connected information system; a QR code is only a carrier. Teams still have to identify the battery, collect data and evidence, maintain records through lifecycle changes, and expose different information to public, legitimate-interest and authority audiences. Use the Commission’s August 2026 battery data-point guidance alongside the Regulation instead of treating an early vendor checklist as the final schema.
The EU DPP Registry became operational on 20 July 2026. It is an EU-level index for unique identifiers and required registration metadata, not a central store for every detailed battery record. The detailed passport remains the responsibility of the economic operator and may be hosted by that operator or a service provider. A vendor’s “Registry ready” statement therefore needs to be unpacked: does its product create and host records, support identifier resolution, submit required registration data, or only issue a QR link?
Published battery-passport product options
These are candidates for evaluation, not independently tested compliance claims. Vendor websites do not establish interoperability, implementation time, price or legal sufficiency. Request a dated proposal covering modules, categories, identifiers, volumes, integration, service, export and exit terms. The cited pages do not provide comparable scoped quotes.
| Product | Published fit | Best first evaluation question |
|---|---|---|
| Circularise Battery Passport | Supplier evidence collection, battery and material traceability, and governed QR-code disclosures; the vendor also describes upstream traceability and selective sharing. | Can the pilot trace your priority fields to supplier evidence across the tiers you need, and demonstrate each audience view? |
| Siemens Battery Passport / DPP4.0 | Battery-passport creation and management, APIs and Catena-X integration; Siemens positions DPP4.0 as an enterprise DPP engine across products and systems. | Can your battery and supplier systems exchange the exact fields and identifiers you need, including operational updates? |
| AVL Digital Battery Passport | Structured product and lifecycle data, integration, role-based access, evidence governance, reporting and enterprise operations, according to AVL. | Can AVL map your battery model and unit-level lifecycle data to the Commission guidance and your existing data systems? |
| Spherity VERA | Spherity markets VERA for digital product and battery passports, with identity and trusted data exchange as part of its positioning. | Which components are included in the offered scope: passport authoring, hosting, identifier resolution, Registry submission, supplier collection and support? |
How to choose without buying a QR-code layer alone
Run the same pilot dataset through each shortlisted platform. Include one model with several variants, supplier declarations with missing values, a conflicting certificate, a serialised battery record, and a lifecycle update. Ask the provider to show where each value came from, when it was reviewed, what changed, and which role can see it. For sensitive supplier information, verify selective disclosure with an actual test account rather than accepting a slide describing privacy.
Then trace the data path end to end. Can the platform import from ERP, PLM, battery-management or product-lifecycle systems? Can suppliers submit structured fields and evidence without an onerous onboarding process? Can a user export their records and event history in documented formats? Can you change QR destinations without breaking persistent identifiers? What happens when a supplier, service provider or your contract ends? Keep these questions separate from the legal interpretation; software can support a control without making your organization compliant by itself.
- Match each battery SKU to the legal category, capacity threshold and placing-on-market date that apply.
- Map every required data point to a named internal owner, source system or supplier, evidence type and update trigger.
- Test public, business, legitimate-interest and authority access against the battery-specific rules and implementation guidance.
- Ask for a live demonstration of identifier creation, data-carrier resolution, Registry workflow and an API response; label any roadmap feature as planned.
- Compare total first-year cost and exit terms from dated quotes. Include integrations, supplier onboarding, per-passport or transaction charges, hosting and support.
A focused pilot that answers the hard questions
A useful pilot can be small: select one in-scope battery family, a realistic supplier set and a few representative passport records. Agree success measures before the vendor configures the demo. For example, measure the share of required fields with evidence, unresolved supplier requests, time to publish a corrected value, completeness of a unit-level record, and whether a person in each access role sees only the permitted information. Keep unknown data explicitly unknown; a polished sample passport can conceal how much manual work production requires.
Document gaps and assign them to the software, your source systems, suppliers, process owners or policy interpretation. Do not assume the EU Registry will repair missing content or that registration itself validates a passport’s data. A defensible purchase decision is one where your team can explain the complete route from a battery identifier to an evidence-backed value, its current version, the person responsible for it and the authorized recipients.
Sources and review context
Sources were reviewed for this editorial guide on 9 October 2026. Provider descriptions are attributed public statements. This guide does not report hands-on software testing or certify regulatory compliance. Check the current original source when a detail affects your decision.
How DPP Atlas reviews evidence