Home/Blog

Supplier data collection for textile DPPs, without a portal

How to collect passport data from tier 1 to tier 4 textile suppliers without a login portal: who holds what, request design, chasing and confidentiality.

A denim jacket has a simple label and a long supply chain. The garment is sewn in one factory, the denim is woven in a mill that may dye its own yarn or send it out, the yarn comes from a spinner, the cotton from a gin, and the buttons and rivets from a trims supplier with its own plating line. Each of them holds a piece of the data a textile passport is likely to need, and most of them have never heard of the brand that will publish it.

This article is about getting that data back without asking every supplier to log into another platform. It covers who holds what, why portal-first collection tends to stall, how to design a request that gets answered, how to handle supplier names that are commercially sensitive, and what to check when the data comes back. It ends with a 30-day plan and a request template you can adapt.

Which supplier holds which passport data?

Tier numbering varies between companies. In this article, tier 1 is the garment maker you buy finished goods from, tier 2 the fabric and trims suppliers, tier 3 the spinner, and tier 4 the raw fibre or recycled feedstock source. Wet processing (dyeing, printing, finishing) may sit inside the mill or at a separate dye house.

TierSupplierData they typically holdEvidence they can provide
1Garment makerMaking country and facility, bill of materials, component weights, fabric and trims suppliers used for the orderPurchase orders, packing lists, factory identifier
2Fabric millWeaving or knitting country and facility, fabric composition, fabric weight, finishing routeFabric specification, composition test report, transaction certificates
2Dye house or printerDyeing or printing country and facility, process type, chemicals usedRestricted substances test reports, chemical inventory declarations
2Trims supplierMaterials of buttons, rivets, zips, labels and threads; plating or coatingREACH Article 33 declaration, test reports
3SpinnerYarn composition, blend ratio, spinning countryTransaction certificates for organic or recycled content
4Fibre sourceFibre origin, recycled feedstock sourceCertification upstream of the spinner

Two things follow. First, the countries that French law already asks for (weaving, dyeing and printing, and making, under Décret n° 2022-748 implementing the AGEC law) sit at tiers 1 and 2, so that is where collection should start. Second, organic and recycled content claims depend on a chain of transaction certificates that starts upstream. Under the Textile Exchange Content Claim Standard procedures, the certification body checks incoming transaction certificates and volumes before it issues an outgoing one, so in practice you ask your fabric supplier for the certificate covering your goods rather than tracing the spinner yourself.

The exact fields of the textile passport are not adopted yet. The Joint Research Centre published its proposal on apparel passport content in May 2026 and the Commission plans to adopt the delegated act in 2027. Countries of production, composition by component and certificate references are reasonable fields to start with because they are already required or widely requested.

Why do supplier portals with logins get low response?

A mill that supplies twenty brands may be asked to use twenty portals. Each one needs an account, a password, an onboarding email that may land in spam, and a screen in a language that may not be the user's own. The portal asks for everything at once, organised by the brand's data model, with product codes the supplier does not use. The person who knows the answer, often in the merchandising or quality team, is not the person who received the login.

None of this is a reason never to use a portal. It is a reason not to start with one. The suppliers who answer first are the ones who can reply to a normal business email with a small attachment. Once the data flow works and volumes justify it, a structured upload or an integration can replace the email; see integrations for how data can enter a passport from existing systems.

How should a data request be designed?

A request is a small piece of work you are asking someone else to do for free. Design it so that a busy person can finish it in one sitting.

  • One product. Name a single style and order, using the supplier's own reference where you know it: "Article 4471, your PO 23-118". A request for "all products supplied in 2026" will wait.
  • Few fields. Five to eight fields per supplier is a workable target. Ask the fabric mill only for what the fabric mill knows.
  • Pre-filled. Fill in what you already have from purchase orders, specifications and previous certificates, and ask the supplier to confirm or correct. Correcting a value is faster than creating one.
  • Evidence by name. "The GRS transaction certificate covering the fabric shipped against PO 23-118" is clear. "Any sustainability documents" is not.
  • A deadline and a reason. Give a date about two weeks out and one sentence on why the data is needed.
  • One contact. A named person who answers questions within a day.

Which language and format work best?

Write the request in English and, where you can, in the supplier's working language as well. Keep sentences short and avoid internal terms such as "DPP readiness wave 2". Reply formats that work across most suppliers are a plain-text reply under the email or a one-row spreadsheet with the field names in the first column.

Fix formats in advance, because cleaning is slower than asking clearly:

  • Countries as two-letter ISO 3166 codes or full English names, one per process.
  • Composition as fibre name and percentage, per component, using the generic fibre names of Regulation (EU) No 1007/2011 (for example "polyamide" rather than a trade name).
  • Weights in grams per square metre for fabric and grams for components.
  • Dates as year, month and day.
  • Certificates as standard, certificate number, holder name and date of issue.

Avoid fillable PDF forms: they are hard to read back and often get printed, signed and scanned.

How should chasing and escalation work?

Most non-response is not refusal. The request reached the wrong person, was forwarded and lost, or was put aside behind production work. A schedule handles this better than repeated automated reminders.

  1. Day 0: send the request to a named contact, copying your buyer or sourcing manager.
  2. Day 5: short personal reminder in the same thread, offering a call.
  3. Day 10: phone or messaging call from the person who manages the commercial relationship.
  4. Day 14: escalate through the tier 1 supplier for upstream data, or to the supplier's management for direct suppliers.
  5. After the deadline: record the field as missing, note the reason, and add the data requirement to the next purchase order or supplier agreement.

For tier 2 to tier 4, the tier 1 supplier is usually the right channel. It buys from those suppliers and has the leverage. Where the brand nominates the mill, it can ask directly, but should tell the tier 1 supplier it is doing so.

