prodpas.eu

Which data must I request from my supplier of products?

Information on materials, origin and compliance

From a supplier, you request the information needed to complete the digital product passport of a product: data on the materials and substances processed in the product or component, the origin of components, declarations of conformity and test reports, and, depending on the product group, information on repair, disassembly, recyclability or energy performance. This is not a fixed list that is the same for all products. The passport is completed per product group with the data categories established by the ESPR and the corresponding delegated act for that group. What you ask your supplier for is therefore always the translation of those data categories into the specific components or raw materials that this supplier delivers.

Who this applies to, and who it does not

This applies to manufacturers and importers who must have a digital product passport drawn up for a product that falls under a product group for which the ESPR has been declared applicable. The supplier does not need to create a passport themselves; that obligation lies with the manufacturer or importer placing the product on the market. What does lie with the supplier is the obligation to make the underlying information available if requested. This applies to actors in the supply chain: component manufacturers, material suppliers and other links before the manufacturer. It does not apply to data that has nothing to do with the passport, and not to product groups for which no delegated act has yet been adopted — for those products, the passport obligation does not exist at all, and neither does the request to the supplier to provide for it.

No fixed date yet: this depends on the delegated act per product group

There is no round date to name when this request obligation to suppliers applies to all products. The ESPR itself contains the framework — the obligation of actors in the supply chain to provide requested information, and the requirements for what a passport must contain — but the actual entry into force date and the precise data set are laid down per product group in a delegated act. Until that act exists for a particular product group, there is no obligation to maintain a passport and therefore no legal obligation for suppliers to specifically provide for it. Anyone who now enters into discussions with suppliers does so in anticipation of the act that will apply to their product group, not on the basis of an already established date for all products at once.

How to approach this in practice

Start by determining which product group the product falls under and whether a delegated act has already been adopted or is in preparation for it; this determines which data categories will subsequently be required in the passport. Then go through the list of required data categories as it applies to the digital product passport — product identification, technical performance, composition, conformity, and environmental and circularity information — and determine for each category which supplier or component manufacturer has the corresponding source data. Request this data specifically: not "send everything you have", but per component the specific information needed (for example: material composition of this component, test report of this coating, certificate of origin of this raw material). Record who has supplied which data and when, so that a trail can be found back if the origin of a piece of data is later disputed. Finally, check whether the supplied information is in a form that is usable for a digital passport — i.e. transferable and linkable to the product — rather than just a paper certificate that does not readily fit into a data structure.

The legal basis: Article 38 and Article 10 ESPR

This approach follows from two provisions of Regulation (EU) 2024/1781. Article 38 regulates the requirements for actors in the supply chain: it establishes that these actors, upon request, must provide the information necessary to comply with the requirements for the product — the basis on which a manufacturer or importer can request data from a supplier. Article 10 regulates the requirements for the digital product passport itself: what kind of information a passport must contain, in what form, and for whom that information must be accessible. Together, these articles determine both what must ultimately appear in the passport and the obligation of the parties further down the chain to provide the source data required for this.

Those preparing a product passport now can use the data categories of Article 10 as a checklist when formulating a targeted request to suppliers, and it is best to set up the recording of who provided what immediately — that saves investigative work once the delegated act for your own product group enters into force.

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

As a manufacturer or importer, you compile the digital product passport yourself, but most of the content does not come from your own administration. It comes from the parties that supply you: component makers, raw material suppliers, assembly companies. Article 38 of the ESPR (Regulation (EU) 2024/1781) establishes that actors in the supply chain have obligations regarding the provision of information needed for the passport. What this means in practice breaks down into a few recognisable components.

Knowing which data the passport needs

Article 10 of the ESPR describes what a digital product passport must contain in terms of information. For a company with 10 to 100 employees, this first means translating it: determining which of these information requirements apply to which component or raw material, and thus which supplier they must be requested from. This is not a one-time exercise but something that differs per product group and per delegated act — which is why it makes sense to first clarify whether the product passport applies to your products and which data categories are involved.

Actually requesting data from the supplier

The obligation under Article 38 works in practice in two directions: the supplier must provide something, but you must ask for it — and specifically enough. For a company of this size, this usually means that someone is designated to maintain a list per supplier: which data are needed, which have already been received, which are still missing. For companies with a handful of fixed suppliers this is manageable in a spreadsheet; with a broader procurement package it quickly becomes confusing without a fixed format.

Receiving data on time and in the correct form

It is not enough that the data arrive at some point — they must be there before the passport is compiled and published, and in a form that can be processed. For a production company, this means that data provision becomes part of the procurement process itself, not something that is followed up on afterwards. In practice, this works best if the supply of passport data has a fixed place in the procurement terms, so that it is not a matter of asking and hoping but of an agreement that is set in stone. How this is concretely shaped is described in how you record the supply of passport data in your procurement contract.

Data can be substantiated

What a supplier provides becomes part of your passport and thus (partly) your responsibility to the outside world. This does not mean you have to measure or test everything yourself again, but it does mean there must be something to fall back on if the accuracy of a piece of data is questioned. For a company without its own laboratory or testing capacity, this is often the most underestimated part: requesting the figure is one step, documenting the substantiation behind it a second.

Where things go wrong in practice

A few situations come up repeatedly with companies that tackle this issue.

First: the data are only requested at the moment the passport needs to be made, while the supplier is long gone from the process to still deliver something quickly, or the order has long been completed. Second: a general request is sent ("send us your product data") without specifying which data exactly are needed according to Article 10, after which the supplier sends back something that does not match what the passport requires. Third: with an assembly product, it is forgotten that not only the direct supplier but also a subcontractor behind them must provide data — which creates a gap in the chain that is only noticed late. What to ask about in this context is described in which data you request from a subcontractor who manufactures a component. Fourth: data are provided, but no one checks whether they are correct — until a customer or supervisory authority asks about it. And fifth: a company works with multiple suppliers for the same component, for example to spread supply risk, and discovers that each supplier provides different data in a different format, meaning the passport would have to differ per batch. How this is handled is described in what to do if you use multiple suppliers for the same component.

Another recurring pattern is that a supplier simply does not provide data — through unwillingness, lack of knowledge, or because the supplier itself does not know where the information should come from. What can be done about this is described in what you can do if your supplier does not provide the data.

What you can document

A number of documents and agreements make requesting supplier data manageable rather than something that is reinvented each time:

  • A data specification per product group: a list of which information elements from Article 10 of the ESPR belong to which component or which raw material, so that a purchasing manager does not have to figure out each time what is needed.
  • A fixed part of the purchase contract on the provision of passport data, including what happens if that data is not provided or proves to be incorrect. A detailed example can be found in the agreements that can be included in a purchase contract.
  • A control procedure for incoming supplier data, so that not every figure is blindly accepted. See how a supplier's data are checked for accuracy for the approach to this.
  • An overview per supplier of what has been provided and what is still missing, maintained as a fixed part of the procurement file instead of loose email exchanges.
  • A confidentiality agreement for data that the supplier considers confidential, so that requesting detailed information does not stall due to cold feet. See whether a confidentiality statement can be requested from the supplier.
  • A procedure for supplier change, so that it is clear what happens to the existing passport once the supplier is changed. More information on this at whether the product passport must be adjusted in case of a supplier change.
  • Additional agreements for imports from outside the EU, where the question of who supplies which data gains an extra layer. See what the product passport means when importing from outside the European Union.

These provisions make requesting supplier data less dependent on the memory of one purchasing manager, and give a company something to fall back on once a dispute arises over who should have supplied what.

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.