Why DPP Readiness Starts With Your Supply Chain
A Digital Product Passport can only be as reliable as the information that reaches the product record
DPP readiness often depends less on the passport interface than on the information moving between brands, manufacturers and material suppliers.
Take a single garment style. The brand may hold the commercial product record. The manufacturer has the bill of materials and production details. A fabric mill holds technical information about the textile. Another supplier may provide trims. Certificates sit with compliance teams. Facility information may be maintained in a separate supplier database.
None of these records is unusual. The challenge is keeping them connected as they move between organisations and systems.
For that reason, supply-chain readiness is one of the first practical dependencies behind a reliable Digital Product Passport.
The DPP does not create the underlying evidence
The EU Ecodesign for Sustainable Products Regulation establishes the framework for Digital Product Passports. Textile apparel is one of the priority product groups, while the detailed textile-specific DPP requirements are still being developed.
The framework is already clear on an important point: DPP information is expected to be structured, interoperable and connected to persistent product identification. The European Commission also notes that suppliers of products or services may be required to provide relevant information available to them.
For brands, importers and manufacturers preparing for this system, the practical consequence is straightforward.
A DPP cannot correct an uncertain source record.
If a material has two different names across the brand and supplier systems, the passport does not decide which one is right. If a certificate cannot be linked to the material or facility it covers, the product record still lacks usable evidence. If a supplier changes a component and the product record is not updated, outdated information may remain attached to the product.
The quality of the final product record therefore depends on the quality of the information handoffs behind it.
Where supply-chain data starts to break
Most supply chains already exchange large amounts of product information. The challenge is that the information was not always created for the same purpose.
Consider a cotton overshirt.
In a brand PLM system, the main fabric might be recorded as:
Organic cotton twill, 240 gsm
The garment manufacturer may use:
Main fabric - Navy Twill - 240G
The fabric mill may identify the same material internally as:
CT-240-OC / Shade 19
All three records can be correct. They are still difficult to connect automatically unless there is a reliable relationship between them.
The same issue appears with supplier names, factory locations, test reports, transaction documents, certificates and production batches. People can often recognise that two records refer to the same thing. Systems need a more explicit connection.
This is one of the less visible parts of DPP preparation. The work is not simply collecting more files from suppliers. It is making sure that incoming information can be attached to the correct product record without relying on someone to interpret it manually each time.
Supplier readiness is a handoff problem
A useful way to assess DPP readiness is to look at the points where information changes hands.
A supplier sends a material specification to a manufacturer. The manufacturer uses that material in a style. Product information moves to the brand. A compliance team adds supporting evidence. The product may later be updated, reordered or produced in another facility.
At each of these points, the identity of the record needs to remain clear. A material specification should still be traceable to the correct material. A certificate should have a defined scope. A supplier or production change should be reflected in the product record that depends on it.
This becomes especially important when sourcing changes over time. If a material, supplier or facility changes, the organisation needs to know which product information is affected and which evidence needs to be reviewed.
A supplier may have excellent documentation but send it in a way that cannot be linked reliably to products. Another supplier may have sophisticated internal systems but no agreed process for communicating changes. A smaller supplier may work with simple tools but provide consistent information with clear identifiers and scope.
The practical question is therefore not whether a supplier uses a particular software platform. It is whether the information can move between organisations without losing its identity or context.
A certificate is not the same as product evidence
This distinction matters especially when companies begin mapping existing sustainability and compliance documents.
A certificate may confirm that an organisation, site, process or material meets a particular standard. Its existence does not automatically prove that it applies to every product associated with that supplier.
Before using a document as part of a product record, the relationship needs to be understood.
Which legal entity is named on the document?
Which facility does it cover?
What is the scope?
What products or materials can it support?
When was it issued and when does it expire?
Is there another document or transaction record needed to connect it to the specific product?
These are ordinary evidence-management questions, but they become important when information is expected to travel with a product in a structured form.
DPP preparation can therefore expose a gap that spreadsheets often hide: companies may have the document, but not the structured relationship between the document and the thing it is supposed to support.
Product identifiers need to survive supplier changes
Another supply-chain issue appears when sourcing changes.
A material in a product specification may initially come from Supplier A. Six months later, the purchasing team approves Supplier B for the same specification. From a commercial point of view, the product may still be sold under the same style.
From a data point of view, something has changed.
The source, supporting documents, facility information or material characteristics may now be different. Whether that change requires a different DPP record will depend on the applicable product-specific rules and the level at which the passport is defined.
Companies do not need to predict those rules today to improve the process.
They do need to know when a relevant sourcing change happens and which product records are affected.
That requires a connection between product identifiers and supplier records that survives beyond the initial onboarding exercise. A one-time data collection project will quickly become outdated if procurement changes are not reflected in the same information flow.
Do not ask suppliers for everything
A common reaction to uncertainty is to create a very large supplier questionnaire.
That can produce more data without producing more clarity.
For DPP preparation, the better starting point is to define a small set of information that has a clear relationship to the product and a clear owner.
For one material, for example, a company might first test whether it can consistently identify:
- the internal material reference;
- the supplier's material reference;
- the supplier and relevant facility;
- the material description and composition already used in current processes;
- the available supporting evidence;
- the date or version of the information;
- the products in which that material is used.
The purpose of the exercise is not to guess the final textile DPP dataset. The detailed requirements will be defined through the relevant EU rules.
The purpose is to test whether supplier information can move into a product record without losing its identity, context or ownership.
Test the process where sourcing actually changes
A useful readiness check is not to choose the simplest product in the range. It is to choose a style where something changed during the season.
For example, select a product where the fabric supplier changed, a second production facility was introduced, or an alternative trim supplier was approved.
Then check whether the current records make that change visible.
Can the team see which version of the material specification is now active?
Can the supporting evidence be connected to the new supplier or facility?
Can the organisation identify which styles were affected by the change?
Can the previous and current records be distinguished without relying on email history or individual knowledge?
This type of test reveals whether the information model can survive a real sourcing event.
A product record that works only while the supply chain remains unchanged is not yet a reliable product record.
The supplier conversation needs to change
Brands often approach supplier data as a request-response process.
A question is sent. The supplier finds the document. The brand stores the answer. The process starts again when another team or customer needs similar information.
DPP preparation is an opportunity to make that exchange more systematic.
Instead of repeatedly asking for isolated files, companies can define how important product information should be identified, delivered, checked and updated.
This does not require every supplier to use the same software.
It requires agreement on the information being exchanged and enough structure to preserve its meaning between systems.
For suppliers, that creates a clearer expectation. They can see which data is required, which evidence supports it and when an update needs to be communicated. For brands, it reduces the amount of interpretation required after the information arrives.
Supply-chain readiness comes before passport design
The Digital Product Passport has a visible layer: a data carrier, a product identifier and information made available to the appropriate users.
Behind that layer is a network of records created by different organisations.
For textile products, some of the most important preparation work will happen in that network long before the final DPP is published.
Companies can start by understanding where product information originates, how suppliers identify it, how evidence is connected, and what happens when sourcing changes.
At DeviceStamp, we see this as a practical supply-chain integration problem. The objective is to preserve the relationship between products, materials, suppliers and evidence as information moves between organisations, so that the product record can be maintained instead of reconstructed whenever it is needed.
The practical starting point is therefore not the passport itself. It is whether product, material and supplier information can remain connected as it moves through the supply chain.
Regulatory context
Textile apparel is included among the priority product groups under the EU Ecodesign for Sustainable Products Regulation (ESPR) Working Plan 2025-2030. Textile-specific DPP requirements will be defined through the relevant delegated act and supporting technical specifications.
Official EU information: