
The European Commission has launched the Digital Product Passport (DPP) registry. For fashion brands, the framework for textile passports is already largely in place: the implementing regulation has been adopted, technical standards have been published, and initial recommendations on textile content have been issued.
To learn more: Textile DPP: Everything Fashion Brands Need to Know About the Content of the Future Digital Passport
In this article, we break down the architecture of the future DPP in four parts: how it works overall, what has already been decided, what still needs to be decided regarding the textile sector, and what this means in practical terms for a brand’s information system.
The DPP is not a large European database where every brand would submit all of its product information. The system is based on a decentralized model, organized into four components:
Managed by the Commission, the registry stores the products' unique identifiers, their customs codes, and some registration data. It does not contain the complete passport.
Its purpose is to verify that a passport exists and complies with the required format. For imported products, this verification may be conducted at customs. Products manufactured in the European Union must also be registered before they are placed on the market.
Detailed data continues to be hosted by the economic operator itself or by a DPP Service Provider —a provider specializing in the creation and hosting of passports. The registry maintains a list of verified providers and monitors the link to the DPP they host.
Each product is equipped with a data carrier (QR code, NFC chip, or RFID tag) that links to its digital passport. The ESPR Regulation sets out functional requirements without specifying a particular technology at this time. The delegated act on textiles will specify the permitted data carrier(s).
The Commission will finally launch an ESPR web portal. It will provide access to public information and to restricted fields based on each user’s role: consumers, repairers, recyclers, or regulatory authorities—each group will see different data.
Key point: The registry indicates that a passport exists and where it can be found. The brand—or its service provider—is responsible for its content.

Implementing Regulation (EU) 2026/1778, published in the Official Journal on July 17, 2026, establishes the rules governing the registry’s operation. It entered into force on August 6, 2026, and will apply to the textile sector once its delegated act is adopted. For trademarks, the draft is already structured around seven key points:
Key point: The automated check verifies form, not substance. The regulation specifies that the accuracy of the data is still verified by market surveillance authorities, and that a successful registration does not constitute proof of compliance.
The registry is based on a semantic repository: a library of data models and definitions that all passports must comply with. For each product group, the Commission will publish the expected structure, formats, and multilingual labels in this repository.
This standard will be available free of charge via public APIs. As a direct result, proprietary formats will become difficult to justify.
Implementing Decision (EU) 2026/1736 of July 14, 2026, cited six harmonized standards developed by CEN-CENELEC. They cover unique identifiers, data carriers, exchange protocols, storage and archiving, APIs, and interoperability. A solution that complies with these standards is presumed to be in compliance.
The last two standards, on access rights management and data authentication, were scheduled for September 2026.
The scope of the future DPP is now known. The specific provisions, however, will depend on the delegated act expected in 2027. The report published in May 2026 by the Commission’s JRC does, however, provide guidance on three key areas:
Granularity refers to the level at which the passport is created: by model, by production lot, or by individual item. The finer the granularity, the more expensive and time-consuming the data collection and labeling processes become. The JRC proposes:
With regard to the environmental footprint, this information would initially be required at the model level, with the option to use default values. The registry regulation adds a requirement: a passport created for an item must be linked to its lot and model identifiers, when available.
The JRC proposes dividing the data into three categories:
The key issue with this level of access is confidentiality. Indeed, the report emphasizes that supplier data—such as fingerprint calculation parameters—can reveal commercially sensitive information.
The registry already maintains a list of verified service providers. However, the rules governing their activities will be set forth in a dedicated delegated act, which the Commission has announced will be issued in 2027.
The Commission's tentative timeline: adoption of the delegated act on textiles by the end of 2027, followed by a transition period of at least 18 months. For the fashion industry, the requirement will therefore take effect starting in 2029.
These architectural choices have very tangible implications for a fashion brand’s tools. Here are four key points for brands to keep in mind as they prepare for these changes:
Most brands manage their product data at the model level in their PLM systems. Batch information, on the other hand, is typically stored in the ERP system (the software that manages orders and inventory), in communications with suppliers, or in scattered files.
The DPP will require linking the two: a batch identifier, associated with a model, that contains data from both levels. The JRC notes that the batch level is already common in the industry’s internal practices, whereas the item level remains rare.
Each field must comply with the structure, format, and value lists specified in the semantic reference framework. An address entered as free-form text or a country of origin that is incorrectly coded will not pass the automated validation. Data quality is now a prerequisite for market access.
Who collects, who validates, who records, who corrects? Each update creates a new, time-stamped, and traceable version, and the brand remains responsible even when it delegates.
For the CSR, Product, Procurement, and IT departments, this translates into clear approval processes and formalized supplier commitments. The DPP is first and foremost a supplier data initiative—much more than just a QR code on a label.
Access to the registry requires identity verification, which must be renewed at least every three years. For a company, this means obtaining a qualified electronic seal from a trusted service provider. The process is straightforward, but it involves both the legal and IT departments; it’s best to address this early on.
Best practice: Start mapping out right away where each piece of expected data is located (PLM, ERP, PIM—that is, the product information management tool—or supplier files) and at what level it exists: model, lot, or item. This simple inventory reveals most of the gaps that need to be addressed.
Waiting for the delegated act to be issued before getting started would leave little leeway. With about one year of development per collection, a brand that wants to be ready by 2029 must begin working on its data as early as 2027. We recommend moving forward on three initiatives simultaneously.