DPP-Ready Supplier: The Data Your Supplier Must Provide You for the DPP

What is the DPP and why can it not be completed without supplier data?

The Digital Product Passport (DPP) is a traceability instrument that the EU plans to introduce for priority product groups, including textiles, under the Ecodesign for Sustainable Products Regulation (ESPR). Although the framework has entered into force, the product-specific mandatory data fields are being defined incrementally, through delegated acts due in 2027 and beyond; the right move today is therefore to focus not on a fixed date but on building a "data-ready" supply chain. For the design and data logic of the framework, see our EU Ecodesign / ESPR guide, and for supplier selection, our ESPR/DPP and supplier selection article.

The critical point is this: the data forming the backbone of the DPP is controlled not by the brand but by the upstream supplier. What the fibre is, where the yarn comes from, in which mill the fabric was knitted, with which dye chemistry and recipe it was processed, and which certificates cover it — all of this originates with the fabric manufacturer and the dye/print/finishing plant. The buyer cannot guess this data after the fact; it must be requested at the contract and sample stage. In a single-coordinator structure (in-house knitting + contract dye/print/finishing through a vetted network under one point of contact) this chain can be reported from a single source, reducing data gaps and "who is responsible" ambiguity; the coordinated contract network advantage here translates directly into data quality.

Which core DPP data fields should you request from your supplier?

Dividing DPP data fields into four blocks is a practical working method: (1) identity and traceability, (2) material and composition, (3) chemical and environmental compliance, (4) sustainability metrics. The table below shows the fields typically to be requested, where this data is generated in the supply chain, and whether KARCEM — knitting in-house and coordinating dye/print/finishing through a vetted contract network — can provide it.

The distinction here matters: some fields are ready today and can be reported on a sample/batch basis (composition, origin, certificate, fastness); other fields (product-level carbon/water) are provided incrementally as the calculation methodology and delegated act become clear. Keeping the two categories separate in the supplier contract is the soundest approach for realistic commitment and auditable data.

In what format and with what evidence should you request each data field?

The value of the DPP lies in the data being machine-readable and verifiable; free-form expressions such as "cotton, certified, compliant" are therefore inadequate. For each field, you should request (a) the data itself, (b) the evidence that verifies it, and (c) the validity/batch context. The table below summarises the correct format and type of evidence for frequently requested fields.

A practical suggestion: turn these fields into a single supplier data template (a standard set of columns on the buyer side) and have the same template completed for every new development/batch. This way, data from different suppliers is collected in the same structure, and later transfer into the DPP platform requires no manual clean-up. With a supplier such as KARCEM knitting in-house and coordinating dye/print/finishing through a vetted contract network under one point of contact, consistency is high because every row of the template can be populated from a single source; for upstream inputs such as yarn, a document chain is requested.

How do you establish traceability at batch level?

The DPP must answer not only "what does the product contain" but also "where is the evidence for this specific batch". For this, traceability must not break along the chain: yarn input → knitting batch → dye/print/finishing batch → laboratory test → shipment. Each link must carry the reference of the previous link. When a single coordinator owns the chain, because the link between in-house knitting and the contracted dye/print is kept within one coordinated record, the most common break — "the fabric manufacturer and the dyehouse don't talk to each other" — where data is lost is eliminated.

• Single reference backbone: Each fabric batch is given a unique tracking number, and all documents (composition, recipe, test) are linked to this number.
• Stage linking: Which yarn lot the knitting batch is based on, and which recipe the dye/print batch relies on, is recorded; the choice of reactive/disperse dyeing and the recipe parameters are part of the batch record.
• Attaching the evidence: Colour fastness, ΔE and dimensional stability results are archived under the same batch number.
• Certificate mapping: Which certificate scope the shipped product falls under (GOTS/OCS/GRS/RCS) is associated through the document chain; the GOTS/RCS and carbon context is established at this point.

Once this structure is in place, completing the DPP for a buyer becomes not "reproducing the data" but "exporting the existing batch record". Because retrospective traceability is generally costly and error-prone, the right time is to establish data discipline at the sample/approval stage.

What is realistic to request today for sustainability metrics (carbon/water)?

In textiles, the bulk of the product carbon footprint arises upstream (fibre production, yarn, energy-intensive wet processes); a meaningful figure at brand level can therefore only be calculated with supplier process data. Here, rather than giving an invented number, the right approach is to agree on the methodology and data source. Our Scope 3 carbon and low-water sustainable dyeing content explains which process decisions this calculation depends on.

