What a Data Sheet Is Designed For
What the Battery Passport Requires
Reference Object
What a Data Sheet Is Designed ForModel- or batch-specific. One document per type, valid for everything produced in that series.
What the Battery Passport RequiresModel- and battery-specific. Annex XIII explicitly distinguishes between information regarding the battery model and data on individual batteries, including condition and status changes.
Result
What a Data Sheet Is Designed ForA document. The end result is a PDF that a person reads.
What the Battery Passport RequiresA data record. Machine-readable, accessible via the QR code on the battery, with tiered access for the public, market regulators, notified bodies, and individuals with a legitimate interest.
Cadence
What a Data Sheet Is Designed ForIn the event of a product change, or, if in doubt, once per model generation.
What the Battery Passport RequiresOngoing. The information must be accurate, complete, and up to date for as long as the battery remains in circulation. Repurposing creates a new record linked to the previous one; it expires only upon recycling.
The regulation says so itself
Annex XIII, in paragraph 4, requires data on individual batteries, not on the model: condition values, charge cycles, negative events, and the status as unchanged, repurposed, reused, remanufactured, or end-of-life. A document that applies to an entire series cannot capture this information.
Regulation (EU) 2023/1542, Annex XIII, No. 4, in conjunction with Article 77(2)
The question you should ask yourself
Will the database you're currently building for the Battery Passport also support the ESPR Digital Product Passport for your other products later on? If not, you'll be building the same foundation a second time—and this time under the same time pressure.