If you have been searching for custom battery passport solutions or battery passport platform development, you are probably a manufacturer or importer who has read Regulation (EU) 2023/1542, seen the date 18 February 2027, and concluded that something bespoke has to be built. That conclusion is understandable and, in most cases, wrong. Almost everything about the battery passport is already decided by regulation and standards. The only genuinely custom part is your data — where it lives, how messy it is, and how it gets into the shape the regulation demands.
This article separates the two, then compares the three ways to get there.
What is already decided for you
The content. Annex XIII of the Battery Regulation lists what a battery passport must contain. The Commission's guidance "Digital Batteries Passport – data points by category" (v3.2, 19 October 2026) turns that into 71 numbered data points, each labelled mandatory, applicable in certain cases, optional, or not to be filled for February 2027 — separately for EV, LMT and industrial batteries. You do not get to choose the fields. Download the full list as a checklist.
The access tiers. Article 77(2) splits the data into what the public sees, what persons with a legitimate interest (repairers, recyclers, second-life operators) see, what authorities and notified bodies see, and the dynamic state-of-health layer. Cathode chemistry, dismantling instructions and test reports are not public. This is fixed, although the implementing act that details access rights is still pending (now expected Q4 2026).
The carrier and the identifier. From 18 February 2027 the battery carries a QR code (Article 13(6)) that resolves to its passport. Every passport needs a unique identifier; GS1 Digital Link on a GTIN plus serial number is the convention the ecosystem has settled on.
The data structure. DIN DKE SPEC 99100:2025-02 organises the passport into seven clusters — identification, materials and composition, carbon footprint, due diligence, circularity, performance and durability, labelling and conformity. CEN/CENELEC JTC 24 has delivered the first EN standards for DPP systems, including EN 18222 for the interface layer; EN 18239 and EN 18246 were ratified in August 2026. EN 18216–18223 are cited for ESPR products (Decision 2026/1736), not for battery passports, and EN 18239/18246 are not cited — so none gives a presumption of conformity for a battery passport. Design with reference to them.
The registry. The EU DPP Registry has been live since 20 July 2026. It stores unique identifiers and commodity codes only; the passport data stays with the economic operator or its DPP service provider. The Commission published the Registry API and the battery data model on 30 October 2026, so that contract is now the target to build against.
The integrity layer. Signing each passport as a W3C Verifiable Credential is not written into the regulation, but it is what verification tools read and what lets anyone check a passport has not been altered. Building something proprietary here means building something nobody else can verify.
Every item on that list is a standard. "Custom development" of any of them means re-implementing a standard — and then maintaining your copy alone when the Article 77/78 delegated acts change it, which they will.
What is genuinely custom
This is the part that is yours, and it is where the time goes.
- Where your data lives. Cell supplier spec sheets as PDF, pack assembler bills of materials in Excel, cycle-life results from a test lab, nameplate data in an ERP, state-of-health values in a battery management system. None of it is in Annex XIII order.
- Your battery categories. An e-bike pack (LMT), a forklift battery (industrial) and a home storage unit (industrial, above 2 kWh) each get a different set of mandatory fields from the same 71.
- Your serialisation. The regulation wants one passport per battery. You have serial ranges, production batches and sometimes a module-and-pack hierarchy. Mapping model-level data onto unit-level passports is a design decision, not a form field.
- Your access policy. Who counts as a repairer or recycler for your products, and how they get a key.
- Your update cadence. Battery status changes (reused, repurposed, remanufactured, waste), state-of-health updates, supplier substitutions. Each one is a new passport version with an audit trail.
- Your systems. Label printing, RFID encoding, ERP or PIM synchronisation, and whatever your importer or distributor needs from you.
A good solution is custom in exactly these six places and standard everywhere else.
The three routes
| Build in-house | Self-service passport software | Done-for-you service | |
|---|---|---|---|
| Time to first compliant passport | 6–18 months | Days to set up, then as long as your data cleaning takes | Within 30 days of handing over your data |
| How the work is organised | An internal project plan, competing with your other priorities | Self-paced, by whoever owns the passports | Agile 14-day sprints, side by side with your team, until the data is complete |
| Who does the data work | Your engineers and a regulatory owner | Your team, in the vendor's forms | The provider, with your data contact answering questions |
| When the delegated acts change | You re-map, re-test and re-sign everything | Vendor updates the schema; your team re-fills the gaps | Provider re-maps and tells you what is newly missing |
| BatteryPass-Ready conformance | Your job to achieve and keep | Depends on the vendor | Provider's job |
| Registry submission | Build against the Commission's Registry API yourself, with a Service Account per operator | Usually included | Prepared and submitted on your behalf once your organisation is verified in the Registry |
| Best fit | OEMs with a platform team and many product lines | Companies with clean data and a person to own the passports | Importers and manufacturers without an IT department |
Building in-house is a legitimate choice for a large OEM that already runs a product-data platform and wants the passport inside it. For everyone else, the build route spends a year reproducing standards and leaves the actual problem — the data — untouched until the end.
Self-service software fixes the standards problem and leaves the data problem with you. That works if your data is already clean and someone on your team can own it. If the honest answer is "our data is in supplier PDFs and three spreadsheets", the software will be set up in a day and the passports will still not exist in six months.
The done-for-you route treats the data work as the deliverable. You send what you have; the provider maps it against the 71 data points for each battery category, flags every gap before anything is published, signs and hosts the passports, and re-maps when the rules move. This is the model PassportLab operates, and it exists because the data work is the part customers consistently underestimate.
Seven questions to ask any vendor — or your own team
- Which version of the Commission guidance do your data-point labels follow, and what happens when the next version lands? The answer should name a version (v3.2 today) and describe a re-mapping process, not a migration project.
- Do your battery passport exports pass BatteryPass-Ready? Fraunhofer IPK's test environment runs eleven scenarios plus data validation. It is voluntary, but it is the only public conformance check that exists.
- How is tiered access enforced? One passport with access control is right. Separate public and private documents will drift apart.
- Can you issue one passport per serial number from model-level data? If not, you will be doing that by hand.
- How are you preparing for the delegated act on DPP service providers? It is scheduled for Q2–Q3 2027 and will regulate whoever hosts your passports. A provider that has not heard of it is a risk.
- Whose registry account is used for submission? The economic operator's: its verified Registry organisation and Service Account. A provider submits only as the third party you authorise under Article 19(4) of Implementing Regulation (EU) 2026/1778, never with credentials of its own in your place.
- Where is the data hosted, and for how long? EU hosting, ten-year archival, and a passport that stays reachable until the battery is recycled.
So, do we build custom battery passport solutions?
No — and we would advise you not to buy one. The passport software already exists and already follows the standards above. What is custom is your data, and that is the work we do: map your supplier PDFs, ERP exports and test reports to every data point, flag the gaps, sign and host the passports, and keep them current as the delegated acts arrive.
If that matches your situation, book a readiness call and bring whatever data you have, however messy. If you first want to know whether your batteries are in scope at all, the two-minute battery check answers that. And the full checklist of the 71 data points is free.
Last reviewed: 29 October 2026. Regulatory status reflects the Commission's published guidance and schedule at that date.