Which products need a passport? What should you ask suppliers for? And how can you prepare without disrupting your product launch?
Your next battery model is almost ready for production. The specifications are finalized, suppliers are confirmed, and the launch date is approaching. But if someone asked whether its Digital Battery Passport was ready, would you know where to start?
For product teams, preparing for Digital Battery Passports means more than understanding which products are covered. It means knowing where the required information comes from, identifying gaps before they affect a launch, and making sure there's a process for managing changes after the battery is sold.
These are some of the challenges we see in our work with battery manufacturers. And although compliance and IT have important roles, many of the decisions depend on product knowledge.
So how can product teams turn these requirements into something manageable?
Which battery models should you prepare first?
Start by mapping your battery models against the covered categories. Then identify which in-scope batteries are expected to be placed on the EU market or put into service from 18 February 2027, and ask your compliance team to confirm applicability and responsibility.
Under Article 77 of the EU Battery Regulation, Digital Battery Passports will be required for electric vehicle (EV) batteries, light means of transport (LMT) batteries, and industrial batteries above 2 kWh.
However, knowing the categories is only the beginning.
A manufacturer may produce several battery models, offer different configurations, or supply batteries that become part of larger systems. In these cases, understanding which finished battery needs a passport is not always straightforward.
We've seen this come up in customer discussions where manufacturers were preparing different battery categories for separate product launches. Before moving to technical implementation, they needed to clarify which products were covered, when they would enter the market, and who was responsible for them.
A practical way to approach this is to build a simple product scope register.
For each battery model, record its category, capacity, weight (mass), relevant variants, intended market, launch date, and the economic operator responsible for placing it on the market. Add a column for compliance to confirm whether the passport requirement applies.
For example, if your company produces an industrial battery model with several capacity variants, don't assume that all variants can be treated identically. Record their configurations and specifications so compliance can assess the scope and the team can determine which information can be shared.
It’s important to distinguish between battery-model information and information linked to an individual battery. Some model-level information may be reused, while the applicable battery identifiers and passport scope need to be confirmed for the product.
The European Commission's Battery Passport FAQ further clarifies how the requirement applies to finished batteries made up of multiple packs or modules.
What should you have at the end? A confirmed list of covered models and variants, the launches they relate to, and the responsible economic operators.
This becomes the starting point for data collection and technical implementation. Without it, teams risk preparing information for the wrong products or discovering missing models too late.
How do you find the data you already have, and what's missing?
Take one representative battery model and map each applicable passport data field to its source, owner, and update process.
Product teams often assume that preparing passports will require collecting a large amount of new information. In reality, some of it may already exist in engineering documentation, ERP systems, manufacturing records, or supplier files.
The difficulty is that the information wasn't necessarily collected with a Digital Battery Passport in mind.
We've seen this in discussions with manufacturers looking to automate passport creation. In one case, the customer wanted static information to be pre-filled at model level, instead of manually entering identical specifications for each individual battery.
That sounds like an IT task, but the first question was actually about the product: which specifications are shared, which vary between models, and where is the authoritative version of that information?
To answer these questions, start with a basic data map.
These are illustrative data sources, not a complete list of mandatory fields. The applicable data points depend on the battery category and regulatory requirements.
The Commission's Battery Passport data-point guidance can be used alongside Annex XIII to identify which fields are required, conditional, or not yet applicable.
Once the required fields are identified, give each one a status: available and verified, available but needing review, missing, or not yet applicable.
This is where the exercise becomes useful. If a field is missing, you can identify who needs to provide it. If the information exists in several systems, you can agree on which source is authoritative. And if the same data applies to multiple models, you can determine how to reuse it without repeated manual entry.
A missing field should be assessed against the requirements that apply to the battery and the relevant date. Some information generated during a battery’s use may not be available when it is first placed on the market. Don’t assume it can be deferred: confirm which information is required at that stage, and what update obligations apply later, against the current Regulation and Commission guidance.
The result should be a data gap tracker with an owner and next action for every unresolved item, not simply a list of information the company hopes to collect.
What should you do when suppliers don't have the information you need?
Make supplier requests specific to the product, define the evidence needed, and establish a process for handling missing or changing information.
This is often more effective than sending suppliers a general request for Digital Battery Passport data.
A supplier may hold information about a particular component but not know which of its specifications are relevant to the finished battery passport. Another supplier may have the information but only in a technical document or a different format.
Product teams can help procurement connect these requests to the actual product. The exact fields should first be confirmed against the applicable passport requirements, this gives the supplier a defined task and makes it easier to identify missing information.
But what if the supplier still can't provide it?
First, establish whether the information is mandatory for that battery and launch date. If it is, work with procurement and compliance to identify an alternative source, resolve the missing information, or escalate the issue before the battery is placed on the market. Required information cannot simply be postponed because a supplier is unprepared.
If the field is conditional or relates to an obligation that applies later, document that decision and include it in the longer-term data plan.
The collection method can also be adapted to the supplier. Not every company needs an API connection. Structured templates, spreadsheets, and document uploads may be sufficient, depending on the information and workflow.
In our experience, the most useful improvement is often making supplier requests clearer before introducing more complex technology.
Not every supporting document collected from suppliers needs to appear directly in the Digital Battery Passport. Some information may be needed to calculate, verify, or support passport data rather than being published as a passport field.
How can you make sure Digital Battery Passports don't delay a launch?
Add a Digital Battery Passport readiness check to the product launch process, and test the complete workflow before production or release.
Most product teams already use launch checkpoints to confirm that specifications, documentation, manufacturing, and other requirements are ready.
We see that Digital Battery Passport preparation can follow the same approach.
In one of our implementation discussions, the customer planned to begin with one or two battery models using manual or batch imports before expanding toward a more automated solution.This can be a practical way to test the process while identifying gaps in product data and system connections. It doesn't change the obligation to provide passports for all covered batteries when the requirement applies.
For product teams, a useful launch-readiness check would cover six things:
- Scope confirmed: The model and relevant variants have been assessed, and compliance has confirmed the applicable requirements.
- Required data available: Mandatory information has been collected and reviewed, with unresolved gaps escalated.
- Individual identification ready: Each covered battery can receive its required unique identifier, and the QR-code process fits into manufacturing and labeling.
- Passport tested: A representative battery record can be created and accessed through its QR code, with the applicable public and restricted information handled correctly.
- DPP Registry requirements checked: Confirm with compliance who is responsible for any required Registry-related steps, what information must be provided, and when. Creating and hosting a passport and meeting any applicable DPP Registry requirements are separate considerations.
- Maintenance owner assigned: The company knows who will manage relevant corrections and updates after launch.
The fourth check is particularly important. A passport may appear complete in a spreadsheet, but that doesn't confirm that the identifier is correctly connected, the QR code works, or the intended users can access the appropriate information.
We find that testing with a representative battery before scaling the process often helps identify these issues early.
And manufacturers don't necessarily need to automate everything before they begin. Manual entry or batch imports can be appropriate starting methods if they reliably support the required information and production volume.
For larger-scale operations, however, connecting passport creation to existing systems may reduce repetitive work and make the process easier to maintain.
The goal is to choose an approach that works for the products being launched, rather than waiting for a perfect technical setup.
What should happen when a supplier, component, or battery model changes?
Product changes should trigger a review of the information affected, so the company can determine whether its Digital Battery Passports need to be updated.
Let’s keep in mind that creating the first passport is only part of the work. Have a think about a product team changing a component supplier after a battery model has entered production.
The first question is whether the new component changes any specifications or information included in the passport. If it does, the team needs to identify which models and individual batteries are affected.
Product management can identify the impacted products and revisions. Your procurement team can obtain the updated supplier information. Compliance can assess whether passport data needs to change, and IT can support the required update.
If the supplier change doesn't affect any applicable passport information, the team can document the assessment rather than automatically changing every passport. This is why we recommend linking Digital Battery Passport reviews to existing engineering change or product change processes.
The same principle applies after a battery is sold, although the information may be harder to access.
One challenge we've heard from manufacturers is how to maintain dynamic information, such as battery state of health, when the battery operates outside their own systems.
In one customer discussion, possible approaches included obtaining information through a BMS or an intermediary system. The challenge wasn't simply creating a technical connection. It was also determining where the information would come from and how the company could maintain it.
For product teams, this means identifying the relevant lifecycle events and agreeing on how information should reach the responsible team or system.
Not every update requires real-time connectivity. The Commission's Battery Passport FAQ explains that dynamic information must be updated at least when a battery's status changes or a change is being considered, with other updates depending on the type of information and circumstances.
A simple repair does not automatically require a new passport. However, repurposing and remanufacturing, as well as certain operations involving batteries that have become waste, can trigger the requirement for a new, linked passport. Once a battery is recycled, its passport ceases to exist.
The practical takeaway is to make passport impact part of existing product and lifecycle decisions. When something changes, the team should know who checks the passport, what information needs reviewing, and who is responsible for taking action.
How do product, IT, and compliance make this work together?
The easiest way to begin is not to create a large cross-departmental project around every possible Digital Battery Passport scenario.
Instead, bring the relevant teams together around one representative battery model and work through the process from product definition to passport creation.
Product management should be able to explain the finished battery, its variants, and upcoming launches. Compliance should identify the applicable requirements and confirm the legal responsibilities. IT should map the sources, identifiers, and data flows needed for implementation.
Procurement joins where supplier information is needed, and service or after-sales teams should be involved when ongoing operational data is part of the process.
Regardless of how responsibilities are divided internally, the economic operator placing the battery on the market remains legally responsible for ensuring that the passport information is accurate, complete, and up to date. Another operator can be authorized in writing to carry out the work on its behalf.
We've seen manufacturers approach this in different ways. Some separate data mapping from technical integration, while others begin with an ERP-connected workflow. What matters is that the product and data decisions are clear before the process is scaled.
A useful outcome from the first working session is three things: an approved product scope, a data gap tracker with named owners, and a defined process for creating and maintaining passports.
These give the team something concrete to work with and help prevent the same questions from being reopened at every stage.
“One thing we see in practice is that creating the Digital Battery Passport isn't always the biggest challenge. It's figuring out which products are covered, where the information comes from, and can be displayed in the required format. Once product, IT, and compliance teams have a clear picture of that, the implementation becomes much easier.”
— Dimitar Klimoski, Project Manager at Minespider
What should product teams take away from this?
Digital Battery Passports introduce new information and coordination requirements, but product teams don't need to build an entirely new product management process to handle them.
Much of the work can fit into activities they already manage: product classification, technical documentation, supplier coordination, launch readiness, and engineering changes.
Start with a real battery model. Confirm whether it needs a passport, map the applicable information, identify missing data, and test how its passport will be created. Then make sure there's a process for reviewing relevant changes after launch.
From what we've seen in our work with battery manufacturers, this is where the preparation becomes much more manageable: when broad requirements are turned into defined decisions, data sources, and responsibilities.
A good Digital Battery Passport process should not depend on someone remembering to update a document. It should be connected to the way the battery product is already managed.
What’s next for Digital Battery Passports?
Preparing your products for February 2027 is only part of the process. The European Commission continues to clarify the technical requirements, including how Digital Battery Passport data should be structured, registered, and accessed.
In October 2026, several important updates gave manufacturers a clearer picture of what to prepare for.
Want to know what changed and what it means for your company?
