An EU brand sends you this request on a Tuesday morning.
“For PO #12345. 10,000 units of organic cotton T-shirts. Before first shipment, please share:
Fibre composition by weight, with certificates for any recycled content.
Where each production step happened. Cotton field, ginning, spinning, weaving, dyeing, finishing, stitching.
The chemicals used in the dyes and finishes for this batch.
Energy and water used to make this batch, per kilogram of fabric.
Social audit for the factory, valid on the date you ship.
Batch number and production date for every unit, linked to the GTIN we provide, in a format we can pull into our DPP.
Required by March 30. Data must be kept for ten years and shared with regulators on request.”
That request did not exist on the same PO twelve months ago.
It is now sitting in 2026 contracts from EU brands who are getting ahead of ESPR textile enforcement, expected in late 2027. The textile delegated act is still in preparatory work, with the Commission proposal expected later this year. The brand procurement teams are not waiting for any of that. They are writing the asks into contracts now. By the time the regulation is final, the buyer expectations will already be set.
If you can answer those six asks in two business days, you keep your seat at the buyer’s table. If your answer is two weeks of chasing certificates and emailing suppliers, you lose slots to a more ready competitor. You may not find out why.
The chasing is not random. It is the textile data interoperability problem playing out every Monday, and DPP enforcement compounds it instead of fixing it.
A note on where I am writing this from. I am an engineer. My team and I have spent twelve years building GS1 EPCIS-based traceability infrastructure. We built the backend for a Food Traceability Platform operated by GS1 Germany and Benelog GmbH, now connecting 770+ enterprises across Europe. The textile DPP problem looks structurally like the food traceability problem the platform we built already handles every day. Same data shape. Same supplier readiness pattern. This post is written from the systems side. I have not lived a year inside an Indian textile mill or an EU buyer’s compliance team. I would learn from anyone who has.
This post is about what the asks look like, what is in scope, and how to plan a response.
What the EU buyer is actually asking for
The six items in that request sit on top of nine mandatory attribute categories under the ESPR textile regulation. Read a request like this and the first reaction is usually, “yes, we have GOTS and OEKO-TEX, we are covered.”
You are not covered. The request is asking for something different.
Here is what each ask actually means.
1. Fibre composition with chain of custody for recycled content.
The label percentage is not the ask. The ask is to prove that the 30% recycled polyester is actually 30% recycled polyester. GRS or RCS scope certificates. Transaction certificates linked to your specific shipment. Most Indian exporters have the first. Few have the second tied to a specific PO.
2. Country of origin at each processing stage.
Not “Made in India.” That is for customs. The ask is: where was the cotton grown, where was it ginned, where was the yarn spun, where was the fabric woven or knit, where was it dyed and finished, where was it cut and stitched. Even for a fully Indian supply chain, the answer is in supplier contracts and in people’s heads. Not in a system that produces a structured response in minutes.
3. Chemical inventory of dyes, finishes, and auxiliaries.
Not facility-level conformance. The ask is to list the chemicals used to produce this specific batch. A ZDHC ClearStream report for the dyehouse is partial. It tells the buyer the dyehouse is approved. It does not tell the buyer what went on your fabric.
4. Allocated energy and water per kg of finished fabric.
A nuance worth getting right. ESPR does not require flow meters on every dye lot. It allows an allocated approach under PEF (Product Environmental Footprint) rules: facility energy and water for the relevant period, divided by production volume for that period, gives a defensible per-kg figure. What it does require is three things in structured form: facility energy and water data, structured production volumes for the same period, and an allocation method that holds up in an audit. Most Indian dyehouses cannot produce that combination on a two-day deadline. The gap is data management, not metering.
5. Social audit attestation valid at date of shipment.
This one most exporters get right. SMETA or equivalent, validity dates tracked. The friction shows up when the buyer asks for the same attestation for your sub-contractor. That is where the data starts thinning.
6. Per-unit batch and production data, linked to the brand’s GTIN.
This one is worth slowing down on, because most exporters read it and think they are being asked to build the QR code and the DPP. They are not.
The brand owns the GTIN. It is their product. The brand also designs the QR code, decides what it carries, and runs the GS1 Digital Link resolver that returns the DPP data when a consumer scans the tag. That entire layer is on the brand’s side.
What sits on the exporter’s plate is the data underneath. Batch number and production date for every unit, linked to the brand’s GTIN. The brand decides whether identifier granularity is per-batch (GTIN plus batch) or per-item (serialized GTIN) depending on SKU value. Production events captured in a structured form the brand can pull into their DPP. Ideally as EPCIS events, the GS1 standard for supply chain data. The physical printing of the QR code on the tag is part of your existing label work, done to the brand’s spec.
Most Indian exporters can print whatever QR code the brand hands them. Few can produce the structured event data that has to sit behind it. That is the actual technical gap. We have written about what compliant DPP implementation looks like in detail.
And the line most exporters skip past. Ten years of retention, shareable with regulators on request. A precision note: under ESPR, the legal duty to serve DPP data to EU authorities sits on the EU brand (the Economic Operator placing the product on the market). The retention ask flows down to you through contract, not directly through regulation. Either way, the buyer’s audit defense in year eight depends on the structured data you give them today. If it is not retrievable then, they cannot accept it now.
One request. Six asks plus a retention requirement. None of them unreasonable on their own. All of them different from what most Indian sustainability teams are currently set up to answer.
The 60% you have. The 40% you don’t.
We covered this in Indian garment exporters have 60% of EU DPP data, but the RFQ framing makes the picture sharper.
The fields you can answer today, in two business days:
- Fibre composition by weight
- Final country of origin
- Facility-level audit and certifications
- Test reports for durability and chemical safety
- GTIN at SKU level, for exporters who have done basic GS1 onboarding
The fields the typical RFQ asks for that you cannot answer in two business days:
- Recycled content with batch-linked chain-of-custody
- Country of origin per processing stage with evidence
- Chemical inventory at batch level
- Energy and water per kg at batch level
- Per-unit batch and production data linked to the brand’s GTIN, in a structured format
- Sub-tier supplier compliance documentation in retrievable form
- Production event history in EPCIS format, ready for a brand’s DPP resolver
Five of the six items in that request sit in the second list.
The first list is what you have. The second list is what the buyer is asking for. The two do not overlap as much as exporters assume they do.
How the asks tighten between now and 2027
Here is the trajectory the asks are on, from reading current RFQ language and brand sustainability material over the last eight months.
Today, May 2026. The asks are showing up as RFQ annexes. Some “best efforts” requests, some hard contract clauses. The buyer wants to know what you have. They are still flexible on the format. They are not yet rejecting suppliers for partial data. The EU’s central DPP registry goes live on 19 July 2026, which signals to brands that the broader infrastructure is being set up even before the textile-specific rules land.
Late 2026. The asks become standard procurement criteria. The Commission’s textile DA proposal is expected in this window. Two equally priced suppliers, one with the data ready, the other without. The data-ready supplier wins. The other supplier rarely gets told why.
Early to mid 2027. The format hardens. The buyer specifies that the data must be in EPCIS format, or compatible with their DPP resolver, or both. Suppliers who answered in PDFs and emails twelve months ago now face a different ask. The same data, in a machine-readable structure. The textile delegated act moves through formal adoption in this window.
Late 2027. ESPR textile enforcement begins. The buyer is no longer absorbing your compliance risk. They are pushing it back to you contractually. The data clauses are now backed by liability clauses. The phrase “in conformance with the applicable ESPR delegated regulation” starts appearing in standard terms.
A useful framing: the regulation is the floor. The buyer expectations are the ceiling. The ceiling is rising fast enough that exporters who match it now keep their slots. Exporters who match the floor only will be replaced by exporters who match the ceiling. The same window matters for GS1 Sunrise 2027 readiness. The underlying infrastructure overlaps almost completely.
The two-question test
Here is a test I have been mulling on. It cuts past the certificates and the audit reports.
Question one. If your largest EU buyer sends you the request at the top of this post tomorrow, and asks for a full response on a specific SKU, what is your honest delivery time? Two business days, or two weeks?
Question two. If you took twelve hours to respond, and the response was complete, what would change in that buyer’s procurement decision for the next season?
The answer to question one tells you where you are. The answer to question two tells you what is at stake.
Where I expect the typical answer to land, based on the few conversations I have had so far: Question one, two weeks if everything goes well, four weeks if the dyehouse is slow. Question two, a bigger allocation, or a buyer the exporter has been chasing for years.
The gap between two days and two weeks is not a small operational difference. It is the difference between being the supplier the buyer reaches for and the supplier the buyer falls back to.
What “two weeks” actually costs
The two-week response time is not a cosmetic problem. Here is what it produces in practice.
Lost orders. The buyer is running a procurement window of three weeks. You take two of those three weeks just to answer the data ask. You answer late. The slot goes to a supplier who answered in three days. You are told the order went elsewhere. No reason given.
Longer payment cycles. The buyer’s compliance team withholds approval until the data is verified. Verification takes time because your data came in as scanned PDFs and email threads. The PO is held. Your working capital cycle lengthens.
Audit risk transferred to you. If the buyer accepts incomplete or unstructured data, and the regulator later asks for it, the buyer has the right under most contracts to ask you for it again. You may not have it anymore. It was in a WhatsApp thread that someone left the company a year ago.
Slot loss you cannot trace. The most expensive cost is the order that never enters your inbox, because the buyer’s procurement team quietly downgraded you from “preferred” to “fallback” after a previous round. You will not find out. The exporters who lose this way often do not realize they lost it.
The cost of two weeks is not the two weeks. It is the procurement preference you lose by the third RFQ.
What a two-day response actually requires
Before signing off, the practical bit. A two-day response is not a heroic feat. It is the output of three things being in place upstream.
A product master that knows what each SKU is made of. Fibre composition, sub-component bill of materials, supplier and processing stage for each component, certifications associated with each. Most ERPs hold a partial version of this. Almost none of them hold it in DPP-ready structure.
An evidence vault. Every certificate, every test report, every audit attestation, ingested once, hashed, validity windows tracked, retrievable by SKU or by supplier or by batch. This is the system most exporters do not have. Its absence is the actual reason data requests take two weeks.
An event layer that records who did what to what, when. EPCIS events covering production, transformation, and shipping. Captured from your shop floor and from your suppliers, in whatever input mode they can support. The output is a structured event history that survives across buyers and across years.
Those three blocks are the difference between two days and two weeks. They are not optional if you want to be the supplier the buyer reaches for in 2027. The roughly eighteen months between now and ESPR textile enforcement is enough time to put them in place. Buyer procurement preference will tighten well before that. Starting in 2027 is starting late.
If you run a vertically integrated mill, you have a structural head start on those three blocks. We covered why in vertical integration is now a DPP sales weapon for Indian mills.
A diagnostic worth running this week. Take one live PO. Pretend the request at the top of this post is part of it. Set a clock. See how long your team takes to produce a structured response covering all six asks.
If the answer is two days, you are ahead of where most Indian exporters sit today.
If the answer is two weeks, you are where most of the market sits. You also know what the buyer learns the next time they ask.
If the answer is “we cannot, the data is not in a system,” the diagnostic is doing its job. That is the answer that tells you where to start.
When you run this on a live PO, what choke point do you think you’ll hit? My guess, viewed from the systems side: the batch-level chemical inventory, or the recycled content chain of custody. I have not done enough of this work specifically inside Indian textile mills to know the real order. If you have, tell me where the friction actually lives.
