Battery Passport Exemptions
This page focuses on the real-world situations where teams misclassify products, miss obligations, or build the wrong compliance architecture.
Use this as a decision aid. When in doubt, treat the question who is placing the battery on the EU market or putting it into service¯ as the primary trigger and document your rationale.
Start with the non-negotiables
Battery Passports become mandatory from 18 February 2027 for EV batteries, LMT batteries, and industrial batteries above 2 kWh that are placed on the EU market or put into service from that date. Most exemptions¯ in practice are not true exemptions. They are usually classification issues, boundary issues, or responsibility shifts between actors.
If a battery is out of passport scope, it may still be regulated under the EU Battery Regulation. Do not treat no passport¯ as no compliance.¯
| Question | Why it matters | Where to go next |
|---|---|---|
| Is it an EV, LMT, or industrial battery > 2 kWh | These are the passport-trigger categories from 18 Feb 2027 | Batteries in Scope |
| Who is placing it on the EU market | Determines who must create and maintain the passport record | Implementation and Governance |
| Is the item a battery, a module, or part of a larger system | Some obligations change when modules are incorporated into packs or systems | Data Requirements Overview |
True exceptions & special-use cases
The regulation is broad, but certain batteries designed for special purposes are commonly treated as exceptions in practice. These cases are usually narrow and should be supported by clear product intent and documentation.
If you believe your product is a special-use exception, capture evidence early: intended use, customers, restrictions, labeling, and distribution controls. General availability¯ products rarely qualify.
| Case | Typical rationale | What to document |
|---|---|---|
| Military or defense-specific batteries | Designed exclusively for military use and controlled distribution | Design intent, restricted sales channels, end-user controls |
| Aerospace-specific batteries | Designed exclusively for aerospace or space use with constrained market placement | Design intent, certification context, restricted distribution |
| Prototypes and non-market demonstration units | Not placed on the market and not put into service in a commercial sense | Internal controls, non-sale status, disposal plan, traceability |
Capacity thresholds & classification traps
A large share of edge cases¯ are actually threshold errors. Industrial battery classification and the > 2 kWh trigger are easy to misunderstand when products are modular, configurable, or built into equipment.
When capacity can vary by configuration, treat the highest configuration you place on the market as the governing case unless you have strict SKU controls that prevent higher-capacity placement.
| Edge case | Risk | Practical handling |
|---|---|---|
| Configurable packs with optional extra modules | Teams assume the base variant is in scope logic for all variants | Define passport per marketed SKU and lock configuration control |
| Battery embedded in equipment sold as a system | Assuming system¯ is exempt from battery obligations | Classify the battery category first, then map obligations |
| Portable-looking products that function as industrial energy units | Misclassifying industrial batteries as portable due to form factor | Use intended use and market placement, not appearance |
Spare modules, service parts, and integrations
Service and aftermarket flows create the most confusion. A common situation is a module¯ sold as a spare part that is intended to be incorporated into a larger battery pack or a battery energy storage system. In some cases, obligations may not apply to the module as a standalone product when it is supplied for integration rather than placed as an independent battery on the market.
Treat service parts as a governance problem. Even if a specific part is treated differently, you still need traceability, revision control, and evidence that the part was used only as intended.
| Scenario | Common mistake | Controls to implement |
|---|---|---|
| Module shipped as a spare for incorporation into a pack | Treating the module like a finished battery product with full obligations | Document integration-only intent; restrict channels; track serial and destination |
| BESS component modules shipped to integrators | No clarity on who owns passport and who updates lifecycle events | Contractual responsibility map; data handoff rules; audit trail |
| Aftermarket upgrade kits | Assuming upgrades do not change identity or record requirements | Change control policy: when an upgrade triggers new identity versus update |
Legacy inventory, transitioning & placement date
The compliance trigger is tied to when a battery is placed on the EU market or put into service. This creates transition questions for inventory, staged shipments, phased rollouts, and products assembled from components procured before the passport start date.
You should be able to prove the placement date for in-scope products and tie that to the presence or absence of a passport record. If you cannot prove the placement date, you should assume the stricter interpretation in operational planning.
| Transition case | What to track | Recommended policy |
|---|---|---|
| Stock produced before 18 Feb 2027 but sold after | Market placement date and distribution records | Use sales and import records; do not rely on manufacturing date alone |
| Products assembled in EU from imported components | Who is the manufacturer of the battery placed on the EU market | Define the responsible economic operator and data ownership early |
| Refurbished or repurposed batteries re-entering commerce | Whether the activity is treated as a new placement on the market | Define reuse workflows and record update rules; document decision logic |
Commonly misclassified batteries (gotchas)
A common failure mode is assuming a battery is out of scope¯ because it is portable, embedded in equipment, or sold as part of a product rather than as a standalone pack. In practice, scope is driven by battery category and capacity thresholds (especially the > 2 kWh industrial battery trigger), and by whether the battery is placed on the EU market. If a battery pack exceeds 2 kWh and is not an SLI battery, treat it as in-scope until proven otherwise.
| Battery or product example | Why teams assume out of scope | Why it may be in scope | What to check |
|---|---|---|---|
| Cordless power tool packs (pro and consumer) | Marketed as portable¯ and bundled with tools | Pack capacities are rising; some exceed 2 kWh; may be treated as industrial depending on category and placement | Pack Wh rating; whether placed on EU market as pack or embedded battery; category classification |
| Commercial lawn and grounds equipment (ride-on, zero-turn, professional mowers) | Viewed as equipment¯ rather than battery products¯ | Often uses large packs > 2 kWh; used in professional settings; battery is still placed on the EU market | Pack Wh rating; whether battery is sold as a replaceable unit; who is the economic operator for EU placement |
| Portable power stations / mobile energy boxes | Marketed as appliances or generators¯ | Capacity frequently far exceeds 2 kWh; effectively a portable energy storage product | Battery category used for compliance; capacity; presence of multiple modules; replacement battery packs |
| Robotics and industrial equipment batteries (cleaning machines, warehouse carts, mobile robots) | Not an EV or an obvious battery product¯ | Often > 2 kWh; used in industrial/commercial environments; batteries are placed on the EU market with equipment | Capacity; intended use; serviceability and replaceability; product documentation and category |
| Embedded battery packs sold with a device or machine | Embedded means exempt¯ assumption | Embedded does not automatically exclude scope; obligations attach to the battery placed on the EU market and its category | Who places on the EU market; whether battery is rechargeable; capacity; which battery category applies |
Quick checklist for edge cases
If you are stuck, use this checklist and document the answers. In audits, consistent, documented decision logic is often as important as the final classification outcome.
If you sell into the EU, default to in scope until proven otherwise¯ for EV, LMT, and industrial batteries above 2 kWh. Then work backward using classification evidence, market placement evidence, and responsibility mapping.
| Checklist item | Yes or no? | Evidence to keep |
|---|---|---|
| We can classify the battery category with a written rationale | __ | Category decision memo; product spec; intended use statement |
| We can prove the EU market placement or in-service date | __ | Import docs; sales invoices; distribution records |
| We have a single responsible owner for passport data and updates | __ | RACI; system source-of-truth map; supplier handoff rules |
| We have identity and change control rules for upgrades and repairs | __ | Serialization policy; revision control; service procedures |
Disclaimer. Informational guidance only. Not legal advice. Validate requirements against current official regulation text and implementing acts.