Founding offer The Founding Partner Program is open — 1,000 companies, 6 months free. Start free →
Textile

Textile DPP: The Data You'll Need to Provide

Fibre composition, origin, chemicals and circularity — a field-by-field look at what the EU textile Digital Product Passport is expected to require, and where that data actually lives.

9 min read · Updated Oct 2026
Denim garments on a rail

Textiles were among the first product groups named in the ESPR working plan, and for good reason: the sector combines long, opaque supply chains with high volumes and low recycling rates. The delegated act that sets the exact requirements is indicated for (expected), with a transition period after that. This article describes what the direction of travel already makes clear — and, more usefully, where each piece of data tends to hide inside a real textile business.

The field map at a glance

Before the field-by-field detail, the shape of the whole thing. The third column is the one worth reading twice: it is where projects actually stall.

Field groupWhat is expectedWhere it lives todayThe usual gap
IdentityProduct, operator and facility identifiersGTIN in the ERP or PIMOperator and facility identifiers do not exist yet
CompositionFibre percentages, per component; recycled content stated separatelyTech pack, supplier material declarationThree versions disagree — label, tech pack, supplier system
OriginCountry at minimum, pressure toward stage levelPurchase orders, supplier declarationsUnstructured; needs a collection workflow, not a query
Substances of concernPresence above threshold, specific enough for recyclersTest reports, chemical declarationsPDFs in a shared drive, not matched to batches
Durability and careCare instructions, lifetime indicators, repair informationCare labelling specificationsMostly a copy exercise — the cheapest section to fill
CircularityRecyclability, separation guidance, disposal instructionsUsually nowhereHas to be created from the bill of materials
FootprintEnvironmental impact data, methodology unsettledNowhere, unless an LCA existsA separate workstream, not a software feature

Product identification

Every passport begins with identity. You need a unique product identifier — in practice a GTIN encoded in GS1 Digital Link — plus an operator identifier for the responsible economic operator and, increasingly, facility identifiers for the sites involved in production. EN 18219 defines all three identifier types, which is why "which factory made this order" is passport data and not just internal record-keeping.

Where it lives: the GTIN is usually in your ERP or PIM. Operator and facility identifiers frequently do not exist yet and must be obtained. This is a small task that surprises people by sitting on the critical path.

Material composition

Fibre content by percentage, at the level of the product and, for multi-component articles, per component. Recycled content is stated separately from virgin material, and claims about recycled content need to be substantiated rather than asserted. The fibre names themselves are not free text: Regulation (EU) No 1007/2011 already fixes the official designations, and only those names may be used to describe fibre composition (Article 5(1), Annex I) — use them in the passport field too; the field's exact validation will be set once the textile delegated act and the registry's data model exist.

Where it lives: the tech pack and the supplier's material declaration. The trap is that composition often exists in three slightly different versions — one on the label, one in the tech pack, one in the supplier's own system — and the passport forces you to pick one and stand behind it.

Origin and traceability

Expect country of origin at minimum, with pressure toward stage-level traceability: where the fabric was woven or knitted, where it was dyed and finished, where it was cut and sewn. The direction is clearly toward more granularity, not less.

Where it lives: purchase orders and supplier declarations, rarely in a structured form. This is the field that most often requires a supplier data-collection workflow rather than a database query.

Substances of concern

Presence of substances of concern above threshold, with enough specificity for recyclers to handle the material safely. This connects the passport to REACH and to your existing restricted substances list.

Where it lives: test reports and supplier chemical declarations, usually as PDFs in a shared drive. Passport software should let you attach and version these, not just store a yes/no flag.

Durability, care and repairability

Care instructions, expected lifetime indicators, availability of spare parts or repair services where relevant. For textiles the durability metrics are less mature than in electronics, but care and repair information is a low-cost field to populate and a high-value one for consumers. Care data is stored as ISO 3758 symbol codes rather than as pictures of the label — the passport page renders the graphic from the code.

Where it lives: care labelling specifications — already produced for the physical label, so this is mostly a copy exercise.

Circularity and end of life

Recyclability information, guidance on separating components, and instructions for correct disposal. This is the section recyclers actually open, and it is the least populated section in most early passports.

Where it lives: usually nowhere yet. It generally has to be created, by working backwards from your bill of materials.

Environmental footprint

The delegated act is expected to reference environmental impact data. The methodology question — full PEF study, simplified footprint, or supplier-declared values — is not fully settled, and honest vendors will tell you so rather than promise a number.

Where it lives: nowhere, unless you have already run an LCA. Budget for this as a separate workstream, and be sceptical of any platform claiming to produce a compliant footprint from a product name alone.

The practical sequence

Do not try to fill every field at once. A workable order is: identity first, because everything else attaches to it; then composition and origin, because those are the fields buyers ask for today; then chemicals and care, which mostly already exist somewhere; then circularity; then footprint.

Two structural warnings. First, the data you need for the first three sections lives with your suppliers, not with you — so your real project is a supplier communication project with a software component, not the reverse. Second, whatever you build should survive the delegated act changing shape, because it will. Category-agnostic data models age better than textile-specific ones.

Worked example: one polo shirt, field by field

A representative scenario, since the field list reads differently once it is attached to a real order. A cotton polo shirt, 1,000 units, made in Denizli for a German buyer, to be sold once the textile act applies.