One must also be cautious on the regulatory side: in which product group, in what detail and on what timetable the carbon and water fields will become mandatory in the DPP will be determined incrementally, through 2027+ delegated acts. Accordingly, the most robust position today is to have "set up the data-collection infrastructure and defined the methodology"; let us clarify precise numerical commitments together once the scope is settled. For the broader regulatory framework, see our CBAM/EPR/CSDDD and sustainability-regulation guide.

Which questions should you ask before accepting your supplier as DPP-ready?

The most practical test is to request a sample DPP data set from the supplier for a real batch. Seeing a completed template rather than a declaration quickly reveals data maturity. The following checklist can be used in sample/approval discussions:

1. Can you provide composition, origin, certificate no. and fastness data linked to the same batch reference?
2. Can you evidence ZDHC/MRSL and REACH-SVHC compliance with a current declaration/test?
3. Can you provide a document chain for upstream inputs such as yarn?
4. Are knitting and dye/print/finishing coordinated under one point of contact, or is the data fragmented across unmanaged firms?
5. Which data do you collect today for carbon/water metrics, and which methodology do you use?

A single coordinated chain is a decisive advantage in answering these questions: when the chain from knitted yarn to fabric, to the contracted dye/print/finishing batch and its test is kept within one coordinated record, the "DPP-ready" claim can be evidenced with a single batch record. To view supplier selection criteria holistically, take a look at our sourcing/procurement guide and our ESPR/DPP supplier selection article.

Frequently asked questions

At minimum, which core data fields should I request from my supplier for the DPP?

At a minimum, request these core fields: full fibre composition (by %), origin (spinning/knitting/finishing country and facility), proof of chemical compliance (ZDHC/MRSL, REACH-SVHC), valid certificate numbers and scope, and product identity/lot traceability. Without these, the passport skeleton cannot be filled. A practical approach is to group the fields into four blocks: identity and traceability, material and composition, chemical and environmental compliance, and sustainability metrics.

Should I request the data as a free-text declaration or in a specific format?

Request structured, evidence-backed data rather than free text. Composition as a percentage (e.g. 95% cotton / 5% elastane); certification with a number plus a scope (Scope/TC) document; chemical compliance with a current ZDHC/MRSL declaration or test report; colour fastness with the relevant ISO/AATCC method and result value. For each field, ask for the data itself, the evidence that verifies it, and the lot context; this automates the transfer into the DPP.

How is lot-level traceability set up in practice?

Each fabric lot is assigned a unique tracking number, and all documents (composition, recipe, testing) are linked to that number. The chain must not be broken: yarn input, knitting lot, dye/print/finishing lot, laboratory testing, shipment; each link carries the reference of the previous link. Colour fastness, ΔE and dimensional stability results are archived under the same lot number. The right time to establish this discipline is at the sampling/approval stage, not retroactively.

For sustainability data such as carbon and water, what is realistic to request today?

The realistic ask today is not a single precise figure, but defining the methodology (scope, boundaries, data source) and starting to collect the available process data. In textiles, the bulk of the carbon footprint arises upstream (fibre, yarn, energy-intensive wet processing), so the figure can only be calculated with supplier process data. Rather than a made-up number, agree on the methodology; numerical commitments will firm up as the post-2027 delegated acts are clarified.

How do I test whether a supplier is genuinely DPP-ready?

Test along four axes: can they provide the data in a structured format, do they establish lot-level traceability, do they keep chemical/certificate evidence up to date, and have they defined a methodology for sustainability metrics? Instead of a verbal 'yes', request a sample, completed DPP data set for a real lot; this quickly reveals data maturity and shows whether the declaration is genuine.

Why is a single coordinator across a vetted network advantageous for DPP data?

In a single-coordinator structure, knitting is in-house and dyeing/printing/finishing are run through a vetted, geographically close contract network under one point of contact, so the chain can be reported from a single source; data gaps and 'who is responsible' uncertainty are reduced. The 'fabric manufacturer and dyer don't share data' break, where data loss most often occurs, is eliminated. From its Esenyurt/Istanbul base, KARCEM provides composition, origin, certificate scope (GOTS/OCS/GRS/RCS), ZDHC/MRSL compliance and colour fastness/ΔE<1 data linked to a lot reference.