How should confidential supplier names be handled?

Suppliers, and tier 1 manufacturers in particular, often do not want their own suppliers' names published, because those names are part of their commercial advantage. The answer is to separate what is collected from what is shown to each audience.

ESPR, Regulation (EU) 2024/1781, leaves it to each delegated act to specify which actors have access to which passport data and which actors may create or update it (Article 9(2)(f) and (g)). Its Annex III includes unique facility identifiers among the information a passport may contain, but whether textile facility details will be public is not decided. France's AGEC traceability information asks for countries of the main production steps, not company names. A sensible default:

  • Consumers: countries of weaving or knitting, dyeing or printing, and making.
  • Business customers and recyclers: what they need to act on, such as composition and treatments, with facility details only where agreed.
  • Authorities: facility names, identifiers and evidence documents, available on request or through restricted access.

Tell suppliers this in the request itself. A sentence such as "your company name will not be shown to consumers" removes a common reason for silence. The audience model is covered in our article on access layers.

What should be checked when data comes back?

Run the same checks on every return before anything goes into a passport.

  • Composition totals add up to 100% per component, and the declared composition agrees with the care label. Regulation (EU) No 1007/2011 allows a 3% manufacturing tolerance between declared and analysed composition, so a larger gap against a test report needs an explanation.
  • Countries are given per process, and the making country matches your purchase order and shipping documents.
  • Certificate holder name and site match the supplier who sent it, or the supplier's upstream source where that is the point.
  • Certificate scope fits the claim. A scope certificate shows a company may handle certified goods; the transaction certificate covers specific goods. GOTS requires the seller's scope certificate to be valid on the shipment date.
  • Dates are plausible: certificates current or covering the shipment, test reports recent and tied to the right lot.
  • Substance declarations refer to a dated version of the REACH Candidate List, since Article 33 duties apply to substances on that list above 0.1% weight by weight.

Record what was checked and by whom. How evidence links to individual fields is covered in our article on evidence and certificates.

What does a 30-day collection plan look like?

Start with a pilot of a few products that represent your supply chains, for example a denim jacket with metal trims, a knitted jumper with a blended yarn and a printed T-shirt. Then scale what worked.

DaysActivityOutput
1 to 3Choose pilot products; list the fields you need and what you already hold from purchase orders, specifications and certificatesField list with gaps marked per product
4 to 6Map suppliers per product and tier; name one contact per supplier; agree the channel with tier 1Supplier map and contact list
7Send pre-filled requests: one product, few fields, evidence named, deadline day 21Requests sent and logged
8 to 13Answer questions within a day; first reminders on day 12Question log; first returns
14 to 17Calls from the commercial contact; tier 1 passes requests upstreamEscalation log
18 to 21Check returns as they arrive; send specific follow-ups for gapsChecked data with evidence attached
22 to 26Final escalation; record missing fields and reasonsGap register
27 to 30Review what worked; update template and purchase order clauses; plan the next product batchRevised template and rollout plan

To test whether the data you collected is enough to build a passport, you can turn a CSV into a passport with the pilot products.

Request template

Adapt this to each supplier, keep only the fields that supplier can answer, and pre-fill the values you already have.

Subject: Product information for article 4471 (your PO 23-118), reply by [date]

Dear [name],

We are preparing product information for the EU market, including information already required in France. For one article only, please confirm or correct the values below and attach the documents listed. It should take about 15 minutes. Your company name will not be shown to consumers.

Article: 4471 denim jacket. Your reference: [their code]. Order: PO 23-118.

1. Country of weaving: [pre-filled, e.g. TR]. Correct? Yes / No, it is: ____

2. Country of dyeing: [pre-filled]. Correct? Yes / No, it is: ____

3. Fabric composition: [98% cotton, 2% elastane]. Correct? Yes / No, it is: ____

4. Fabric weight in g/m2: ____

5. Recycled or organic content claimed for this fabric: ____ %, standard: ____

Documents: the transaction certificate covering the fabric shipped for PO 23-118, if a content claim applies; your latest composition test report for this quality.

You can reply under this email or fill in the attached one-row sheet. Questions: [name, phone], we reply within one working day.

Thank you,

[name, role, company]

Where does a passport platform fit?

Collection is a relationship task first and a software task second. What software can do is keep the requests small and the returns tidy.

HyperDPP sends no-login data requests to suppliers, who enter data only in the fields opened to them, and keeps each returned value with its evidence status and the audiences allowed to see it. If you want to see where your supplier data stands today, the readiness check is a short place to start. Regulatory information last checked November 2026.

Frequently asked questions

Who should a brand ask for tier 2 to tier 4 supplier data?

Usually the tier 1 garment maker, who buys the fabric and trims and can pass the request upstream. Direct contact with mills and spinners helps where the brand nominates them or where the tier 1 supplier cannot obtain certificates.

Do suppliers have to agree to have their names shown in a digital product passport?

The textile passport content is not adopted yet, so it is not decided which facility details will be public. ESPR lets the delegated act set which actors can access which data, and the French AGEC traceability rules require countries rather than company names, so names can be kept to business or authority audiences.

What format should a supplier data request use?

A short email with a one-row spreadsheet or a plain-text reply template works for most suppliers. Ask for evidence documents by name, such as the transaction certificate for the specific order, and give units and country formats in advance.

How long does it take to collect passport data for one product?

It depends on the supply chain depth and relationships. A 30-day plan with a pilot product, a first request in week one, reminders in week two and escalation in week three is a realistic structure to test before scaling.

See a live passport for your own product.

In a 30-minute session we take one of your products, build its passport from your own file, and map the missing fields and evidence status together.

Request a demo →