EU Battery Passport 2027: What SMB Manufacturers Need to Do Right Now

EU Regulation 2023/1542 requires electric vehicle batteries, industrial batteries, and light-means-of-transport batteries to carry a compliant Digital Product Passport from February 18, 2027. That deadline is under nine months away. We walked through the compliance requirements with a Dutch mid-size manufacturer of industrial battery packs — here is what the readiness gap actually looks like, and the fastest path to closing it.

---

What the EU Battery Regulation actually requires for DPP

The battery passport under Annex XIII of EU Regulation 2023/1542 is more specific than the general ESPR DPP framework. It requires:

• Carbon footprint declaration per kWh of capacity
• Recycled content percentage (cobalt, lithium, nickel, lead) with certified methodology
• State of health and remaining capacity (for batteries placed on market after initial use)
• Supply chain due diligence disclosures
• Hazardous substances list
• Information on dismantling and repurposing
• QR code linking to a digital record accessible for 10 years after the last unit is placed on the market

The 10-year data persistence requirement is the blocker most SMB manufacturers underestimate. A static QR code pointing to a PDF on your current website is not compliant — the regulation requires structured, machine-readable data accessible for a decade.

What that means in practice: your resolver infrastructure must outlive your current hosting arrangement, your current website, and your current tech stack. Most companies rotate hosting every 2–3 years. The battery passport forces you to think in 10-year infrastructure commitments, not sprint cycles.

---

The seven gaps we found in a typical SMB battery manufacturer

We ran through the battery DPP checklist with a Dutch manufacturer of industrial battery packs used in uninterruptible power systems (UPS). The company had 80 employees, sold B2B across the EU, and had an existing ISO 9001 quality management system. They were not unprepared — and they still had seven significant gaps.

Gap 1 — No GTIN registered. The manufacturer used internal part numbers, not GTINs. A GS1 Digital Link URI requires a GTIN as the primary identifier. GS1 Netherlands GTIN registration takes 7–14 business days after membership approval. This is the longest lead-time item and must start first.

Practical implication: if you have 40 SKUs and each requires a separate GTIN, you cannot batch-register overnight. GS1 membership, GTIN allocation, and system data entry are a 3–4 week process at minimum.

Gap 2 — Carbon footprint data exists but is not in machine-readable format. The manufacturer had a carbon footprint assessment (PCF) from a consultancy, but it was a PDF report, not structured data. The DPP requires the PCF per kWh in a format a resolver can serve as JSON. Translation effort: roughly 2 days with a data engineer, assuming the PDF methodology is clean enough to extract figures from programmatically.

The harder case: if your PCF was done at facility level rather than per-product, you need to allocate the carbon footprint across your SKU catalog. That is a modeling exercise, not a data entry task.

Gap 3 — Recycled content percentages were unavailable per material. The bill of materials showed cobalt and lithium sourcing but not the certified recycled-content percentage. The manufacturer's tier-2 supplier had the data — but not in a format the manufacturer could pull on demand. Supply chain data collection is a 3–6 week project, and that assumes cooperative tier-2 suppliers.

Regulation 2023/1542 requires separate recycled content declarations for cobalt, lithium, nickel, and lead. If your battery chemistry does not use all four, you must still declare the ones that apply with certified methodology.

Gap 4 — No dynamic QR code infrastructure. Current packaging QR codes pointed to a static URL on the company website. No resolver, no analytics, no ability to update the destination without reprinting. Switching to a dynamic resolver with QR-Verse Business plan resolved this in two hours — including setting up a dedicated id.company.com subdomain and testing the first compliant GS1 Digital Link URI.

The packaging artwork update took longer than the technical setup. Working with the print supplier to place a correctly-sized compliant QR code at the right minimum module size added two weeks to the timeline.

Gap 5 — No 10-year data storage plan. The regulation requires data access for 10 years after the last unit is placed on the market. The manufacturer's current web infrastructure rotates hosting every 2–3 years. A dedicated DPP data platform or a long-lived cloud storage layer is required — and it needs contractual guarantees, not just a verbal commitment from your current hosting provider.

Gap 6 — State of health data model not defined. For batteries placed on market after initial use (second-life batteries), the DPP must include state of health and remaining capacity. The manufacturer's internal testing measured these values but there was no data model or API for exposing them in a machine-readable format that a resolver could serve on demand. Defining that data model is a software architecture task, not a compliance task.

