How do I approach the product passport for electronics step by step?
The passport is created in four fixed steps
The digital product passport for a piece of electronics or ICT equipment does not come into existence all at once, but builds itself up in a fixed sequence. First, data about the product is collected: materials, origin, repair options, and any other information relevant to that product category. Next, that data is entered into a passport that can be traced via a unique identification number, with a link to the manufacturer or importer responsible for its accuracy. The passport is then linked to a physical data carrier on the product itself, usually a QR code, so that a user, trader or enforcement authority can retrieve the data. Finally, the passport must remain accessible for the prescribed period, even if the product is long gone from the shelf. This sequence — data, linking, data carrier, availability — is the core of Articles 9 and 10 of the ESPR, and applies in principle to every product for which the European Commission makes the passport mandatory.
For electronics and ICT, per product group separately
This approach applies to products that fall under the ESPR and for which a specific delegated act makes the passport mandatory. This means that the obligation does not arise all at once for 'electronics' as a whole, but is introduced separately for each subcategory — white goods for example separately from phones, and phones separately from other ICT equipment. For an importer or manufacturer, it is therefore relevant which specific product group their articles fall into, and not merely that it is 'electronics' in a general sense. This step-by-step approach does not concern other obligations sometimes mentioned in the same breath, such as ecodesign requirements on energy consumption or repairability itself — these are separate rules that may exist alongside the passport, but do not coincide with it. The passport is an information carrier, not a quality mark and not a guarantee that the product meets all requirements.
A date is not yet fixed, but the work plan is
There is not yet a fixed date on which the passport for electronics or ICT equipment becomes mandatory. The obligation arises only once the European Commission adopts and publishes a delegated act for a specific product category; that act then also determines per category from which point onwards the passport is required. The Commission's work plan for the period 2025-2030 lists electronics and ICT equipment as a category for which such delegated acts are being prepared, with an expectation that the first of these will appear no earlier than 2027. That is a planning, not a commitment on an outcome or a firm end date. Until a delegated act is in place, there is therefore no obligation for the product group concerned to maintain a digital product passport. As soon as an act is published, the associated date is fixed and will be stated here.
The practical sequence for those preparing now
Anyone who wants to think ahead about a digital product passport should do so in the order in which the obligation will actually take effect. The first step is to check which specific product category your own assortment falls under, and whether a delegated act is already in preparation for that category. The second step is to inventory the data that such a passport must contain at minimum according to Article 10 of the ESPR — these are often data that already exist somewhere within your own organisation, in procurement, quality or compliance, but have not yet been bundled together. The third step is to consider who will technically host the passport and keep it up to date, because the obligation to keep the data accessible for a longer period does not automatically shift to a third party; that choice lies with the manufacturer or importer. The fourth step is the link with the data carrier on the product, so that the QR code or similar marking at the moment the obligation takes effect actually points to a functioning passport. Anyone who works through these four steps in order will not face surprises once the delegated act for their own product category is published.
Where this is stated: Article 9 and 10 of the ESPR
This structure follows directly from the ESPR itself. Article 9 of Regulation (EU) 2024/1781 describes what a digital product passport is and how it is linked to a product via a data carrier and a unique identification number. Article 10 of the same regulation sets out the requirements that the passport must meet, including the accessibility of the data and the responsibility of the market actor who supplies the data. Both articles form the framework within which later delegated acts, per product category, fill in the details.
Anyone who wants to start right now should best begin by mapping out their own product category and the data that will be needed for it — that inventory takes no waiting time for a delegated act and is the basis for every subsequent step.
What this is based on
- Regulation (EU) 2024/1781 (ESPR), article 9 (digital product passport)
- Regulation (EU) 2024/1781 (ESPR), Article 10 (requirements for the digital product passport)
The regulation itself is on EUR-Lex. We provide references per statement; you do not have to take our word for it.
What you must concretely do
What is expected of you
The digital product passport does not come together all at once. Articles 9 and 10 of the ESPR (Regulation (EU) 2024/1781) describe what a passport must contain and how it must be accessible, but the practical implementation — who supplies what, when, and in what form — is up to the company itself. For an organization of 10 to 100 employees, that means a number of sequential steps, each of which requires someone to drive it.
Collecting and organizing product data
Article 10 lists which information categories belong in the passport, such as data on materials, origin and repair options. For many companies, the first step is not the passport itself, but tracking down that data: is it with a supplier in Asia, with the company's own procurement department, or not documented anywhere? That research usually takes more time than filling in the passport afterwards.
Determining whether and when the obligation applies
Not every electronics product falls under the obligation on the same date; this is regulated per product category through delegated acts. A company that operates multiple product lines does well to determine for each line when the obligation comes into play, rather than waiting until everything must be done at once. Anyone missing that overview can build it up in the article on how I regulate the product passport for all my product lines at once.
Arranging the QR data carrier and hosting
Article 9 requires a data carrier on the product by which the passport is digitally unlocked, and Article 10 sets requirements for its accessibility during the required period. This is a technical and a logistical step: who ensures that the QR code is placed on the product or packaging, and who guarantees that the underlying data remains available for ten years? For a mid-sized company, this is often the moment when a decision is made whether to build this in-house or outsource it.
Testing before the passport goes public
A passport that is live but displays incorrect or incomplete data is harder to fix than a passport that has been checked in advance. It is advisable to review how a product passport can be tested before it is published, so that errors in links or missing fields are noticed before the first customer or regulator scans the QR code.
Preparing employees to work with the passport
The passport does not only affect compliance or legal matters; it also affects procurement, customer service and sometimes the shop floor. Anyone who needs to explain what a customer sees when scanning the code, or who needs to respond if a regulator asks about it, needs training for that. This topic is covered in the article on how employees learn to work with the product passport.
Where things go wrong in practice
A number of situations come up regularly at companies that are working with the product passport.
Data that is not centralized anywhere. Material data is held at the factory, warranty information is with customer service, and repair instructions are with an external party. No one has an overview, and the passport remains on hold until the last moment.
The QR code is seen separately from the passport. A company arranges a QR code on the packaging, but the underlying data is not kept up to date. After a product change, the code then points to outdated information.
All product lines are treated as one project. Because the deadlines differ per category, treating all lines the same leads to unnecessary rush for lines that still have time, and delays for lines that are up first.
Testing is skipped because the deadline is approaching. Under time pressure, the passport is published directly without review, after which errors only come to light when a customer or regulator responds to them.
Staff are only informed once the passport is already live. Customer service receives questions about the QR code without knowing what is behind it, leading to unclear answers to customers.
What you can document
- An overview of which product data are required according to Article 10 of the ESPR, and which organisations currently have this data available.
- A schedule per product line, including the expected date on which the obligation for that category comes into effect — to be organised using the document on how to plan the implementation of the digital product passport in the organisation.
- Agreements with suppliers on who supplies which data and in what format.
- A test protocol for the passport before it is released, including who carries out the inspection.
- An overview of who within the organisation needs to be trained, and when.
- An estimate of the costs per step, to be compared with the indication in the article on what a digital product passport for electronics costs.
- A decision on hosting and the QR data carrier: developed in-house or outsourced, and which requirements this decision must meet according to Article 9.
This is not legal advice. This page provides general information about the regulations that this platform covers. We are not familiar with your situation. If you are in doubt about your own case, consult a lawyer or the competent supervisory authority.
Written with AI based on the sources above, checked by a human on 2026-08-22. Is something incorrect? Let us know — corrections take priority.