A digital product passport (DPP) is a structured, machine-readable record that travels with a garment from raw material to end of life. For a denim SKU, it is not a marketing document—it is a data obligation. Production teams that wait for their compliance department to figure it out will find themselves scrambling to backfill information that should have been captured at the very first supplier conversation.
This guide walks you through the specific data fields you need to gather, where in the production workflow you collect them, and what is still unresolved as the denim pilot programme moves forward.
Key takeaways
- A denim DPP requires structured data across at least five categories: fibre origin, chemical use, recycled content, care instructions, and end-of-life guidance.
- Data collection must start at raw-material sourcing, not at the finished-goods stage—retrofitting is expensive and often incomplete.
- The denim pilot programme is actively working to define which fields are mandatory versus recommended, so your internal template should flag that distinction clearly.
- Production managers, not just sustainability teams, own most of the underlying data—it lives in your BOM, your mill certifications, and your chemical compliance sign-offs.
- A DPP is only as good as the chain of custody behind it; undocumented claims will not pass audit.
What is a digital product passport and why does denim get its own pilot?
A digital product passport is a digital record—typically accessed via a QR code, RFID tag, or data carrier on the product—that contains verified information about a product's materials, manufacturing processes, repairability, and end-of-life options. The concept is central to the EU's Ecodesign for Sustainable Products Regulation (ESPR), which is rolling out sector by sector.
Denim was selected as one of the early textile categories for piloting because it has a well-documented environmental footprint—water-intensive cotton cultivation, indigo dyeing, and stonewashing—and because the supply chain, while complex, is traceable enough to make a pilot feasible. WWD reported in August 2026 that a new DPP pilot is bringing together Denim Deal's network of partners to give denim suppliers a competitive edge through early adoption.
For production teams, the practical implication is straightforward: a denim SKU will eventually need a machine-readable record that a regulator, a retailer, or a recycler can query. The question is not whether you will build one—it is whether you build it correctly the first time.
Which data fields does a denim DPP require?
The field set is still being finalised through pilot programmes, but the categories below represent the current working consensus among industry bodies and the pilot participants. Think of each category as a section of your DPP data schema.
1. Fibre origin and material composition
This is the foundation. You need:
- Fibre type and percentage — e.g., 98% cotton, 2% elastane. This must match the care label declaration and be traceable to a specific mill or spinner.
- Country of fibre origin — where the cotton was grown or the synthetic fibre was produced, not where the fabric was woven.
- Certification status — whether the cotton carries a recognised standard (organic, Better Cotton, or equivalent). The certification number and issuing body belong in the record.
- Yarn count and construction — relevant for recycled-content verification because blended yarns complicate percentage claims.
Where to collect it: your fabric BOM and mill certification pack. If your mill cannot provide country-of-fibre-origin documentation, that is a sourcing conversation you need to have now.
2. Chemical use and restricted substance compliance
Denim finishing is chemically intensive. The DPP needs:
- Dyestuff identification — the indigo or synthetic dye used, including CAS numbers where available.
- Finishing chemistry — stonewash enzymes, softeners, resins used for stretch recovery, and any coating applied.
- MRSL/RSL compliance declaration — a reference to which restricted substance list the product was tested against, the testing laboratory, and the test date.
- Wastewater treatment confirmation — some pilot frameworks are asking for a declaration that the manufacturing facility treats effluent to a defined standard.
This data typically lives with your wet-processing supplier or laundry. If you outsource finishing, you need a signed chemical compliance declaration in your supplier file—not just a verbal assurance.
3. Recycled content and circular material claims
If your denim contains recycled cotton, recycled polyester, or any post-consumer fibre, the DPP must substantiate that claim:
- Recycled content percentage by weight — broken down by fibre type.
- Source of recycled material — pre-consumer (cutting waste) or post-consumer (collected garments). These are treated differently under most certification schemes.
- Chain-of-custody certificate — the certification body, certificate number, and scope. Global Recycled Standard (GRS) and Recycled Claim Standard (RCS) are the most common frameworks.
- Traceability to the recycling facility — the name and location of the facility that processed the waste into fibre or yarn.
The Ellen MacArthur Foundation has published guidance on circular material claims in fashion, and its framework for distinguishing pre- and post-consumer recycled content is a useful reference when you are setting up your internal data schema.
4. Care and use instructions
Care instructions are already mandatory on garment labels in most markets, but the DPP version needs to be machine-readable and more detailed than a symbol strip:
- Washing temperature and cycle type — expressed as a value, not just a symbol, so it can be read by smart appliances.
- Drying method — tumble dry settings or line-dry recommendation, with the reason (e.g., elastane degradation risk at high heat).
- Ironing and bleaching guidance — including explicit prohibitions.
- Repair guidance — basic information about common denim repairs (re-riveting, seam reinforcement) supports the repairability dimension of the ESPR.
This section is the one most likely to be managed by your product development team rather than production, but production needs to verify that the care instructions on the DPP match the actual construction—particularly if the fabric or finish changes between sampling and bulk.
5. End-of-life and disassembly guidance
This is the section that most production teams have the least existing data for:
- Recyclability assessment — whether the garment, as constructed, can be mechanically or chemically recycled. Blended fabrics, bonded seams, and non-removable trims all affect this.
- Disassembly instructions — which components need to be removed before recycling (metal rivets, zips, labels with non-textile substrates).
- Take-back or collection scheme information — if the brand participates in a take-back programme, the DPP should reference it.
- Material hazard flags — any components that should not enter standard recycling streams (certain dyes, PFC-based water-repellent finishes).
For most denim SKUs, the recyclability assessment requires input from a textile recycler or a third-party assessor. This is not something your production team can self-certify without external validation.
How does a DPP connect to your existing production documents?
You are not starting from zero. Much of the data a DPP requires already exists somewhere in your workflow—it is just not structured or centralised.
| DPP data category | Where it currently lives |
|---|---|
| Fibre origin and composition | Fabric BOM, mill spec sheet |
| Chemical compliance | MRSL test report, supplier declaration |
| Recycled content | Chain-of-custody certificate |
| Care instructions | Tech pack, care label spec |
| End-of-life guidance | Rarely documented—needs new process |
The practical challenge is that these documents sit in different systems, are owned by different teams, and are formatted inconsistently. Building a DPP means creating a data collection workflow that pulls from all of them into a single structured record at the point of bulk sign-off.
If you work with a PLM system, the DPP data schema maps reasonably well onto existing BOM and compliance modules—but most PLM configurations will need new custom fields, particularly for end-of-life data and chain-of-custody certificate references. Our look at production workflows in the context of AI ambitions versus production reality covers some of the structural gaps that make data centralisation harder than it looks.
What does the denim pilot programme tell us about mandatory versus recommended fields?
The pilot is still running, and the field set is not fully locked. Based on what has been reported publicly, including the WWD coverage of the Denim Deal pilot, the intent is to give suppliers a competitive advantage through early adoption rather than to penalise laggards immediately.
In practice, that means:
- Mandatory fields (expected to be enforced once the regulation is finalised) will likely cover composition, country of origin, and care instructions—data that already has label-law precedent.
- Recommended fields in the pilot phase include end-of-life guidance and detailed chemical use records, but these are expected to become mandatory over time.
- Pilot-specific fields being tested include repairability scores and water-use data at the fabric production stage—these may or may not make it into the final regulation.
Build your internal template to capture all categories now, but flag which fields are currently mandatory versus in-progress. That way you can report on your readiness honestly and close gaps systematically.
What is still unresolved?
Honesty matters here. Several things are genuinely unsettled:
Verification and audit standards. The DPP framework specifies what data must be present, but the mechanism for verifying that data is accurate—third-party audit, blockchain anchoring, self-declaration—is still being worked out. A DPP with unverified claims is a liability, not an asset.
Data carrier standards. Whether the DPP is accessed via a QR code, an NFC chip, a GS1 Digital Link, or some other carrier is not yet uniform across markets. Your IT and labelling teams need to track this.
Interoperability between systems. If your mill uses one data format and your brand's DPP platform uses another, someone has to do the translation. The pilot is surfacing these friction points, but solutions are not standardised yet.
Liability for upstream data. If your mill provides incorrect fibre-origin data and you pass it through to the DPP, who is liable? The legal frameworks here are still developing.
For production managers, the honest answer is: build the data collection process now, be transparent about what is verified versus declared, and stay close to the pilot outputs as they are published. Sourcing Journal has been tracking the regulatory timeline closely and is worth monitoring for updates.
A practical starting checklist for your production team
Before your next denim development season, work through these steps:
- Audit your current BOM template — does it capture country of fibre origin, not just country of fabric manufacture?
- Review your mill and laundry supplier agreements — do they include a requirement to provide MRSL test reports and chemical declarations?
- Identify your chain-of-custody gaps — if you make recycled-content claims, do you have the certificates to back them up at SKU level?
- Map your care instruction data — is it stored in your tech pack in a structured, exportable format, or as a free-text note?
- Start the end-of-life conversation — contact your trim suppliers about rivet and zip removability, and ask your fabric supplier about recyclability assessments.
- Define your DPP data owner — this is a production and compliance function, not a marketing one. Assign it explicitly.
Our guide to tech pack software built for production covers how structured data fields in a tech pack connect to downstream compliance workflows—relevant context as you think about where DPP data should live in your system.
FAQ
What is a digital product passport in fashion? A digital product passport is a structured data record attached to a physical product—typically via a QR code or RFID—that contains verified information about its materials, manufacturing, care, and end-of-life options. It is required under the EU's Ecodesign for Sustainable Products Regulation for textile products.
When do denim brands need to comply with DPP requirements? The regulation is being phased in by product category. Denim is part of an active pilot programme, and mandatory compliance dates for textiles are expected to follow the finalisation of the ESPR delegated acts. Production teams should treat the pilot timeline as a preparation window, not a grace period.
What is the difference between a DPP and a care label? A care label is a physical, human-readable label with washing and drying symbols. A DPP is a machine-readable digital record that includes care data plus material origin, chemical compliance, recycled content, and end-of-life guidance. The DPP replaces nothing on the physical label—it adds a structured digital layer.
Who in a production team owns the DPP data? Ownership is distributed. Fibre origin and composition come from sourcing and the fabric BOM. Chemical compliance comes from the wet-processing supplier. Care instructions come from product development. End-of-life data requires input from external assessors. A single data owner needs to be assigned to consolidate and validate all of it.
Can a PLM system generate a DPP automatically? Not yet, for most brands. PLM systems hold much of the underlying data, but DPP output formats and data carrier standards are not yet natively supported in most platforms. Custom field configurations and export integrations are typically required. This is an area where the tooling is catching up to the regulation.
What happens if a supplier provides incorrect data for a DPP? The legal liability framework is still developing, but the practical risk is significant: an inaccurate DPP that is audited or challenged exposes the brand to regulatory and reputational consequences. Supplier agreements should include explicit data accuracy warranties for DPP-relevant information.