Digital Product Passport for Non-EU Manufacturers

If you manufacture in Türkiye, Bangladesh, Vietnam or anywhere outside the EU and your products end up on the EU market, the Digital Product Passport will reach you through your customers — even if the regulation puts no passport duty on you — unless you sell under your own name, in which case you are the manufacturer (Art. 2(42)). This guide explains the legal chain, the contract clauses already appearing in purchase agreements, what a real buyer questionnaire asks, and the preparation that keeps your export orders safe.

Who legally owns the obligation — and who does the work

Under the Ecodesign for Sustainable Products Regulation (Regulation (EU) 2024/1781), the manufacturer — whoever markets the product under its own name — must ensure a valid digital product passport exists (Art. 27(1)(c)), and an importer must check that one is available before placing the product on the market (Art. 29(2)(c)). For imported goods that is typically the brand and the EU importer.

Here is the practical asymmetry: the brand and the importer hold the liability, but the fibre composition, the factory identification, the test reports and the process data live in your systems. Liability flows down the contract; data flows up. The result is already visible in 2026 — supplier questionnaires, data clauses in purchase agreements, and audits that include "DPP readiness" as a line item.

Three routes into the EU market — and where you sit

Route 1: you sell to an EU importer or brand. The most common setup for contract manufacturers. The importer is the operator; your exposure is contractual. Expect data delivery obligations, evidence requirements and audit rights in the next contract renewal, if they are not there already.

Route 2: you sell under your own brand via an EU subsidiary or distributor. Your EU entity or the distributor placing goods on the market carries the operator role — which means your own group carries it. The digital product passport moves from "customer request" to "our direct obligation".

Route 3: you sell direct without an EU establishment. This is where the authorised representative enters: an EU-established party you can mandate in writing for specified tasks (Art. 28) — but not the passport, which stays with you as manufacturer (Art. 28(1)). Fulfilment and e-commerce routes do not make the obligation disappear — they determine who answers for it. If no one in the chain can, the products should not be crossing the border.

Identify your route first; every preparation decision — who registers passports, whose system hosts data, who talks to customs — follows from it.

The customs connection

The digital product passport is not enforced only on shelves — it will be checked at the border too. ESPR provides for customs verification: declarants provide the passport's unique registration identifier, and customs can confirm it exists in the EU's central registry, launched on 20 July 2026, once that registry is connected to EU customs systems (by 6 August 2030 at the latest). A shipment whose passport data is missing or unregistered becomes the importer's emergency — and the importer's emergency becomes the supplier's cancelled reorder. We cover the border flow step by step in DPP at EU customs.

What your buyers will ask for on the digital product passport

Exact fields arrive with each category's delegated act, but the pattern across ESPR's framework is stable:

What the questionnaire actually looks like

The supplier questionnaires circulating in 2026 follow a recognisable script. They ask whether every SKU has a unique GTIN; whether you can export composition data in a structured file rather than a PDF; which facility produced which order; whether certificates can be matched to specific batches; whether recycled-content claims carry supplier evidence; and — increasingly — which DPP software or format you can deliver data in. Two meta-signals matter as much as the answers: completeness (blank cells read as risk) and speed (a 48-hour turnaround tells the buyer your data is systematised; a three-week turnaround tells them it lives in email archives).

Contract clauses to expect — and to negotiate

Digital product passport language entering purchase agreements clusters around four clauses: data delivery (defined fields, structured format, deadlines per order); evidence obligations (certificates and test reports matched to batches, retention periods); audit rights (buyer or third party may verify data at the source); and liability allocation (who bears the cost if a shipment is blocked for passport deficiencies). Read the last one twice. A reasonable position to negotiate: you warrant the accuracy and timeliness of the data you provide; you do not underwrite the buyer's own registration and filing duties. Put the boundary in writing before the first blocked container makes it a dispute.

How to prepare for the digital product passport: four moves that pay off regardless of the final rules

