prodpas.eu

How do I document the supply of passport data in my purchase contract?

What you record: supply obligation for passport data

A purchase contract can specify that the supplier provides the data needed to compile the digital product passport, and that this supply is a condition for product acceptance. In practical terms: which data the supplier provides, in what form, before which point in the procurement process, and what happens if data is missing or changes later. The ESPR already places the obligation to provide information on actors in the supply chain, but the precise procedure — how, when, in what format — is something the parties agree on in their contract themselves.

Who this applies to, and what does not

This agreement is relevant for anyone purchasing components, materials or complete products that fall under a product group for which a digital product passport will apply. This applies to manufacturers purchasing from supply chain actors, and to importers sourcing products from outside the EU. It does not apply to the purchase of products or components that fall outside the designated product groups — there is currently no passport obligation for these, and therefore no basis for contractually enforcing data supply under the ESPR. The distinction between the role of manufacturer and the role of importer is also relevant: Article 29 of the ESPR (Regulation (EU) 2024/1781) describes specifically what is expected of importers, while Article 38 more broadly covers actors in the supply chain in general.

From when this becomes relevant

There is no fixed date by which this contractual clause must be in place everywhere — this depends on when a delegated act designates a specific product group and the associated timelines for that group. This is determined separately for each product group in separate regulations that have yet to be issued or are not yet included in these sources. What is certain: as soon as a product falls under a designated product group, the obligation arises for actors in the supply chain to provide relevant information under Article 38. It is therefore practical to include the contract clause before the obligation for a specific product group takes effect, so that the provision of data is regulated as soon as it is needed, rather than having to negotiate under time pressure.

How you implement this in the contract

The sequence in which this is usually tackled begins by determining which data is needed for the passport of the specific product — think of material composition, origin, repair data or other information relevant to that product group. Next, the contract specifies which party provides which part of that data: for a composite product, no single party provides everything, but multiple links in the chain contribute pieces of information. Then comes the question of the timing of delivery: preferably before or at the same time as the delivery of the physical product, so that the passport can be compiled in time. An agreement on format is also useful, so that the supplied data can be processed without further editing. The next step is to set out an update obligation: what happens if the composition of a component changes, or if a supplier itself needs to correct data after the passport has already been compiled. Finally, it is common to regulate liability in case data proves to be incorrect or incomplete, and to include an inspection right so that the purchasing party can verify the supplied data before it enters the passport. For importers, it is additionally relevant to specify in the contract with the manufacturer that the manufacturer has fulfilled its own passport obligations, as the importer bears responsibility for this.

The legal basis: Article 38 and 29 ESPR

Article 38 of the ESPR (Regulation (EU) 2024/1781) describes the requirements for actors in the supply chain, including the provision of information needed to compile the digital product passport. This article forms the basis on which a purchasing party can and may request data supply from suppliers: the obligation to cooperate lies not only with the manufacturer or importer, but extends across the entire chain. Article 29 of the same regulation specifically describes the obligations of importers, including ensuring that the product is accompanied by a correct passport and that the manufacturer has fulfilled its own obligations. Together, these articles form the foundation on which a contractual agreement on data supply can be built — the law requires cooperation, the contract regulates how that cooperation works in practice.

If you are now drawing up or revising a purchase contract, you can include a provision on data supply for the product passport at the next opportunity, even if your own product group has not yet been designated — this way the agreement is already in place and there will be no need to renegotiate later.

Where this is based on

The regulation itself is on EUR-Lex. We provide references for each claim; you do not have to take our word for it.

What you must do concretely

What is expected of you

A product passport is compiled from data that originates somewhere in the chain: from the manufacturer of a component, from a subcontractor, or from an importer who places products from outside the EU on the market. Who ultimately has to draw up the passport depends on their own role, but the data itself often comes from another company. This makes the purchase contract one of the practical places where the supply of passport data is regulated.

Data from suppliers are needed to be able to compile the passport

The ESPR describes in article 38 that actors in the supply chain have a role in making available the information necessary for the product passport. For a company of 10 to 100 employees, this means that its own suppliers — from raw material supplier to component maker — must provide data that will subsequently be included in the passport of the end product. Without that supply, part of the information that the passport must contain is missing. Which data exactly that is varies per product group and per component; which data must I request from my product supplier provides an overview of this.

Importers have their own obligation to check and pass on data

Whoever imports products from outside the EU falls under article 29 of the ESPR. This states that importers must check whether the manufacturer has completed the required conformity procedures and whether the product is accompanied by the necessary information, including the product passport. For an importing company, this means that the purchasing relationship with the manufacturer outside the EU is not only about price and delivery time, but also about whether and how passport data are supplied. More about this role can be found in what does the product passport mean if I import products from outside the European Union.

The purchasing relationship must settle something about the form and timing of delivery

Neither of the articles prescribes a contract form. What does follow from them, however, is that somewhere in the relationship between buyer and supplier something must be agreed upon regarding which data are supplied and that those data are correct. For a company that purchases from multiple suppliers, that is a practical task: not every supplier delivers data in the same way, in the same form or at the same time.

Where things go wrong in practice

A common situation is that the purchase contract does contain agreements on quality, delivery time and price, but nothing about the passport data. The buyer then assumes that the supplier "will sort it out", while the supplier does not see a separate obligation there because the contract says nothing about it.

It also happens that the data are supplied, but too late — only after the product is delivered, whereas the passport must be present at the time of delivery. Without an agreement on the timing of delivery, this creates a delay that lies not with the buyer, but with the supplier, while the buyer is still held accountable for it.

A third situation: the supplier supplies data, but not in a form that can be processed — a PDF with free text instead of structured data that fits into the passport. The result is that the buyer has to manually transfer the data, with a risk of errors. How to check that data can be found in how do I check whether the data from my supplier are correct.

Furthermore, it happens that a company changes supplier without anything being laid down in the contract about the data from the previous supplier that have already been processed in an existing passport. This raises the question of whether and how the passport needs to be adjusted, a subject that is addressed in I am changing supplier, does the product passport need to be adjusted.

Finally, things go wrong when a supplier delivers components that are processed in multiple product groups, and the contract does not make clear which data is needed for which application. This applies for example to my supplier delivers components from different product groups — how do I handle that.

What you can document

In the purchase contract, or in an annex to it, the following can be included:

For companies that still need to determine whether these agreements are already relevant for their products, does the digital product passport apply to my products and when does the product passport become mandatory for products a first orientation, and provides what is a digital product passport for products background on the data that ultimately matters.

This is not legal advice. This page provides general information about the regulations that this platform concerns. We do not know your situation. If you are in doubt about your own case, consult a lawyer or the competent supervisory authority.

Written with AI on the basis of the sources above, checked by a human on 2026-08-22. Is something incorrect? Let us know — corrections are given priority.