Short answerA Digital Product Passport readiness roadmap typically spans 12 to 24 months in six phases: inventory existing product data, analyse gaps against the relevant delegated act, collect supplier data, assign system ownership per attribute, run a pilot on one product line, then scale across the catalogue. Supplier data collection usually sets the critical path.
Key takeaways
- Most organisations need an estimated 12 to 24 months to reach passport readiness, depending on catalogue size, supplier count and data maturity.
- Supplier data collection is usually the longest phase, often taking an estimated 6 to 12 months for strategic suppliers alone.
- The battery passport deadline of 18 February 2027 leaves battery manufacturers the least time, while textile and steel acts are expected to apply from 2028 onwards.
The roadmap runs in six phases with supplier data as the critical path
DPP readiness follows a predictable sequence regardless of sector. The six phases are data inventory, gap analysis, supplier data collection, system ownership, pilot product and scale-up. Phases overlap in practice, and supplier data collection runs longest because it depends on external parties with their own priorities.
The starting point depends on deadlines. Battery manufacturers face the battery passport from 18 February 2027 and must compress the plan. Companies in ESPR priority groups such as textiles, furniture or steel have more time, since delegated acts are expected from late 2026 for iron and steel and from 2027 for textiles, with application typically at least 18 months later. Both groups benefit from starting the slow phases now.
Phases one and two: inventory the data and measure the gaps
The inventory establishes what product data exists, where it lives and who maintains it. A cross-functional team from product data, sustainability, compliance, sourcing and IT lists every candidate passport attribute and maps it to a source system, an owner and a quality level.
The gap analysis compares that inventory with the requirements of the relevant act or preparatory study. Useful classifications per attribute:
- Available and structured: ready for automated feeds.
- Available but unstructured: held in PDFs, free text or spreadsheets.
- Held by suppliers: needs collection and verification.
- Not yet measured: requires testing, calculation or new processes, such as a carbon footprint.
The ESPR guide lists the information requirements to test against. The output is a prioritised gap list with effort per attribute group.
Phases three and four: collect supplier data and assign ownership
Supplier data collection starts as soon as the gap list is stable. Strategic suppliers covering the largest volume come first, with a shared template for materials, origin, substances, recycled content and certificates. Contracts and supplier codes of conduct should add data obligations, including update frequency and evidence formats.
System ownership runs in parallel. Each attribute receives one system of record and one accountable role. PLM typically owns materials and composition, ERP owns identifiers and batches, PIM owns consumer-facing content, and a DPP service provider assembles and publishes the passport. The DPP data architecture article explains how these systems connect, and governance practices are covered in the product data quality guide.
Phases five and six: pilot one product line, then scale
The pilot proves the end-to-end chain on a single product line with a manageable number of articles and suppliers. It should include real identifiers, a printed data carrier, live access tiers and at least one external reader, such as a recycler or repairer, testing the restricted data. A good pilot product line has high volume, few components and cooperative suppliers.
Scale-up extends the proven pattern across the catalogue in waves, ordered by regulatory deadline and revenue. Automation matters most here: data quality rules, completeness dashboards and supplier portal workflows replace the manual effort that carried the pilot.
Effort ranges by phase
The following ranges are estimates for a mid-sized manufacturer or brand with several thousand active articles and 50 to 200 direct suppliers. Actual effort varies with data maturity and sector.
| Phase | Duration (estimate) | Internal effort (estimate) | Main roles |
|---|---|---|---|
| 1. Data inventory | 1 to 2 months | 40 to 80 person-days | Product data, IT, compliance |
| 2. Gap analysis | 1 to 2 months | 30 to 60 person-days | Sustainability, compliance, product data |
| 3. Supplier data collection | 6 to 12 months | 100 to 250 person-days | Sourcing, sustainability, suppliers |
| 4. System ownership and integration | 3 to 6 months | 80 to 200 person-days | IT, enterprise architecture, data owners |
| 5. Pilot product line | 3 to 4 months | 60 to 120 person-days | Cross-functional pilot team, DPP provider |
| 6. Scale-up | 6 to 12 months | 150 to 400 person-days | Data stewards, sourcing, IT |
Fund readiness as a data programme
The central insight is that DPP readiness succeeds when budgeted as a product data programme with a regulatory deadline, owned jointly by sustainability and product data leadership. Passport software is the smallest cost item. The larger costs sit in supplier engagement, attribute cleansing and integration, which also improve channel content and compliance reporting. A business case for product content platforms can carry these shared benefits.
Frequently asked questions
How long does Digital Product Passport readiness take?
An estimated 12 to 24 months for most mid-sized organisations. Companies with structured PLM and PIM data and established supplier portals sit at the lower end. Companies relying on spreadsheets and with deep, unmapped supply chains sit at the upper end or beyond.
Which phase should start first?
The data inventory starts first, because every later phase depends on it. Supplier outreach should begin as soon as the gap analysis identifies supplier-held attributes, since it is usually the longest phase and determines the overall timeline more than system work does.
What makes a good DPP pilot product?
A good pilot product line has meaningful volume, a simple bill of materials, a small number of cooperative suppliers and falls within an upcoming delegated act. It should test real identifiers, printed data carriers, access tiers and at least one external reader.