An individual physical battery unit used as the item-level identity anchor for a serialized battery passport.
Battery item is the individual battery layer in battery-passport implementation. The distinction lets item-level identity, status history, and lifecycle events stay specific to one physical battery while model-level or batch-level evidence can be inherited without duplication.
A battery item is an individual physical battery unit: the specific asset that needs its own identity, access path, and lifecycle record in a serialized battery passport. It is not a product model, manufacturing batch, software platform, QR code, or data carrier.
In digital passport and traceability systems, a battery item is the specific physical unit or serialized product instance to which item-level battery-passport data is attached. Technical blueprints, chemistry profiles, and conformity templates may be managed at model level; production inputs and quality context may sit at batch level; but the battery item is the physical asset connected to the unique identifier, data carrier, and battery passport record. It is the layer where use-derived and unit-specific evidence can accumulate, including state of health, repair history, chain-of-custody events, and end-of-life milestones.
The common mistake is to collapse product, battery, model, batch, and item into one level. Model-level data describes the product design, such as shared chemistry, dimensions, baseline declarations, and other stable attributes. Batch-level data describes a shared production or logistics context, such as supplier lots, production dates, or quality evidence for a subset of units. Item-level data describes one serialized physical battery. A model-level QR code or batch-level record cannot substitute for item-level identity when the question is which battery is being scanned, used, repaired, transferred, repurposed, or recycled.
Battery item is best treated as an implementation-granularity term rather than a standalone verbatim EU legal definition. Article 77 of the EU Battery Regulation requires a battery passport for individual batteries in covered categories, including LMT batteries, industrial batteries above 2 kWh, and electric vehicle batteries, and Annex XIII includes information that can be specific to the individual battery or result from use. DIN DKE SPEC 99100 uses battery item as battery-passport implementation context rather than a public verbatim definition, helping teams distinguish individual item-level records from model or batch groupings while respecting the copyrighted standard text.
For MES, ERP, labeling, and passport-system teams, battery-item architecture means serialization must be planned inline with manufacturing and lifecycle-data capture. Item records should inherit stable model-level or batch-level attributes where appropriate instead of copying every chemistry, conformity, or supplier fact into every record. At the same time, the item record must preserve the unique identifier, data-carrier resolution path, lifecycle events, status changes, repairs, chain-of-custody updates, and end-of-life evidence that belong to one physical battery. Parent-child associations also matter when cells, modules, packs, repairs, repurposing, and recycling create hierarchies or changed assemblies over time.
These entries are non-verbatim context summaries. They are not presented as public legal definitions.
DIN DKE SPEC 99100:2025-02 — Requirements for data attributes of the battery passport
DIN DKE SPEC 99100 uses battery item as non-verbatim battery-passport implementation context for an individual battery unit, helping distinguish item-level records from model-level and batch-level groupings.
Non-verbatim implementation-context summary only; not a verbatim DIN definition. DIN DKE SPEC 99100 is a copyrighted standard, so this page uses it as implementation context rather than republishing the standard text.
Reference: Section 3.25
Reviewed public draft page. Aligns with identity/access policy: separates identity, carrier, QR/access mechanism, passport record, item granularity, and service-platform infrastructure.
Implementation records should capture physical battery identifier, unique identifier, data carrier link, passport record, status history, repair and service events, chain-of-custody events, state-of-health updates, end-of-life milestones, and model or batch inheritance rules.
Battery item is the granularity question behind the passport and the item-level granularity control for evidence routing. It defines which facts belong to this individual battery and which can be inherited from a model, batch, supplier, or chemistry record, while certification records can remain linked without losing traceability.
Useful context for explaining battery-passport identity and the difference between records, standards, and implementation layers.
Read on MinespiderBattery-sector context for item-level identity, passport records, and supply-chain evidence.
Read on Minespider