Battery passport: the complete overview
Find out whether and when your battery needs a passport and which data it contains.

What is the battery passport?
The battery passport is a digital record that identifies an individual battery and documents its key properties: from the manufacturer's identification through performance and durability values to information for dismantling and recycling. It is accessed via a QR code on the battery that leads to an electronic view of the passport. Legally, the battery passport is anchored in Chapter IX of the Battery Regulation, which consists of Articles 77 and 78. Which data belongs in the passport and who may see it is governed by Annex XIII of the regulation.
The battery passport is also the EU's first mandatory digital product passport (DPP). The Ecodesign Regulation ESPR will later extend digital product passports to further product groups, but the battery passport follows its own rules from the Battery Regulation. This is more than a formality: Decision (EU) 2026/1736 has harmonised six DPP standards, but the associated presumption of conformity currently applies only to ESPR product passports and not to the battery passport. Using these standards remains voluntary.
For practical implementation there is still solid orientation. DIN SPEC 99100 sets out the data attributes of the battery passport. For the technical interface, EN 18222 is a dedicated API standard; its DIN version, DIN EN 18222:2026-09, has been published.
If you are right at the start, begin with our introductory guide to the battery passport.
What the passport is for
The duty is one thing, the purpose another. Recital 123 of the regulation names it expressly. The passport is introduced “to increase transparency along the supply and value chains for all stakeholders”. It should maximize the exchange of information and allow batteries to be tracked and traced. Four groups benefit from it. For manufacturers the view is worth it, because it shows which figure is needed for what.
- The public is to receive information about batteries placed on the market and their sustainability requirements. That is the public block every QR scan reveals.
- Reusers, second-life operators and recyclers need current data for handling. On top come tailored details such as the state of health. That is the level for persons with a legitimate interest.
- Buyers of a used battery should be able to judge residual value and remaining lifetime. The same goes for third parties acting on their behalf. Article 14(2) names exactly this purpose. It grants read access to the parameters in Annex VII, for stationary battery energy storage systems, LMT and electric vehicle batteries.
- For market surveillance authorities the passport should make the work easier. It does not replace or change their competences.
In practice: the passport is not a form for the authority. It is a data source for four different sets of readers. Knowing who needs a figure later leads to better decisions while filling it in. That applies to how precisely the composition is described, for example.
Who is affected?
The passport obligation of Article 77 covers exactly three battery categories:
- LMT batteries, i.e. batteries for e-bikes, e-scooters and other light means of transport,
- industrial batteries with a capacity above 2 kWh, which in the regulation's system also includes stationary energy storage,
- EV batteries, i.e. traction batteries for electric vehicles.
What counts is the placing on the EU market or putting into service from 18 February 2027. Where the battery was manufactured does not matter: responsible for the passport is the economic operator who places the battery on the EU market. This applies to manufacturers based in the EU as well as importers bringing batteries or battery-powered products in from third countries. For other batteries, such as classic portable batteries, Article 77 does not provide for a passport obligation.
Also important: the passport applies per battery, not per model. Every single battery placed on the market or put into service needs its own passport with its own identifier, reachable via that battery's QR code. This makes the battery passport a task for your series production processes, not just for the documentation department.
Details on deadlines and who is affected are in the guide EU Battery Regulation 2027: timeline.
The deadline: 18 February 2027, and what to do until then
18 February 2027 triggers several obligations at once. From that day on, affected batteries must have a battery passport when placed on the market or put into service, and carry the QR code; on our reading, registration in the EU registry is tied to that day as well, because Article 77(10) names no date of its own. By the same date, the member states must have designated their national registry administrators.
Realistically, you need to complete the following steps by the deadline:
- Clarify whether you are affected. Check per product line whether your batteries count as LMT batteries, EV batteries or industrial batteries above 2 kWh, and who in your supply chain is the economic operator placing them on the market.
- Take stock of your data points. Map your existing data against Annex XIII. The Commission's non-binding guidance “data points by category” of 19 October 2026 (version 3.2) lists 71 data points with their mandatory status per battery category and their legal basis, usually a provision of Annex XIII, and is the best working basis for this.
- Involve your supply chain. Many values, such as recycled content shares, come from suppliers. Clarify early who delivers which values and in which format.
- Plan your identifiers. The passport needs a unique identifier that works as a link. For the EU registry this identifier has to be in a URL format under JTC 24. It may not exceed 2000 characters.
- Bring the QR process into production. The QR code must lead permanently to the correct passport. It goes on the battery or, where nature and size do not allow or warrant this, on the packaging and accompanying documents. This concerns printing, application and the stability of the linked address.
- Prepare the registry verification. Only a verified economic operator, or a third party it has commissioned that is verified itself, may register. Verification currently runs through a qualified electronic seal or a qualified electronic signature under eIDAS and is valid for at most three years. Plan lead time for this.
- Watch the open legal acts. Implementing acts for the carbon footprint and for access via legitimate interest were still missing on 17 November 2026; the current status is on the page What the EU still has to deliver. If you anticipate requirements that have not yet been adopted, allow for later changes.
You will find a detailed step-by-step list in the Battery passport checklist 2027.
Data scope: Annex XIII explained
Annex XIII of the Battery Regulation defines which data belongs in the battery passport. Who may see which entries is governed by Article 77(2). There are three access tiers.
Public data
The public model data helps your customers see whether the battery suits their intended use. Rated capacity describes the amount of charge a fully charged battery can deliver under specified test conditions. For the electrical connection, the data includes minimum, nominal and maximum voltage: the lower limit, the value used to designate the model and the upper limit. It also includes the initial power capability and its limits. Where relevant, the respective temperature ranges accompany the voltage and power values.
For planning use, the passport states the expected number of full charge and discharge cycles and the reference test, meaning the test procedure used for this. If a warranty covering lifetime in years is offered, its duration is stated. Electric vehicle batteries also have a capacity threshold: the proportion of the original charge capacity at which the battery is considered exhausted. For storage, the data also states the temperature range the battery can withstand when not operating, together with the test procedure used.
Round-trip efficiency helps compare energy losses: it is the ratio of energy delivered during the test to the energy needed to recharge the battery. It is stated initially and at half the cycle life. To interpret the measurements, the data also includes the internal resistance of the cell and pack, meaning their opposition to current flow, and the lifetime test’s C-rate: the charging or discharging current relative to rated capacity. These entries concern the battery model; Annex XIII point 1 defines the full public scope.

