Which Batteries Need a Passport? Scope Rules

Most of the disagreement about battery passports is not about what the passport contains. It is about whether a particular product needs one at all. The categories in Regulation (EU) 2023/1542 are defined precisely, and a product that looks obviously in scope sometimes is not.

Which battery categories are in scope?

The regulation defines five battery categories and applies the passport obligation to three of them. The distinction matters commercially, because the other two carry substantial obligations under the same instrument without the passport requirement.

What counts as a light means of transport battery?

The definition turns on traction rather than on the vehicle. A pack powering an e-bike, an electric scooter or a light quadricycle is an LMT battery. A pack powering a device that does not move under its own wheels is not, however similar the cells inside it are.

This catches manufacturers who think of themselves as consumer electronics businesses. An e-scooter maker is inside the battery passport regime on the same date as an automaker, with a fraction of the compliance function.

How is industrial battery capacity measured?

Capacity is rated energy in kilowatt-hours, declared by the manufacturer under the applicable measurement standard. The threshold is above 2 kWh, so a battery rated at exactly 2 kWh sits outside the passport obligation.

Two consequences follow. First, the declared rating is the number that decides scope, so a conservative rating has a regulatory effect as well as a commercial one. Second, a modular system assembled from smaller units needs a view on what the battery actually is, because the answer decides whether the threshold is crossed.

Does scope depend on where the battery was made?

No. The obligation attaches to placing the battery on the EU market, which means making it available for the first time on that market in the course of a commercial activity. A manufacturer outside the EU supplying an EU importer is not the responsible economic operator, but the battery is still in scope and the data has to come from somewhere.

In practice this shifts the work rather than removing it. The importer carries the obligation and will contract for the underlying data, which lands on the cell producer and the pack assembler regardless of where they sit.

What about batteries already in service?

The passport requirement applies to batteries placed on the market from the application date. A battery placed on the market before that date does not acquire a passport obligation retroactively.

Repurposing changes this. A battery that undergoes preparation for repurposing or remanufacturing is treated as newly placed on the market, and the operator carrying out that preparation becomes responsible for the passport. Second-life operators who assumed the regime did not reach them are frequently wrong about this.

What if the category is genuinely ambiguous?

Some products sit near a boundary: a battery for a light commercial application that could read as industrial or as electric vehicle, or a large portable pack that approaches the weight test. The regulation does not offer a self-certification route out of the ambiguity.

• Document the categorisation decision and the evidence behind it at the time you take it.
• Where two categories are arguable, the more demanding one is the defensible planning assumption.
• A national market surveillance authority can and does take a different view later.
• Retrofitting a passport is far cheaper than defending an absent one during an inspection.

The asymmetry is the point. Building passport data for a battery that turns out to be exempt costs you the data collection. Not building it for one that turns out to be in scope costs you the market.

Who in the chain has to act once scope is settled?

Scope decides which product lines are affected. It does not decide who does the work, and those are different questions with different answers. The economic operator placing the battery on the EU market holds the legal obligation, but almost none of the data originates with them.

Every row of that table has the same accountable party and a different source. That asymmetry is the whole difficulty of a battery programme: the operator who answers to the regulator controls none of the inputs directly, and has to obtain each one by contract from a party with no equivalent obligation.

How does the passport interact with other obligations?

A battery in scope for the passport is almost always in scope for other parts of the same regulation, and often for instruments outside it. Treating the passport as a standalone project produces duplicated collection.

• Due diligence obligations under the same regulation apply on their own schedule, ahead of the passport date.
• Carbon footprint declaration requirements phase in per battery category and feed the same field the passport carries.
• CSRD reporting under Directive (EU) 2022/2464 asks for figures the passport already holds at product level.
• Waste obligations at end of life depend on the dismantling data the passport publishes.

The practical consequence is that the passport is a better organising unit than any single obligation. Collect once against the product record, and each instrument becomes a projection of it. Collect per obligation, and the same supplier is asked for the same figure three times in a year, which is how supplier goodwill is spent.

What scope means for the data you must hold

Once a battery is in scope, the passport must carry chemistry and composition, carbon footprint, recycled content of cobalt, lithium, nickel and lead, state of health and expected lifetime, hazardous substances, dismantling information and supply chain due diligence. Those fields are set out in the battery passport guide and the evidence behind each of them is a supplier problem before it is a software one.

Scope is therefore the first decision in a battery programme, not a compliance formality at the end of it. It determines how many product lines need supplier engagement, and supplier engagement is the constraint that decides whether the date is met.