1. Fix identification first. Each product needs a persistent unique product identifier that meets ISO/IEC 15459 (EN 18219) at the level your delegated act sets; for products sold through retail the practical route is a GTIN licensed from a GS1 member organisation. Your company and sites need consistent identifiers. This is cheap now and painful later.
2. Centralise product data. One structured source per product — composition, care, certificates — instead of data scattered across order emails and PDF archives.
3. Choose a carrier strategy. A GS1 Digital Link QR lets one code serve retail scanning and passport access; see why the URL syntax matters.
4. Answer buyer questionnaires fast. Speed of response is itself the signal buyers use to sort future-proof suppliers from risky ones.

Walkthrough: the questionnaire lands on a Tuesday

A representative scenario. A 90-person garment manufacturer near İzmir receives a supplier data questionnaire from its largest German buyer: 34 questions, a structured spreadsheet template, a four-week deadline, and a closing line noting that responses "inform 2027 sourcing decisions."

Week 1 — triage: the export manager maps questions to owners: GTIN list (ERP), compositions (production), certificates (quality), facility data (management). Gaps surface immediately — two certificate families can't be matched to batches, and 14 SKUs share GTINs across colourways. Week 2 — fixes: GTIN duplicates are corrected in the ERP (painful but contained at 14); the certificate-matching gap is honestly marked "in progress, resolved by Q1." Week 3 — structure: answers move from email drafts into the buyer's template; composition data exports cleanly because it was already field-based, not free text. Week 4 — delivery: the response ships two days early, complete except the flagged item, with a one-line note: "sample product passport page available on request."

The counterfactual writes itself: the same questionnaire sitting in a sales inbox for three weeks, answered in prose, with "composition data attached as PDF scans" — read by the buyer as exactly what it is, a preview of every future data request. Two suppliers, same factory quality, different 2027 order books.

The authorised representative decision

If you sell into the EU without an EU establishment, choosing the authorised representative arrangement is a real decision, not a formality. Two configurations dominate: a specialised AR service (independent of any single buyer, adds an annual fee, keeps your options open) or your own EU entity (heaviest, makes sense once EU volume justifies a subsidiary anyway). Your importer is not an AR set-up: it has its own duties under Art. 29. The trap to avoid: assuming someone downstream "probably handles it." Two things are fixed by law, not by contract: the passport duty stays with the manufacturer (Art. 28(1)), and the operator placing the product on the market uploads the registry data (Art. 13(4)). A verified third party may perform registration actions on its behalf, but that operator remains fully responsible (IR 2026/1778 Art. 19(4)). Who does the practical work around them still needs to be agreed in writing — an unowned task is a blocked shipment scheduled in advance.

Notes by manufacturing hub

The pressure arrives everywhere, but not identically. Türkiye: proximity and speed-to-market are the sales argument; DPP readiness compounds it — a supplier two trucking days from the buyer and passport-ready is a strong 2027 pitch. Local competition is already forming, so readiness is also defensive. South and Southeast Asia: longer chains and larger order books mean buyers consolidate harder around data-capable suppliers; the questionnaire wave started with the biggest brands and is moving down the buyer pyramid. Everywhere: the pattern repeats — the first supplier in a region to show a live passport resets the buyer's baseline for everyone else in that region.

The upside case

Everything above frames the digital product passport as risk management; the stronger frame is commercial. EU buyers are consolidating volume with fewer, safer suppliers ahead of category deadlines — and "passport-ready" is entering shortlists alongside price, quality and lead time. The factory that shows a live passport for a sample product in the first meeting is not answering a compliance question; it is making a sales argument no brochure can match. The cost of getting there is modest, while the cost of unpreparedness is measured in lost reorders.

Further reading: Digital Product Passport for textiles · GS1 Sunrise 2027

Related articles

Digital Product Passports at EU Customs: How Checks WorkESPR ties the digital product passport to import controls: declarants will give the registration identifier, customs will check it against the EU registry.Textile DPP Checklist for Exporting SuppliersA Digital Product Passport checklist for textile suppliers and buyers: which data, which standards, in which order. Be ready before the delegated act lands.