Identity resolves in an afternoon: the GTIN is already in the ERP. The facility identifier is not — the factory has never needed one, and obtaining it takes a fortnight of nobody's attention. Composition takes the longest week of the project: the label says "100% cotton", the tech pack says "100% combed cotton", and the supplier's declaration uses a trade name for the yarn. All three describe the same shirt; only one of them matches the official designation in 1007/2011, and that is the one the passport can carry. Origin needs three separate answers — knitted in one facility, dyed at a subcontractor, cut and sewn in-house — and only the third is in any system. Chemicals exist: the azo dye test report is in the shared drive, but it is filed by date rather than by batch, so matching it to this order means opening four PDFs. Care is a copy exercise, ten minutes. Circularity does not exist and has to be written from the bill of materials: main fabric, ribbed collar, sewing thread, one woven label. Footprint is deferred, explicitly, with a note in the record saying so.

The counterfactual is the useful half. Suppose the composition question had been answered by copying the label rather than reconciling the three versions. The passport goes live saying "100% cotton" while the supplier's own declaration says something else, and the discrepancy surfaces the first time a buyer's auditor compares the passport against the material declaration — not as a data problem but as a credibility problem, in the middle of a contract renewal.

Edge cases: where the field list gets awkward

The clean cases are in the table above. These are the ones that generate the questions:

Multi-component articles. A jacket with a shell, a lining, a zip and a drawcord is not one composition — it is four, and the recycler needs them separately. Work out early whether your data model can hold components, because retrofitting that is expensive.

One style, two factories. If the same SKU is produced in two plants, the facility identifier differs while the GTIN does not. Either your record can carry production-batch detail underneath the product, or you need distinct identifiers — deciding this after the labels are printed is the expensive path.

Subcontracted work. A batch sewn at a subcontractor and recorded under your own facility identifier breaks the traceability chain at the first audit. The rule is simple: the identifier records where the work happened, not who sold the order.

Recycled content without a paper trail. If the recycled-fibre share is real but the supplier cannot document it, the honest passport entry is the undocumented share, not the claimed one. The alternative is a greenwashing exposure printed on a QR code.

Deadstock and small runs. Sampling, deadstock fabric and short runs often have no material declaration at all. They are also where "we will fill it in later" quietly becomes policy — decide the rule before the delegated act does it for you.

What your buyers will ask before the law does

European brands are already sending DPP-readiness questionnaires to suppliers. They typically ask three things: can you provide structured composition and origin data per SKU, can you carry a GS1 Digital Link QR on the product, and can you keep that data updated for years after shipment.

A supplier who can answer yes to all three has a commercial advantage that arrives well before the regulatory deadline does. Our textile supplier checklist turns the same ground into eight audit questions you can run against your own systems this month.

Zoom out: why textiles are the test case

Textiles were not picked first by accident, and the choice says something about how the rest of the decade will go. The category has the longest supply chains, the weakest data infrastructure and the loudest consumer-facing sustainability claims — which makes it the hardest place to make a passport work, and therefore the place where the architecture gets proved.

Two things follow. First, whatever the textile act settles on will be read as precedent by furniture, footwear and the categories behind them; the field groups above are unlikely to change shape, only depth. Second, the technical foundation is largely in place while the legal one is not: EN 18216 and EN 18219–18223 are published, the EU's central registry was launched on (though no passport can be registered successfully yet), and batteries become the live rehearsal on . The gap between "the plumbing works" and "the law names your category" is exactly the window in which supplier data gets collected — or does not. Our ESPR guide covers the framework this sits inside.

Frequently asked questions

Is the textile passport field list final?
No. The delegated act that fixes the exact requirements for textiles is expected in the second half of 2027, with a transition period after it. What is on this page is the direction the ESPR framework and the first implementations already make clear — enough to prepare against, not a legal checklist.
Which fields should a supplier prepare first?
Identity, then composition and origin. Everything in a passport attaches to the product identifier, and composition and origin are the two fields European buyers are already asking for in 2026. Chemicals and care mostly exist somewhere already; circularity and footprint usually have to be created.
Does fibre composition data already exist in most textile businesses?
Usually in three slightly different versions — on the label, in the tech pack, and in the supplier's own system. The passport forces you to pick one and stand behind it, which is why composition reconciliation is the most common first week of a DPP project.
What counts as evidence for a recycled content claim?
A supplier document or certificate tied to the specific material and, ideally, the batch. In the passport era an unevidenced claim is a greenwashing exposure rather than a marketing line, and buyer questionnaires already ask which share of recycled-content claims is documented.
Do we need an LCA before the delegated act lands?
Not to start. The methodology question — full PEF study, simplified footprint, or supplier-declared values — is not settled, so budget the footprint as a separate workstream and be sceptical of any platform promising a compliant number from a product name alone.
How granular does origin have to be?
Country of origin at minimum, with clear pressure toward stage-level detail: where the fabric was woven or knitted, dyed and finished, cut and sewn. The direction is toward more granularity, not less, which is why origin is the field that usually needs a supplier data-collection workflow rather than a database query.

Sources

  1. Regulation (EU) 2024/1781 (ESPR) — EUR-Lex — 2026-08-15
  2. Regulation (EU) No 1007/2011 — textile fibre names and labelling — 2026-08-15
  3. European Commission — Digital Product Passport — 2026-08-08
  4. Commission Implementing Decision (EU) 2026/1736 — harmonised standards for the digital product passport — EUR-Lex — 2026-10-07
Digital Product Passport platform

Built on GS1 Digital Link and EN 18216, 18219–18223, from offices in the Netherlands, Türkiye and Azerbaijan.

Last updated:
  • — Corrected: the harmonised standards are EN 18216 and EN 18219–18223; no passport can be registered in the central registry yet; the standards source is now the decision on EUR-Lex.
  • — Expanded to the content standard: field map table, worked example, edge cases, the standards layer, FAQ and primary sources.

You're in time

6 months free

Worth up to€1,4946 × €249

First 6 months€0

Reserved for the first 1,000 companies

Create your account, choose Starter or Growth, and pay €0 for six months. No credit card required.