There is a scheduling problem at the centre of digital product passport planning, and it is worth doing the arithmetic before anything else. When a delegated act names your product group, it typically allows around eighteen months before compliance bites. Collecting verified supplier and material data is commonly estimated at twelve to eighteen months. Those two figures overlap almost exactly — which means the moment your act publishes is roughly the moment you would have needed to have already started. Waiting for your final field list is therefore not a cautious strategy, it is a decision to be late. The practical response is to build the data backbone now against what every product group will need in common, and treat the group-specific fields as the last mile rather than the foundation. Request the integration datasheet to see what your current records could already evidence.
Digital Product Passport Readiness
The one date that is actually fixed, the mechanism that decides when yours arrives, the attributes worth collecting before any field list is published, and who inside the business has to own it.
Two Numbers That Do Not Fit Together
The scheduling conflict that should drive every decision on this page.
What Is Fixed, and What Is Expectation
An important distinction, because treating indicative dates as deadlines produces panic and treating them as optional produces delay.
| Product group | Delegated act expected | Legal status | What to do about it |
|---|---|---|---|
| Batteries EV, industrial above 2 kWh, light transport |
Already legislated separately | Fixed — 18 February 2027 under the Battery Regulation, not under ESPR | If you place these on the EU market, 2026 is your data-readiness year |
| Iron and steel | Adoption work indicated from 2026 | Indicative | An intermediate product group, so it reaches vehicle makers through input materials rather than directly |
| Textiles, tyres, aluminium | Around 2027 | Indicative | Compliance realistically no earlier than 2028 once the transition period runs |
| Furniture | Around 2028 | Indicative | High direct-to-consumer exposure makes early material and origin data worthwhile regardless |
| Electronics and ICT | 2028 to 2029 | Indicative | Heaviest existing compliance load, so the work is largely making existing data machine-readable and item-level |
| Mattresses and later groups | 2029 onward | Indicative | A second working plan is expected before 2030 covering further categories |
July 2026 Is Infrastructure, Not Obligation
A distinction being widely misread, in both directions.
Build Against the Common Core
Field lists differ by product group, but the underlying categories repeat. Comparing two published sets makes the pattern visible.
| Attribute category | Battery passport requires | Textile requirements point to | Collect now? |
|---|---|---|---|
| Material composition | Composition with geographic origin, including for conflict minerals | Fibre composition, including microplastics data | Yes — appears in every group in some form |
| Carbon footprint | Broken down by lifecycle stage | Expected in equivalent form | Yes — and per part, not per plant |
| Recycled content | Recycled content data, with due diligence behind it | Expected, alongside recycler instructions | Yes — verification takes longer than collection |
| Supply chain actors | Due diligence and chain participants | Tier one to tier three supplier locations | Yes — the hardest and slowest to obtain |
| Performance and state | Capacity, cell chemistry, state-of-health metrics | Not equivalent | Group-specific — wait for the field list |
| Chemicals and treatment | Not equivalent | Chemical taxonomy used in dyeing | Group-specific — wait for the field list |
| Conformity | Proof of conformity | Expected in equivalent form | Yes — you likely hold this already, unstructured |
Watch the Battery Passport Even If You Make None
Three reasons it is the most informative thing happening in this space.
Who Owns It Internally
The question that stalls more readiness programmes than any technical issue. Five owners, and the last one is usually missing.
What to Do in the Next Twelve Months
Six moves, ordered by how long they take rather than by how urgent they feel.
Frequently Asked Questions
Only one date is currently fixed: 18 February 2027 for battery passports, covering electric vehicle batteries, industrial batteries above 2 kWh and light transport batteries, under the Battery Regulation rather than the ecodesign framework. Everything else arrives through delegated acts naming specific product groups — iron and steel with adoption work indicated from 2026, textiles, tyres and aluminium around 2027, furniture around 2028, electronics 2028 to 2029. Those are expectations, not statute, and they move.
No, and this is widely misread. That date is when the ecodesign framework reaches full application and the central registry — an index of unique product identifiers — goes live. It is the deadline for the Commission to stand up infrastructure, not a product obligation. No product-specific act has entered into force, which is why batteries remain the only category with a fixed statutory date. It matters to you because the technical architecture is being settled around it.
The arithmetic says no. A delegated act typically allows around eighteen months to compliance, and collecting verified supplier and material data is commonly estimated at twelve to eighteen months. Starting when your act publishes means finishing roughly when compliance begins, with no margin for a supplier who cannot answer or a verification step that runs long. Not being named yet means you have preparation time, not exemption.
The categories common to every group: material composition with geographic origin, carbon footprint by lifecycle stage, recycled content with the due diligence behind it, supply chain participants, and conformity evidence. Group-specific items like state-of-health metrics for batteries or dye chemistry for textiles can wait for the act. The fields change by product group; the categories do not, which is why a centralised data backbone beats waiting for a final list.
Three reasons. It is the proof of concept whose data model and carrier requirements later groups are expected to inherit, making it a preview of your own requirements. It is the only fixed date on the calendar, so it is where the practical lessons will emerge first. And exposure travels down the chain through requirements specifications — a component supplier into an electric vehicle programme will be asked for passport-grade data by a customer facing that deadline, well before any act names their own product group.
The supplier data dependency. Identifiers, carriers and integration are bounded technical work with published European standards to build against. Material composition, origin, recycled content and chain participants must come from companies you do not control, some of whom need to ask their own suppliers. That is the long pole, it cannot be compressed by spending more, and it is the only part where starting early genuinely changes the outcome.
Two places. Data held at the wrong granularity — passports attach to products, so plant-level or period-level figures cannot be apportioned credibly to a part number after the fact. And no single accountable owner, which produces four functions each completing their own contribution without anyone noticing that the parts do not join. Run a dry assembly on one product using only what you hold today; the gaps you find are your real programme scope. Start free with three assets and get the granularity right first.
