Blog
Practical guides on Digital Product Passport compliance and EU regulation.
Passport scans are visits to a web page, so GDPR and ePrivacy apply from day one. Here's where the actual risk sits — analytics, geolocation, marketing reuse — and how to keep the compliance layer clean.
The Packaging and Packaging Waste Regulation (EU) 2025/40 adds packaging-level QR obligations on its own timeline. Here's how they relate to the battery passport carrier, and the one-code principle.
Mistakes in a published passport are fixed by correction and versioning, not deletion. Here's how the update obligation works, why silent fixes are the wrong instinct, and how to build for correctability.
For LMT brands that outsource pack assembly, the passport obligation usually lands on the brand, not the assembler. Here's the rebadging trap and how to close the data gap it creates.
No — for EV and LMT batteries the passport is a living record that accumulates state-of-health, repair, repurposing, and recycling events over the unit's life. Here's what that changes operationally.
No — the passport model has public and restricted attribute tiers, with role-based access for regulators and recyclers. Here's what's actually visible to whom, and how evidence stays confidential.
The battery passport's data carrier is a QR code resolving to a per-unit record. Here's how GS1 Digital Link identifiers map to model, batch, and item level — and the mistakes to avoid before printing.
The Battery Regulation's due-diligence duty for cobalt, lithium, nickel, and natural graphite is OECD-aligned and documentation-driven. Here's the SME-scale version of doing it properly.
Probably not as-is. The EU Battery Regulation requires a carbon footprint declared per its own methodology, on its own phased timeline — earlier than the passport itself. Here's how the pieces fit.
No. Your MES and ERP already generate most of the genealogy and master data the passport needs — the missing piece is a publishing layer, not a systems replacement.
The passport requires per-unit identity for the battery you place on the market — not (yet) for every cell inside it. Here's where the serialization line actually sits, and why it's moving.
Mostly, yes. A source map showing where each group of battery passport attributes already lives in a typical manufacturer — ERP, MES, PLM/PDM, test stations, and supplier documents.
What to do when the cell manufacturer ignores your passport data requests: what you can demand, how verifiable evidence works without exposing supplier secrets, and when to switch suppliers.
With the 18 February 2027 deadline approaching, here's an honest back-plan of what takes months (supplier data, due diligence) versus what takes weeks (publishing), and where to start.
Not every battery needs a Digital Product Passport in 2027. Here's the category-by-category scope of Regulation (EU) 2023/1542, including the exclusions and the CN codes that matter.
If you place the finished battery on the EU market, the Digital Product Passport obligation is yours — even when every cell comes from someone else. Here's why, and what to do about it.
The EU Battery Regulation (2023/1542) is the first EU rule with a fixed Digital Product Passport deadline. Here's exactly what it requires, and for which battery types.
A category-by-category breakdown of when the EU's Ecodesign for Sustainable Products Regulation (ESPR) requires a Digital Product Passport, from batteries in 2027 onward.
A Digital Product Passport (DPP) is a structured, machine-readable record of a product's materials, origin, and lifecycle data. Here's what that means in practice.