The Registry is live, but textile rules are not final
On 20 July 2026, the European Commission launched the Digital Product Passport Registry and a testing environment. This is an operational milestone for the wider Digital Product Passport system. The Registry is designed to hold unique product identifiers and required registration metadata, while the fuller product information remains stored by the responsible economic operator or a service provider. It does not mean that every garment sold in the European Union suddenly needs a passport today.
Textile apparel is a priority product group under the Ecodesign for Sustainable Products Regulation, or ESPR. The Commission currently plans to adopt the textile-specific delegated act in the second half of 2027, with its textile page indicating Q4 2027. That future act is expected to define the exact data fields, scope, granularity, access rights, and related ecodesign requirements. The published timeline is expressly indicative and may change as legislative and technical work continues.
The Commission also states that economic operators will receive a transition period of at least 18 months after a relevant ESPR delegated act is adopted. For a small brand, the sensible response is therefore neither to ignore the subject nor to behave as if the final textile specification already exists. The practical task for 2026 is to improve the quality and structure of product records that are likely to support future compliance, while keeping software and labelling decisions reversible.
What a textile Digital Product Passport is—and is not
A Digital Product Passport is a structured digital identity for a product, component, or material. Under the EU framework, a physical data carrier such as a QR code can connect the product to information that different users access according to their roles. Consumers, repairers, recyclers, customs authorities, and market-surveillance bodies may not all see the same information. The system is intended to make product data more accessible, interoperable, and useful across a product's lifecycle.
For textiles, the Commission lists possible information areas such as product identification, fibre composition, origin, responsible economic operators, and information relevant to use, repair, resale, disassembly, recycling, or disposal. These are useful preparation signals, not a final checklist. The Commission is explicit that the exact textile requirements will be determined by the delegated act and supporting technical specifications.
A passport is also not a sustainability certification. A QR code does not prove that a fibre is lower impact, that a supplier is certified, or that a product meets an environmental claim. The DPP is an information and compliance infrastructure. The quality of any claim will still depend on the evidence behind the data, the scope of that evidence, and whether the information stays accurate when materials, suppliers, or production batches change.
Map who may hold the obligation before choosing a system
The Commission's textile guidance says the primary obligation is expected to sit with economic operators that place textile apparel products on the EU market or put them into service there. Depending on the commercial setup, that operator may be a manufacturer, producer, or importer. Distributors and dealers are expected to ensure that a required DPP is available for the products they handle, while some suppliers or service providers may need to provide information available to them.
This makes role mapping an early business decision, especially for a small brand selling across borders. A brand should document which legal entity owns the product specification, which entity imports into the EU, who controls product identifiers, and which partner retains the supporting records. The answer may differ between direct-to-consumer sales, wholesale, marketplace sales, and arrangements where an EU distributor acts as importer.
Do not assume that a factory, fabric mill, sourcing agent, marketplace, or software provider will carry the whole obligation. Supply-chain partners may provide essential evidence, but the operator placing the product on the market needs a reliable way to obtain, validate, and maintain that evidence. Clarifying ownership of each data field is more valuable now than buying a platform with an attractive demo but unclear responsibilities.
Build a minimum product evidence file now
Start with information that already supports product development and truthful communication. Give each style and colorway a stable internal identifier. Keep the approved bill of materials, fibre composition, trim details, care instructions, supplier references, and the version of the specification used for production. Where records exist, link them to purchase orders, sample approvals, test reports, transaction documents, or certificates without implying that every document will become a mandatory DPP field.
Next, decide the smallest level at which your records remain dependable. Some evidence is model-level, such as a base construction. Other evidence changes by color, supplier, production order, or batch. A composition certificate from one supplier should not silently follow a style after the fabric source changes. Even before the EU confirms whether a textile passport must operate at model, batch, or item level, a brand can preserve the relationships between product version, material source, and production run.
Use a simple evidence register with four questions for every important field: who supplied the information, what document supports it, what product or batch does it cover, and when must it be reviewed? Mark unknowns openly. A missing origin field is a data gap to resolve; an inferred origin presented as fact is a traceability risk. This discipline also helps brands assess existing sustainability statements without treating a material name or certificate logo as a complete supply-chain claim.
Keep technology and claims flexible until the delegated act arrives
The Registry launch makes the architecture more concrete. It supports registration through a user interface or an application programming interface, and the wider DPP system is being built around identifiers, data carriers, interoperability, data exchange, and storage standards. Six harmonised DPP standards were announced as available when the Registry launched, with additional standardisation work continuing. This is useful infrastructure progress, but it does not finalize the textile data model.
A small brand can therefore test how it creates stable product identifiers, exports structured records, and updates information without committing to a permanent vendor or printing a new QR code on every garment. Ask any prospective provider how data can be exported, how changes are versioned, what happens if the provider closes, and which functions are based on published requirements rather than forecasts. Avoid contracts that turn an uncertain compliance timeline into an urgent technology purchase.
Marketing language needs the same restraint. It is reasonable to say that a brand is improving product data or preparing traceability records. It is premature to claim that a garment is compliant with final textile DPP requirements before those requirements exist. Keep internal readiness work separate from public environmental claims, and review any statement against the evidence attached to the exact product, supplier, and production period.
Use a six-step readiness sequence
First, name one owner for DPP readiness, even if the role is part-time. Second, map the commercial entities and routes through which products reach the EU market. Third, create a product-data dictionary that lists each field, its source, format, owner, evidence, and update trigger. Fourth, test the dictionary on one representative style with multiple materials or suppliers so weaknesses appear before the system is scaled.
Fifth, send a focused information request to key material and production partners. Ask what composition, origin, batch, care, repair, chemical, certification, and end-of-life records they can provide today, in which format, and at what level of specificity. Do not ask partners to guarantee future compliance with an unfinished textile rule. The goal is to learn which data already travels reliably and which fields require new contractual or coordination steps.
Sixth, review the file when the textile delegated act and technical specifications are published. Compare the final scope with the data dictionary, close verified gaps, then select the registration, hosting, and data-carrier workflow that fits the obligation. This sequence turns DPP readiness into normal product governance: clear identifiers, controlled versions, documented evidence, and assigned responsibilities. Those foundations are useful even if the final timeline or field list changes.