Gap 7 — Hazardous substances list was incomplete. The manufacturer's safety data sheets covered the finished battery, but the DPP requires substance disclosures at the component level. Several sub-components sourced from third-party suppliers had no REACH compliance documentation on file. Chasing these down from five suppliers took three weeks.

---

The fastest compliant path for a battery SMB

The critical path to a compliant battery DPP pilot runs like this:

Week 1–2: Apply for GS1 membership and GTIN allocation (cannot be compressed — this is an external dependency).

Week 1–4 (parallel): Structure your carbon footprint data per kWh per SKU. If your PCF is per-facility, this requires an allocation model.

Week 2–3 (parallel with GTIN application): Set up resolver infrastructure. Dedicated subdomain, dynamic QR code generation, JSON-LD or structured data API for DPP fields.

Week 3–8: Supply chain data collection for recycled content and hazardous substances. Start tier-2 supplier outreach immediately — this is the longest parallel track.

Week 6–8: First compliant QR code on packaging artwork. Validate with an industrial 2D scanner and iOS/Android native camera.

Week 8–12: Full catalog rollout assuming similar data availability across SKUs.

A single-SKU battery passport pilot is achievable in 60 days from standing start, assuming GTIN registration begins immediately. Full catalog rollout for a 40-SKU manufacturer adds another 60–90 days depending on how many SKUs share the same data fields.

---

What the QR code on the packaging actually needs to encode

A compliant battery DPP QR code encodes a GS1 Digital Link URI with at minimum the GTIN (Application Identifier 01). For batteries with serialization requirements, the serial number (AI 21) and manufacturing date (AI 11) are also required. The URI structure is:

https://id.yourcompany.com/01/[GTIN]/21/[SERIAL]?11=[MFGDATE]

The resolver at id.yourcompany.com must return a structured DPP data payload. The battery regulation does not specify a single data format, but JSON-LD with a defined schema (the Catena-X battery pass schema is the de facto standard in the EU) is the most interoperable choice.

QR-Verse generates the correct URI and QR code from GTIN input. The resolver hosting and structured data payload are your responsibility — or a DPP platform's. What we handle is the physical code: correct module size (ISO/IEC 18004), correct error correction level, SVG export for print, and scan validation.

Minimum print size for industrial battery packaging: 2 × 2 cm at 300 DPI with Quiet Zone. For small battery cells where space is constrained, the GS1 specification allows minimum module width of 0.25 mm — but test on your actual substrate before committing to a press run.

---

Validation tools before you go to print

Before any packaging goes to press, validate your QR codes on three surfaces:

1. Native iOS camera (current OS) — tests the consumer-facing scan path
2. Native Android camera (current OS) — tests the second major consumer platform
3. Zebra DS3678 or equivalent industrial 2D imager — the scanner type used in EU retail receiving and production line environments

Also validate the resolver response: the QR code is only half the compliance requirement. The data returned when you scan must match the Annex XIII fields. Use the GS1 Digital Link resolver validation tool to check your URI structure before encoding.

---

Tools and resources for battery DPP compliance

• GS1 Battery Passport Implementation Guideline — the technical specification for GTIN encoding and resolver requirements
• Catena-X battery pass schema — open-source data model for DPP data fields, maintained by the automotive supply chain consortium
• CIRPASS pilot project — EU-funded interoperability test environment for DPP implementations
• QR-Verse GS1 Digital Link generator — generates compliant QR codes from GTIN input, Business plan €19/mo
• Recommended DPP data platforms for SMB: Circularise, TrusTrace, Siemens Teamcenter (for larger manufacturers)

---

The bottom line

The battery passport is the first DPP deadline with teeth — February 18, 2027 is a fixed date, not a moving target. Most SMB battery manufacturers are 60–90 days of focused work away from a compliant pilot. The work is not technically complex. It is data collection and infrastructure work that requires starting now, not in Q4 2026.

The single most important action you can take today: apply for GS1 membership and GTIN registration. Everything else — carbon footprint structuring, resolver setup, supply chain data collection — can run in parallel once that process is underway. The GTIN lead time is the one dependency you cannot compress.