The EU Digital Product Passport: What Manufacturers Need to Know Before 2027

Most compliance deadlines creep up on manufacturers through paperwork. This one arrives through the product data pipeline. Starting 18 February 2027, every EV battery, industrial battery over 2 kWh, and light means of transport (LMT) battery placed on the EU market must carry a Digital Product Passport (DPP) - a machine-readable record of what's in it, where it came from, and how to recycle it, linked to the physical product through a QR code or similar data carrier.

Batteries are the first category, but they won't be the last. If your product data isn't currently structured to answer "what is this made of, and where did each part come from" at the individual-unit level, this is the deadline that forces the issue - and the infrastructure question looks a lot like the industrial AI data readiness problem manufacturers are already fighting on the shop floor.

What a Digital Product Passport Actually Is

The DPP is defined by the EU's Ecodesign for Sustainable Products Regulation (ESPR, Regulation (EU) 2024/1781), which the European Commission describes as "a digital container for products, components and materials" holding structured data on safety, material origin, environmental performance, repairability, and end-of-life reuse or recycling instructions. The exact fields required vary by product category and are set out in category-specific delegated acts - the DPP is a framework, not a single fixed form.

Physically, the passport isn't the data itself sitting on the product - it's a link. The Commission's guidance specifies "a digital data carrier, such as a QR code," scanned by a customer, recycler, customs official, or downstream supply chain partner, that resolves to the passport record. Industry implementations also use RFID and NFC tags where a QR code isn't practical (embedded components, harsh environments), though the Commission's own confirmed guidance centres on QR.

Crucially, this isn't an EU-companies-only rule. ESPR obligations attach to "economic operators" placing products on the EU market, which the regulation defines to include non-EU manufacturers (through an EU Authorised Representative), EU-based importers, and distributors. A factory in Ohio or Ho Chi Minh City shipping batteries into the EU is in scope just as much as a factory in Munich. Products are checked against DPP requirements at EU customs.

The Timeline: What's Locked In and What's Still Proposed

It's worth separating what's confirmed regulation from what's still a working plan, because a lot of DPP content online blurs the two.

Confirmed and legally binding:

• 18 February 2027 - under the EU Batteries Regulation (2023/1542), Article 77, EV batteries, industrial batteries above 2 kWh, and LMT batteries require a battery passport. This date is set in the regulation text, not a proposal.

Published as an official plan, but not yet locked in as law:

• On 16 April 2025, the European Commission adopted the ESPR Working Plan 2025-2030, naming iron and steel, textiles, furniture, tyres, aluminium, and mattresses as priority product groups for future DPP requirements, with iron and steel first (public consultation opened May 2026, adoption targeted for later in 2026) and textiles, tyres, and aluminium indicated for 2027.
• As of this article's publication, no delegated act beyond batteries had been formally adopted. Treat every post-2026 category date as the Commission's stated intent, not a finalised deadline - it's the plan, not yet the law.

That distinction matters operationally. Batteries manufacturers have a hard date to hit. Everyone else has a strong, well-sourced signal about where regulatory attention is heading next, which is exactly the situation where building the underlying data capability early - rather than scrambling against a delegated act once it publishes - pays off.

Why This Is a Data Infrastructure Problem, Not Just a Compliance Problem

A DPP isn't a document a compliance team fills in once at product launch. It has to be assembled from data that already lives - if it lives anywhere structured at all - across separate systems: bill-of-materials data in PLM, supplier certificates of origin in procurement systems, energy and emissions data from production (the kind of data an OEE calculator or energy monitoring system already tracks), and end-of-life/recycling instructions from engineering.

For most manufacturers, none of that currently connects at the individual-batch or individual-unit level required for a passport. This is the same gap the industry has been fighting under a different name: getting shop-floor and enterprise data into a state where it's contextualized, traceable, and trustworthy enough to feed a downstream consumer - whether that consumer is an AI model or, in this case, a regulator-mandated public record.

A concrete example: a mid-size manufacturer producing industrial battery packs for material-handling equipment (forklifts, AGVs) currently tracks cell chemistry and supplier batch numbers in a spreadsheet maintained by procurement, tracks assembly-line traceability (which cells went into which pack) in the MES, and has no link between the two. To issue a compliant battery passport by February 2027, that manufacturer needs: a stable unique identifier per battery pack, a data model that ties supplier-level material data to that identifier, an accessible record (hosted, versioned, and available for the product's expected lifetime - the regulation requires passport data to remain accessible after the product is placed on the market), and a QR code or data carrier applied during final assembly that resolves to it. None of that is exotic engineering. It is, however, integration work that takes months, not weeks, if it starts from scratch six weeks before the deadline.

How to Start Now

1. Inventory what you already track. Bill-of-materials, supplier certificates, batch/serial traceability, and end-of-life data usually already exist somewhere - the gap is almost always that they're not linked to a single product identifier.
2. Establish a unique identifier strategy per unit or batch, consistent with how your unified namespace or MES already identifies products on the line, so passport data can be generated from production data rather than re-entered by hand.
3. Check whether your product category has a published Working Plan date. If you make batteries, February 2027 is fixed. If you make textiles, tyres, aluminium products, or furniture, the Working Plan gives you a realistic planning horizon even before the delegated act is final.
4. Budget it as an integration project, not a compliance line item. The ROI calculator is a reasonable starting point for scoping the cost of the data integration work against the cost of non-compliance (which for battery products means being unable to place goods on the EU market at all).
5. Don't wait for the delegated act to start the data model work. The fields will vary by category, but the underlying capability - a system that can produce a trustworthy, structured, linkable record per product - is the same investment regardless of which category's rules land first.

The Bottom Line

The Digital Product Passport is a genuinely new obligation, but the capability it demands - clean, connected, unit-level product data spanning procurement, production, and engineering - is the same capability manufacturers need for AI-driven quality and traceability work anyway. Treated as an isolated compliance checkbox, DPP compliance is a scramble against a series of deadlines. Treated as an extension of the data infrastructure work already underway on the shop floor, it's one more consumer of a data foundation worth building regardless. For a primer on the broader terminology this connects to, see the glossary.