Data for persons with a legitimate interest
Annex XIII points 2 and 4 are accessible to persons with a legitimate interest (Article 77(2)(c)). Point 2 includes the detailed composition and dismantling information, point 4 the data on the individual battery. Who counts as a person with a legitimate interest, and which information they may use to what extent, is to be set out in an implementing act under Article 77(9). Its deadline was 18 August 2026; whether it has been adopted since is shown on the page What the EU still has to deliver.
Data for notified bodies, market surveillance and the Commission
Points 2 and 3 are accessible to notified bodies, market surveillance authorities and the Commission (Article 77(2)(b)). Point 3 holds exactly one thing, the results of the test reports, and only these bodies see it.
DPP Hero assigns each of its 128 fields to an access level: 82 public, 28 restricted, 5 for notified bodies, market surveillance authorities and the Commission and 13 internal. The public passport page returns only public values.
Data that grows with the battery
A second distinction runs across the access levels. Annex XIII point 4 holds data on the individual battery that changes over its life. That covers performance and durability values at placing on the market and at every change of status, the state of health under Article 14 and the status in five stages: original, repurposed, reused, remanufactured or waste. Added to those are the data from use such as charging cycles, negative events, operating temperature and state of charge. For state of health and expected lifetime, Annex VII names the parameters in detail. Since 18 August 2024 the battery management system of stationary battery energy storage systems, LMT and electric vehicle batteries must keep them current under Article 14(1). The remaining entries, accidents or state of charge for example, are not in Annex VII. They belong in the passport, not necessarily in the battery management system.
These entries belong to the second level. They are not public but reserved for persons with a legitimate interest. Under Article 77(4) the economic operator placing the battery on the market must keep them current. They may authorize others in writing, the responsibility stays with them. What the battery management system has to provide and who may read it is in the section Stationary storage.
Three particularities are worth knowing. First, the Commission's non-binding guidance of 19 October 2026 (version 3.2) explicitly defers some data points (“Not to be filled/displayed as of February 2027”): the carbon footprint declaration and label, until the implementing act on the format is in place, and the responsible sourcing information, which it requires only from 18 August 2027. Second, the recycled content shares for cobalt, lithium, nickel and lead also stay empty at the start; they follow Article 8 and its delegated act. Third, material composition (data point 16) and rated capacity (data point 25) stay empty because the same data is already required under other data points.
On the carbon footprint in plain terms: for the CO2 obligations of the Battery Regulation, the later of two points applies in each case, the date named in the law or 12 or 18 months after the methodology act and the format act enter into force. On 17 November 2026 both were missing, so the obligations had not been triggered; the current status is on the page What the EU still has to deliver.
QR code: the marking on the battery
Access to the battery passport runs through a QR code. It is printed or engraved visibly, legibly and indelibly on the battery; where the nature and size of the battery do not allow or warrant this, it goes on the packaging and the accompanying documents. This is required by Article 13(6) and (7), Article 77(3) and Annex VI Part C of the regulation, likewise from 18 February 2027. The code must lead to the passport of exactly that battery. Annex VI Part C requires strong color contrast and a size readable by common phone readers, Article 77(3) a unique identifier under ISO/IEC 15459-1 to 15459-6 or equivalent standards.
In practice that means two things. First, the QR code belongs in your production process, because every single battery gets its own code, as a rule directly on the battery. Second, the address behind the code has to stay stable across the lifetime. A passport whose link dies after a website rebuild misses the point. Plan the URL structure for the long run; what that means for building it yourself or using software is in the section Implementation. For the registry the UPI rule applies: URL format, at most 2000 characters.
The EU registry for battery passports
Alongside the passport itself, the EU requires registration in a central Commission registry.
Implementing Regulation (EU) 2026/1778 has been in force since 6 August 2026. It describes the registry as a directory: stored are identifiers, commodity code and a digital checksum (hash), not the passport contents themselves. The regulation contains no technical rules for the structure of the data, known as schemas.
On 17 November 2026, battery passports could not yet be registered there because the semantic catalogue for batteries was missing; the current status, with deadlines and sources, is on the page What the EU still has to deliver.
For registration itself: only a verified economic operator may register. Verification currently runs through a qualified seal or a qualified signature under eIDAS and is valid for at most three years. Third parties may register on an operator's behalf if they are verified themselves; nobody can take over the economic operator's own verification. A DPP service provider, by the way, is not a defined actor under the Battery Regulation. The registry does keep a list of the verified digital product passport service providers registered there (Implementing Regulation (EU) 2026/1778, Article 3(f)); that is a check of identity, not a certification of the software.
What is uploaded is the unique identifier of the battery (Article 77(10)). The paragraph names no date of its own for it; because the passport duty starts on 18 February 2027, we assume that affected batteries must be registered from that day when placed on the market or put into service.
How the registry works in detail is covered in the guide EU battery passport registry.
The key deadlines
The second life: repurposing, reuse and the new passport
A battery rarely ends where it was sold. A vehicle pack becomes a home storage unit, a faulty module becomes a remanufactured one. The Regulation knows these routes, names them individually and attaches the passport to them.
- Article 3 distinguishes four operations. Point 29 is preparing for re-use, point 30 preparing for repurposing. Point 31 is repurposing itself, point 32 remanufacturing. Repurposing means: the battery is not waste, but is used for a purpose other than the one it was designed for.
- Article 77(7) draws the consequence. It covers batteries prepared for re-use or repurposing, repurposed or remanufactured. For them responsibility passes on. It rests with the economic operator who placed the battery on the market or put it into service. These batteries need a new passport, linked to that of the original battery.
- The status sits in the passport itself. Annex XIII point 4(c) requires the entry “original”, “repurposed”, “reused”, “remanufactured” or “waste”. Once the battery becomes waste, responsibility passes on. It then rests with the producer, the producer responsibility organisation or the selected waste operator.
- At the end comes deletion. Under Article 77(8) the battery passport is deleted once the battery has been recycled.
For residual value, Article 14(2) is the decisive lever. Anyone who has lawfully acquired a battery gets read access through the battery management system to the parameters in Annex VII, among other things to assess residual value, remaining lifetime and the scope for further use. This duty has applied since 18 August 2024 and covers stationary battery energy storage systems, LMT batteries and electric vehicle batteries.
In practice: do not plan the passport as a one-off handover on the day of sale. Plan it as a record that survives a change of status. It has to connect for the next operator.
What the passport delivers beyond the obligation
The compulsory part is not in dispute. Less discussed is that the same data set answers questions companies already have.
- After-sales and service: the QR code leads to a unique identifier of the individual unit. Seeing version, build state and safety notes at once saves queries and wrong parts.
- A direct line to the end customer: anyone who scans the QR code reads the information you publish for your battery.
- Evidence instead of claims: recycled content, carbon footprint and responsible sourcing sit in the public block. Documented properly, you point to a source in a purchasing meeting instead of a brochure.
- Second-hand market: only sight of state of health and usage history makes residual value and further use assessable.
Soberly put: these effects do not arrive on their own. They need maintained data. The passport is a shop window, and an empty one looks worse than none.
What sits alongside the Regulation
Guidance documents, standards and technical models have grown around the battery passport. They help with interpretation but do not replace the text of the Regulation.
- The Battery Pass consortium spelled out the fields from Annex XIII, funded by the German Federal Ministry for Economic Affairs and Climate Action. The Content Guidance last appeared in December 2023, a Technical Guidance in 2024, plus a software demonstrator. DIN SPEC 99100 emerged from it, published in January 2025 (edition 2025-02). The project ended in March 2025.
- The administration shell under IEC 63278-1:2023 comes from the Industry 4.0 world. In English it is the Asset Administration Shell. The standard describes it as a standardized digital representation of an asset. In everyday terms that is the digital twin. The Battery Regulation does not prescribe it.
- Industry data spaces such as Catena-X, the data space of Catena-X Automotive Network e. V. with the open reference building blocks of the Eclipse project Tractus-X, organise exchange between companies. A company already connected there will want to carry the passport there too; it is not a precondition for the passport obligation.
The yardstick stays Article 77(5): open standards, an interoperable format, transferable without vendor lock-in. On top: machine-readable, structured and searchable. Measuring against that avoids betting on one ecosystem.
Stationary storage
Which storage systems are covered
A stationary battery energy storage system is an industrial battery with internal storage, regardless of where or by whom it is used (Article 3 point 15). It needs a passport if its capacity is more than 2 kWh (Article 77(1)):
- home storage above 2 kWh, such as PV storage for private households; a unit of exactly 2 kWh is not covered yet,
- commercial and industrial storage above 2 kWh,
- grid-supporting large and containerized storage (BESS) above 2 kWh,
- uninterruptible power supplies (UPS) and communications infrastructure as industrial batteries above 2 kWh; they are storage within the meaning of point 15 only if they meet that definition.
Portable batteries, for example in laptops or tools, need no passport. From 18 February 2027, however, they too carry a QR code that leads to their information (Article 13(6)).
Existing installations, replacement and expansion
The duty applies to batteries placed on the market or put into service from 18 February 2027; installations already in place need no retroactive passport. Article 77(1) attaches not to the installation but to the individual battery. A replacement or augmentation rack made available on the Union market for the first time in 2028 is placed on the market in 2028 and needs a passport if it is above 2 kWh, even if the installation itself is older. The existing installation gets no passport from this. For repurposed and remanufactured batteries Article 77(7) applies, as described above under “The second life”.
At what level the passport sits
With the battery that is placed on the market. Article 3 defines the battery as a device consisting of one or more cells, modules or packs. If you deliver a finished system, the passport hangs on that system, not on every cell. If you deliver modules that someone else assembles, your modules need the passport if each is above 2 kWh; the system builder creates their own for their product. Settle this before capturing data, because it decides how many passports you keep and the level at which you collect condition data. The data attributes are explained in the guide DIN SPEC 99100.
Who is responsible for the passport
Responsible is the economic operator placing the battery on the market (Article 77(4)): the manufacturer or the importer, also with bought-in cells. They ensure the data is correct, complete and current, and may authorize other operators in writing to act on their behalf. Under Article 3 point 33 a manufacturer is whoever manufactures a battery, or has it designed or manufactured, and markets it under their own name or trademark or puts it into service for their own purposes; placing on the market is the first making available on the Union market. Both fit the system integrator who assembles modules and racks into a storage system above 2 kWh and delivers it under their own name: they owe the passport for that system, while the cell manufacturer owes it only for what they place on the market themselves.
Which condition parameters apply
The parameters for state of health and expected lifetime are set out in Annex VII. Part A names the same ones for stationary battery energy storage systems and LMT batteries: remaining capacity, where applicable power capability and round trip efficiency, the evolution of self-discharge and where applicable ohmic resistance; for electric vehicle batteries it names the state of certified energy (SOCE). Part B names for the lifetime the date of manufacture and where applicable of putting into service, energy and capacity throughput, harmful events such as deep discharges and time spent at extreme temperatures, and the number of full equivalent cycles.
The non-binding Commission guidance lists the condition parameters that Part A names for stationary battery energy storage systems and LMT batteries as data points 62 to 66: for industrial batteries only for stationary battery energy storage systems with a battery management system, and as mandatory for LMT batteries. For electric vehicle batteries the state of certified energy (SOCE, data point 61) is mandatory instead.
The regulation names no fixed update frequency. Article 77(4) requires the data to be current. For the performance values Annex XIII point 4 names the change of status, for the operating conditions regularly recorded values. The passport carries the round trip efficiency twice: publicly as a model value (Annex XIII point 1(n), explained above under “Public data”) and restricted as the remaining value of the individual battery. Who may see these data is described above under Data that grows with the battery.
What the battery management system has to provide
Since 18 August 2024 stationary battery energy storage systems, LMT and electric vehicle batteries must hold current data on state of health and expected lifetime under Annex VII in the battery management system (Article 14(1)). Read access to these parameters goes to whoever has lawfully acquired the battery, at any time and without discrimination. That includes independent economic operators, waste operators and third parties acting on their behalf; the intellectual property rights of the battery manufacturer stay protected.
The access serves three purposes: making the battery available to independent aggregators or market participants for energy storage, assessing the residual value, the remaining lifetime and further use on the basis of the state of health, and facilitating preparation for re-use or repurposing as well as repurposing and remanufacturing. The regulation thus prescribes data access, not a market value.
Alongside the passport stands supply chain due diligence, a separate duty with its own deadline from 18 August 2027 (Article 48(1)). Article 47 exempts whoever stays below the turnover threshold named there and belongs to no group that exceeds it, and whoever re-uses, repurposes or remanufactures batteries already placed on the market. An operator is covered only if they place the storage system on the market themselves or are the first to use it without it having been placed on the market before (Article 3 point 18), for example as a manufacturer who manufactures it, or has it designed or manufactured, and puts it into service for their own purposes (point 33). On registration see The EU registry for battery passports.
Implementation: build it yourself, software or service provider
Nowhere in the Battery Regulation does it say that you must buy software for the passport. The regulation does not prescribe software, it prescribes outcomes. How you achieve these outcomes is up to you: a self-developed system on your own infrastructure meets the regulation just as well as a purchased solution.
It does prescribe properties, the same for every route. The passport may be stored by the responsible economic operator or by whoever is authorized to act on their behalf (Article 78(c)); building it yourself and using a service provider are therefore both permitted. The yardstick for format and portability is set by Article 77(5), as described above under “What else stands next to the regulation”.
We build battery passport software ourselves and still say openly: sometimes building it yourself is the more sensible choice. So compare by type and by points you can verify yourself, not by promises; which EU building blocks are still missing is on the page What the EU still has to deliver.
Four routes at a glance
Each route has its legitimate place, none fits every situation. What matters is which one suits your volumes, your budget and your internal capacity.
- Platform with project business. The strengths: integration into enterprise resource planning (ERP) and product lifecycle management (PLM) systems, individually tailored data models and a project team that accompanies the rollout. The limit: the rollout is an IT project with requirements workshops and interface work.
- Agency or service provider. You commission an agency or a service provider that builds and maintains the passport for you on third-party or in-house technology; that helps when nobody internally has capacity for the topic. Responsibility for the passport stays with you.
- Building it in-house. Your own development team builds the passport as part of the product IT: full control and an exact fit with existing systems, in return you take on the upkeep of the requirements permanently. What that involves is set out below under the six tasks of a self-built system.
- Self-service software. You create an account, enter the data in a guided editor and publish the passport yourself. The strength: testable without an appointment. The limits: no individual project support and no consulting; data collection from suppliers and the responsibility for the content remain with you, and heavily deviating special processes hit the limits of the standard.
What a self-built system has to deliver
If you build it yourself, you are not building a form or a product page, you are building a system with six tasks. Each of them is doable, but each of them means permanent operation.
- A data model per battery type. The required fields differ by battery type: an EV battery needs different information than an LMT battery or a stationary storage system. A self-built system therefore needs a type-dependent data model with its own required-field logic per type, otherwise you check completeness by hand permanently.
- Separate access levels server-side. Merely hiding restricted fields in the interface is not enough: what the server delivers can be retrieved. A self-built system must therefore decide, at the latest before the server responds, which level the caller sees, and design the access check so that it can be adapted to the implementing act under Article 77(9) without rebuilding the system.
- QR codes that last for years. The QR code sits on the battery or, where its nature and size do not allow or warrant this, on the packaging and the accompanying documents. The address behind it must not break over the entire lifetime, and the passport stays available even if the responsible economic operator no longer exists (Article 78(e)). The link has to survive domain renewals, hosting migrations, company renamings and system replacements unscathed. If you build it yourself, you make this availability promise yourself, including backups, monitoring and an answer to the question of who is responsible when the person who built the system leaves the company.
- Schema validation instead of visual checks. A self-built system should validate every passport against a machine-readable schema before publication, for example against the Battery Passport Data Model.
- Versioning and evidence. A battery passport is not a one-off document. Data changes through corrections, repairs and new mandatory information. Article 78(g) requires authenticity, reliability and integrity of the data, point (h) a high level of security and privacy and the prevention of fraud. One way there: a history showing which version was published when and who changed it, a cryptographic signature per published version and a tamper-evident change log, also when market surveillance asks years later. Whether you use verifiable credentials for that, meaning digitally verifiable proofs, or something else is up to you; the Battery Regulation does not mention the term “verifiable credentials” once, it requires the result.
- Watch the open legal acts. Building it yourself needs a named person tracking new legal acts, guidance versions and schema changes. All six tasks apply from the first passport onwards.
Where the data comes from
A self-build calculation that only counts form, database, passport page and QR code leaves out gathering the data from systems already in the house: for example master data and identifiers from the ERP, text and images from the product information management (PIM) system, technical values and bills of materials from the PLM, test reports and life cycle assessments from test houses and service providers. The report under Article 52(3) is published by the economic operator, who is responsible for it, if they fall under the due diligence obligations (from 18 August 2027, Articles 47 and 48); they may cooperate with others for it (Article 48(4)).
The work does not end with the initial filling. Under Article 77(4) the economic operator keeps the data accurate, complete and up to date, and Annex XIII point 4 requires the performance values at placing on the market and at every change of status.
Nobody outside your company can give you a reliable estimate of the duration in months. What can be estimated are the items: the 71 data points of the Commission's non-binding guidance, most of them per battery model, the rest per individual battery, plus the six tasks of a self-build, the number of your models and battery types and the number of source systems. If the QR code is applied in manufacturing, count backwards from the day the first affected battery leaves the line with its marking, not from the deadline itself.
The public block under Annex XIII point 1 pulls data from several sources, among them Annex VI Part A, the declaration of conformity under Article 18 and the recycled content documentation under Article 8(1). Plan procurement separately from the tool and start with the entries that have to come from outside; this collection arises on both routes.
Ask every provider how the data gets from your existing systems into the passport, for example from PIM, ERP or SAP, and have them show you whether there is an open interface and a table import. With DPP Hero those are the REST API (Scale and up) and the CSV import (Business and up). Ready-made connectors for individual products do not exist, and we do not claim otherwise.
One example is the carbon footprint. Annex II lays down that the future method builds on the Product Environmental Footprint (PEF) method and the related Product Environmental Footprint Category Rules (PEFCR). The calculation runs “on the basis of the bill of materials, energy and auxiliary materials” of a specific plant for a specific model. Electronic components such as the battery management unit and the cathode materials have to be identified precisely, because they can make the largest contribution. The basis is company-specific primary data from the plants. DPP Hero does not calculate the carbon footprint itself; the value comes from your life cycle assessment and is carried in the passport.
Where building it yourself holds up and where it tips over
A self-built system is a realistic option when three things come together: a single battery model or very few models, data that rarely changes, and an in-house developer team that takes permanent responsibility for operations. Then the passport is a manageable undertaking: one data model, one public page, one stable link, one change process.
It becomes critical in three places. First, model variety: every additional battery type brings its own required fields, every additional model its own data and maintenance. Second, suppliers: as soon as cell, material or manufacturing data comes from third parties, you need a structured supplier process with checks and tracking. Third, movement in the standards: a new guidance document, an implementing act or a schema change can mean development work. The one-off project then turns into a permanent product with its own task list.
In between lies a gray area: a company with two or three models, a small developer team and supplier data in motion. If the battery passport gets a fixed owner in your company with a budget and a stand-in arrangement, building it yourself can work. If it remains a side project of a single person, it becomes a risk on exactly the day that person does something else.
There are no serious flat figures for either route, the real cost sits in maintenance. Calculate both routes over the same period of several years, include the staff hours and the cost of waiting for the self-built system, and count GS1 identifiers, marking and data collection alongside the software; the items are explained in the guide Battery passport costs, our prices are on the pricing page.
Criteria you can verify yourself
Whatever the route: take the list into every provider conversation, or better, check the points yourself on the product before a conversation is needed at all.
- Type-specific mandatory fields. The mandatory data depends on the battery category; the Commission's non-binding guidance lists some data points only for stationary battery energy storage systems, and condition data under Article 14 exists only with a battery management system. Check whether the editor shows different fields per battery type or whether all types get the same form.
- Blocking schema validation. A passport export should be validated against a published schema, for example the Battery Passport Data Model v2.0. What matters is whether the software actually blocks faulty data or exports it anyway. Do not ask whether validation happens, try it out with a deliberately incomplete data set.
- Access levels verifiable in the data response. Article 77(2) separates public fields, fields for persons with a legitimate interest and fields for notified bodies, market surveillance and the Commission. Look at the responses the public passport page loads from the server (browser developer tools, Network tab), not only at the page source: restricted values must not arrive there in the first place. If they are merely hidden in the display, the separation is no separation.
- Export paths without lock-in. Can you get out again at any time with all your data? Demand machine-readable exports following a published schema in addition to the PDF, ideally via API as well. Also ask under which address the printed QR codes run and what happens to published passports after cancellation.
- Handling of open regulation. Does the provider name open points as open? Ask how they plan for EU building blocks that are still open; which ones those are is on the page What the EU still has to deliver. Serious is whoever names the open points openly.
- Verifiability and signature. Can a third party check that a published passport is unchanged? Look for signatures, a publicly accessible verification route and a version history. They are one way to authenticity, integrity and security of the data under Article 78(g) and (h).
- What may the provider do with your data? Authorized operators may not sell, re-use or process the data beyond what is needed for their storage and processing services (Article 78(d)). Ask what the provider uses your data for.
- Testability without an appointment. Can you create an account without a sales call, play through a passport all the way to publication and see the prices? If a product can only be seen behind a demo booking, check the other criteria especially thoroughly.
Start with the last criterion: if you can test a product without an appointment, you check the others yourself. With DPP Hero you test the editor, publishing and the exports with a free passport; CSV import and share links come with Business and up, the REST API with Scale and up. If terms come up in the providers' answers that you cannot place, look them up in the battery passport glossary.
A seal does not replace this check. There is no legally required certification or official seal; voluntary private audits are offered. Ask who audits and against what.
Which route fits you?
Before comparing providers, it pays to look at what you work with today. Four of the following questions each lead to one route, the fifth helps if you cannot clearly answer yes to any of them:
- Do you need passports for many product categories beyond batteries? If yes, and if budget and time for an integration project are available, the arguments favour a platform with project business. Weigh the project lead time realistically against the 18 February 2027 deadline.
- Does nobody internally have time for the topic? Then a service provider can take the work off your hands. Clarify in writing beforehand in which format you get your data back and what later changes cost. Nobody can take your eIDAS verification as an economic operator off your hands.
- Is the battery passport a core part of your product? If your business model is built on the passport and a development team is permanently assigned to it, building in-house can be the right route. Then check it against the six questions below.
- Do you want to start yourself with a manageable range of models before the deadline? Then self-service software is the direct route: start today, complete the data step by step, publish. The battery passport checklist helps you sort out your data situation.
- Still undecided? For the decision itself: an afternoon with a real account says more than any brochure, and at DPP Hero the first passport is free. Test before you commission a long comparison.
Six questions before building it yourself
If you want to build it yourself, answer these six questions in writing and honestly.
- How many battery models and types do you have? One model with stable data speaks for building it yourself. Several battery types mean several sets of required fields, several models more data and ongoing maintenance.
- Do you have a developer team with permanent responsibility? This is not about the project but about operations until well beyond 2030. If the responsible person leaves, the passport must keep running.
- Who watches the open legal acts? CO2 methodology, the access act under Article 77(9), registry interfaces: someone has to follow what the EU decides on them and build in the changes.
- Do suppliers contribute data? As soon as cell or material data comes from third parties, you need a structured supplier process with checks and status, not just email attachments.
- Can you ensure QR availability over the battery's lifetime? Domain, hosting, redirects, backups: the printed code must still lead to the passport many years from now.
- What does a year of delay cost you? Calculate the self-built route realistically through to 18 February 2027, including testing and corrections. The deadline does not move because an internal project stalls.
If the majority of your answers land on the demanding side, building it yourself is not wrong. But it is then a product you operate permanently, not a project you complete. You do not have to make this decision final: the middle path below keeps both routes open.
The middle path: start with software, keep your data
Building it yourself or software is not a one-way street, as long as two conditions are met: your data belongs to you, in open formats and exportable, and the printed QR codes point to an address you control. Then you can start with software, gain experience with the data model on real passports and still build it yourself later, without starting from scratch. Getting started needs no meeting, and on your own data you see whether the structure holds.
Common mistakes in preparation
- Misjudging the CO2 obligation. The carbon footprint declaration is often presented as a duty in force. In fact the carbon duties were not triggered on 17 November 2026, for lack of a methodology and format act; the current status is on the page What the EU still has to deliver. The Commission's non-binding guidance classes carbon declaration, carbon label and responsible sourcing as not to be filled for February 2027.
- Trusting a seal or certificate. There is no official certification system for battery passport software or DPP service providers, and no GEFEG or BatteryPass seal either. Read advertising claims with seals accordingly critically and check concrete evidence instead, such as schema validation of the exports.
- Overestimating harmonised standards. Decision (EU) 2026/1736 harmonises six DPP standards, but the presumption of conformity applies only to ESPR product passports. For the battery passport it currently has no legal effect.
- Promising fixed registry dates. Battery passports could not yet be registered in the EU registry on 17 November 2026, because the semantic catalogue was missing; the Commission's user guide gave no date, and the current status is on the page What the EU still has to deliver. Plan the connection. But do not tie internal promises to EU building blocks that do not exist yet.
- Underestimating identifiers and verification. The UPI requirement with URL format and at most 2000 characters, the eIDAS verification valid for at most three years, and the question of who in your supply chain is the registering economic operator: all of this needs lead time and is not something for the last weeks before the deadline.
- Ignoring the access tiers. Publishing all passport data unfiltered misses the logic of Annex XIII, and holding everything back does too. The separation into public data, data for persons with a legitimate interest and data for notified bodies, market surveillance and the Commission belongs in the data model from the start.
- Waiting for full legal certainty before collecting data. Individual points still depend on implementing acts, but the large majority of the 71 data points is settled. Anyone who only starts collecting supplier data in 2027 has hardly any buffer left for coordination.
What implementation can cost and which items to budget for is covered in the guide Battery passport costs.
About this page
This page is run by DPP Hero: with our self-service software you create battery passports yourself, without project business, consulting or appointments; anyone looking for an accompanied rollout is better served by platforms with project business or by service providers. A type-specific editor guides you in 7 steps through the required fields of 5 battery types; the data structure follows DIN SPEC 99100. Before publication the GS1 identifiers, the organization's required data and all 7 steps are checked, and JSON exports are validated against the schemas of the Battery Passport Data Model v2.0 with blocking checks; empty lists that the data model leaves open are allowed. Passports are published as a public page with QR code; afterwards you export them as JSON and PDF. Share links for suppliers and the CSV import come with Business and up, the REST API with Scale and up. You can take your data with you at any time. For printed codes to keep working after a switch, they have to run under your own domain (Business and up). If you would like to try it: prices are on the pricing page. In the blog we track new developments as they happen.
Frequently asked questions
Articles and fundamentals
Go deeper into duties, deadlines, registry and costs without searching elsewhere.
Guide
What Is a Battery Passport? Complete Guide
Read articleRegulation
EU Battery Regulation 2027: Timeline & Deadlines
Read articleGuide
Battery Passport Checklist: 10 Steps for 2027
Read articleRegulation
The EU Battery Passport Registry: A Manufacturer's Guide
Read articleIndustry
Battery Passport Costs: Full Breakdown
Read articleTechnical
Battery Passport Data Access: What Becomes Public?
Read articleGuides by use case
Find the starting point that fits your role and your product.
DIN SPEC 99100 software
The standard behind the battery passport and how software implements it.
Battery passport for e-bikes and e-scooters
What applies to LMT batteries, regardless of capacity.
Battery passport for importers
Your 12 obligations under Art. 41, from verification to documentation.
DPP software
The bigger picture: digital product passports under the ESPR.
Supply chain due diligence
Who the duty applies to and which supplier data you need.
Battery passport or digital product passport
Which passport your product needs, and why there can be two.
Ready for the battery passport?
Create your first battery passport for free, without a separate IT project.