How a DPP Reaches the EU Central Registry

ESPR places the duty on the “responsible economic operator” placing the product on the EU market — normally the EU brand or importer, not the export factory. But the data originates in your factory, and an operator can authorise a DPP service provider (Article 2(32)) to store and process its passports (Articles 10(4) and 11(c)); the registry upload stays the operator’s duty (Article 13(4)). In practice three models exist: brand-managed, factory-managed via a service provider, and hybrid. Factories that prepare the data and the passport factory-side remove work from the buyer — a real sourcing advantage.

The Registry stores at least the unique identifiers, not the passport itself (plus the commodity code for imports); delegated acts may add other data (ESPR Article 13(1)–(2)). The full data record — fibre %, carbon footprint (kgCO₂eq), substances of concern, care and end-of-life instructions — remains with the DPP host, accessible for at least the product's expected lifetime.

19–20 July 2026 — Article 13 set-up deadline (19 July); the Registry launched on 20 July. This is infrastructure for the Commission, not an immediate duty for factories. 2027 (expected) — Textile Delegated Act finalises data fields. 2028–2029 — expected enforcement for garments: no valid Registry entry, no EU market access. Buyers, however, are already writing DPP-readiness into 2026–2027 sourcing terms.

At import, customs check the product’s unique registration identifier and commodity code against the Registry — automatically once the registry–customs link is running (Article 15(3)). A match confirms a valid, registered passport; a miss can mean the shipment is held or refused, because ESPR Article 15 makes the registration identifier a customs checkpoint (penalties are set by Member States under Article 74). In-market, surveillance authorities spot-scan care-label QR codes. The Registry check is systematic; physical scans are random.