The DPP Registry Is Live. Textile Compliance Is Not Final Yet

On 20 July 2026, the European Commission launched the Digital Product Passport Registry with a testing environment. Economic operators can use a secure interface or an API. The Registry stores unique product identifiers and associated metadata while the product information itself remains decentralised.

The Commission’s sector guidance is explicit that the Ecodesign for Sustainable Products Regulation does not impose one general DPP obligation across all products. Requirements arrive product by product through delegated acts or separate legislation.

For textile apparel, the indicative Commission timeline points to adoption of the textile delegated act in the fourth quarter of 2027. The timeline may change, and the final data fields and compliance date will be set by that future act.

Even before the textile act is final, businesses can test the horizontal mechanics that are unlikely to disappear: stable identifiers, a product-to-passport link, role-based access, version control and the ability to keep data available when suppliers or service providers change.

The test should also include failure states. What happens when a batch is split, a supplier corrects a composition record or a QR code points to an unavailable service? A pilot that tests only the perfect path is a demonstration, not readiness.

Textile passport preparation depends on information that often begins outside the brand’s own systems: fibre composition, material origin, manufacturing events and evidence held by transformation partners. Waiting for the final delegated act does not fix fragmented ownership.

A useful pilot chooses one real product family and maps which party can substantiate each field. Where evidence is missing, the gap is recorded instead of filled with an estimate.

REZET Hub can structure provenance, custody, transformation and supporting records at batch level, then expose the verified information needed by downstream systems. The Registry remains the EU infrastructure; REZET Hub serves as a proof-and-data layer beneath product claims and circular programmes.

This separation matters. A passport can point to information, but the business still needs to prove how that information was produced and updated.

Select one product family, one identifier method and a defined set of evidence fields. Register test metadata, exercise the interface or API, document access roles and run at least one correction through the full chain. Finish with a gap register that separates current evidence, supplier-dependent evidence and fields awaiting legal definition.