DPP and the Collection Calendar: What Data You Need and When
A practical guide to mapping Digital Product Passport requirements onto your product development timeline—from tech pack to launch.
- The EU Digital Product Passport requires data from multiple departments at different stages of product development
- Tech pack phase captures ~40% of required DPP fields; sourcing and production phases fill the rest
- Aligning data collection with existing workflows prevents last-minute scrambles before market launch
- Three data tiers—design, supply chain, and post-production—map cleanly onto the standard collection calendar
- Starting DPP integration 18+ months before the 2027 textile deadline gives brands time to build robust processes
The timing problem nobody talks about#
Most conversations about Digital Product Passport compliance focus on what data you need. Fewer address the equally critical question: when does that data actually become available?
Fashion product development follows a predictable rhythm. A Fall/Winter collection typically begins 12–18 months before retail launch. The EU's Ecodesign for Sustainable Products Regulation (ESPR) requires that by the time a garment reaches the market, its DPP must contain verified information spanning the entire lifecycle—materials, manufacturing, care, repairability, and end-of-life options (European Commission, 2024).
The mismatch is obvious: you cannot populate a passport with production data during the design phase. But waiting until production ends leaves no buffer for verification. The solution is systematic: map each DPP data category to the collection phase where it naturally emerges.
Three tiers of DPP data#
The ESPR delegated acts for textiles (expected finalisation in 2025) will specify exact fields, but draft technical standards from CEN/CENELEC already outline the categories (CEN-CENELEC, 2024). These cluster into three tiers based on when information becomes concrete:
Each tier builds on the previous. Tier 1 sets intentions; Tier 2 confirms sourcing; Tier 3 records what actually happened.
Mapping data to your calendar#
For a typical 15-month development cycle, here is when each data category should be captured and verified:
| Collection Phase | Timeline | DPP Data Available | Key Actions |
|---|---|---|---|
| Concept & Design | T-15 to T-12 months | Product identifiers, material targets, care codes | Create DPP skeleton; assign unique identifiers |
| Sourcing & Development | T-12 to T-8 months | Supplier info, fibre certifications, country of processing | Collect supplier declarations; verify certifications |
| Sampling | T-8 to T-5 months | Final BOM, tested compositions | Lock material data; reconcile lab tests |
| Production | T-5 to T-2 months | Batch IDs, production facility, actual quantities | Capture per-order manufacturing data |
| Pre-Launch | T-2 to T-0 | Sustainability metrics, repair info, QR linkage | Final verification; generate DPP carriers |
T-0 = retail launch date
The critical insight: by the time you reach production, 60–70% of your DPP fields should already be populated. Production adds batch-specific details, not foundational information.
Where brands typically stumble#
In pilot programmes across European fashion companies, three friction points recur (Sustainable Apparel Coalition, 2024):
1. Supplier data arrives too late. Mills and CMT factories often provide composition certificates only at shipment. For DPP purposes, you need this data earlier—ideally at sampling—to catch discrepancies before bulk production.
2. PLM systems lack DPP-ready fields. Most product lifecycle management tools were built before DPP requirements existed. Custom fields or middleware integrations become necessary, and these take time to implement.
3. No single owner. DPP data spans design, sourcing, sustainability, and compliance teams. Without clear ownership at each phase, information falls through the cracks.
A phased implementation approach#
Brands targeting the 2027 textile deadline should work backwards:
- 2025: Audit current data availability against draft ESPR requirements. Identify gaps.
- 2026 H1: Pilot DPP data collection on one capsule collection. Stress-test supplier workflows.
- 2026 H2: Scale to full seasonal collection. Integrate with labelling and packaging timelines.
- 2027: Full compliance for all applicable products.
This timeline assumes the Commission's delegated acts are adopted by late 2025, as currently projected (European Commission, 2024).
Frequently asked questions
Do I need final production data before I can create a DPP?
No. The DPP is designed to be progressively populated. You create the passport at the design phase with a unique identifier, then enrich it as data becomes available. The passport must be complete by the time the product is placed on the market—not before.
What if my suppliers cannot provide the required data?
This is a common concern. The ESPR places the compliance obligation on the entity placing the product on the EU market—typically the brand. You will need contractual clauses requiring suppliers to furnish specific data points. Start renegotiating supplier agreements now; many are already preparing for similar requests from other brands.
Can I use the same DPP template across all SKUs?
Partially. Static fields (brand info, care instructions, repair guidance) can be templated. But material composition, supplier facilities, and batch data must be SKU- or order-specific. A well-structured data model separates reusable templates from variable fields.
Building the muscle now#
The brands that will navigate 2027 smoothly are those treating DPP not as a labelling exercise but as a data infrastructure project. Every collection cycle between now and the deadline is an opportunity to refine your process.
Trama helps fashion brands structure DPP data collection across the product development timeline—connecting PLM systems, supplier portals, and compliance workflows into a single source of truth. If mapping your collection calendar to DPP requirements feels daunting, that's exactly what we built for.
Generate your collection's passports
From product sheet to compliant, hosted, print-ready QR codes.
Get started