What does a product passport for products cost?
No statutory amount, but a number of fixed cost items
The ESPR (Regulation (EU) 2024/1781) does not prescribe a price for a digital product passport; the regulation determines what must be included and how long it must remain accessible, but not what it may or must cost. What it costs in practice follows from the activities required to comply with Article 9: collecting and maintaining product data, converting that data into a passport in the correct format, applying a QR data carrier to the product, and keeping the whole thing online and accessible for the required period to those authorised to consult the passport. These items apply in principle to every product subject to a passport obligation; their scale depends on the number of products, the number of product categories in which a manufacturer is active, and the choice to organise this in-house or outsource it.
For whom this is relevant, and for whom it is not
This question applies to manufacturers and importers of products for which a passport obligation will apply via a delegated regulation under the ESPR. The ESPR itself is a framework regulation: Article 9 sets out what a product passport must meet once a product category has been designated, but the regulation does not govern tariffs for service providers, software suppliers or hosting parties. There is therefore no maximum price or reference price in the law, and there is also no EU-established fee for having a passport compiled. For product categories not yet designated under a delegated act, the passport obligation does not yet apply, and these costs do not therefore apply there either.
When the costs will actually come into play
The obligation to maintain a digital product passport only arises at the moment a delegated regulation under the ESPR enters into force for a specific product category; those regulations are adopted separately for each product category. For many product categories, the date when this will apply is not yet set — the European Commission is working this out further for each product category. Until a product category is designated and the associated rules apply, there is no statutory obligation for a passport and therefore no statutory moment at which the costs for it must be incurred. What is established is the framework in Article 9: once a product category is designated, the requirements for content, accessibility and the link with a data carrier as described therein apply.
How this plays out in practice for a manufacturer
Anyone wanting to know what a product passport will cost starts by finding out whether and when their own product categories fall under a delegated regulation — this determines whether and from when something needs to be organised. After that, it is a matter of mapping out which data is already available (materials, origin, repair information, conformity) and which still needs to be collected, as that work is often the largest cost item, not the technology around it. Then there is the choice between building and maintaining a system yourself, or outsourcing this to a party that processes the data into a passport, supplies the QR data carrier and provides hosting. In making that choice, it matters that a passport is not a one-off: it must remain up to date as long as the product is in circulation and for as long as the retention period runs, which means that maintenance is a recurring cost item alongside the one-time setup. For a manufacturer with products in multiple product categories, there is also the fact that each product category can have its own content requirements, which makes compiling it separately for each product category additional work, even if the underlying technology is the same.
What this is based on
Article 9 of the ESPR (Regulation (EU) 2024/1781) describes what a digital product passport must contain, how it must be accessible and what role the data carrier plays in this, without setting a price or fee. The European Commission's page on the ecodesign regulation for sustainable products provides the broader framework within which product categories are gradually designated via delegated acts, and confirms that the implementation takes place per product category. For determining costs, what is therefore most relevant is what the law requires in terms of data and accessibility — the rest is a matter of organisation, not of legal requirement.
If you want to prepare now, the best approach is to first determine which product category your own products fall or will fall into and to follow the progress of the associated delegated regulation via the European Commission's page. In parallel, it is useful to already inventory which product data you already have internally and which still need to be collected, regardless of the eventual choice to do this yourself or outsource it — that work is needed as soon as the obligation takes effect, and does not need to wait until that date is set.
Where this is based on
- Regulation (EU) 2024/1781 (ESPR), article 9 (digital product passport)
- European Commission — ecodesign regulation for sustainable products
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
The ESPR (Regulation (EU) 2024/1781) stipulates in Article 9 that a product passport must exist, what it must contain and how it must be made accessible via a data carrier. What the regulation does not do is state a price. There is no tariff, no indicative amount and no cost ceiling in the text. That means that "what does it cost" is not a question that the legislator answers — it is a question that varies from company to company and from product group to product group, depending on what data and systems are already in place. What can be described is: which obligations incur costs, and where those costs typically arise.
Collecting and organising data
A product passport consists of data: materials, origin, repair possibilities, conformity, and whatever the relevant product group requirement further requires. For a company of 10 to 100 employees, the first cost item is almost always here: not in the passport itself, but in the fact that that data is often scattered across procurement, quality and sometimes at the supplier. Finding and validating that data is work that must be done thoroughly once and then maintained. Companies that start here before their own product group is due spreads that cost over more time — see Is it wise to start before my product category is due?
A data carrier and hosting
Article 9 calls for a QR code or similar carrier that points to the passport data, and the data must be consultable for the prescribed period. This translates into two separate cost items: creating the carrier per product (or per variant) and hosting the data over years. A company that wants to build this technically itself pays mainly in development time and maintenance; a company that outsources this pays per product or per subscription. With multiple variants of the same product, there is also the question of whether one passport is sufficient or not — see can I use a product passport for multiple variants of the same product, because that directly reduces the number of passports that need to be created and maintained.
Keeping it current over time
A passport is not a snapshot. Repairs, changes in composition or a new conformity status belong in it. That is an ongoing cost item, not a one-time one. For a company with a limited number of product lines, that is manageable; for a company with many variants and frequent changes, this adds up faster than the initial setup itself.
Staff who have to work with it
The obligation affects not only systems, but also people: who in the organisation ensures that new product data enters the passport, who checks whether a passport is correct before a product leaves the building. That is an organisational cost that is easily forgotten in a budget that only looks at technology. See how do I prepare my staff for working with the product passport for what that preparation involves in practice.
Where things go wrong in practice
A first scenario: a company requests a quote based on "one passport per product" without taking variants into account, and discovers afterwards that the number of passports is three or four times higher than budgeted.
A second: the costs of data collection are underestimated because they are written off internally as "normal work of quality or procurement", so that the total picture of the implementation is not visible anywhere.
A third: hosting is seen as a one-time cost, while the obligation requires accessibility over a longer period — so that a company faces an unexpected follow-up invoice after a few years, or worse, a passport that is no longer accessible.
A fourth: investment is made in a technical solution before it is clear whether the company's own product group is even subject to the obligation, or what requirements apply within it — see Does the digital product passport apply to my products? Spending money on the wrong specification is a cost item that is easily avoided by answering this question first.
A fifth: companies wait until the rules for their product group are final before making any investment, and then have to catch up in a short time what would have been cheaper spread over a longer period. See also What can I do now while the rules are not yet final?
What you can document
- An overview of which product groups and variants fall under the obligation, and which do not yet — as a basis for a realistic cost estimate.
- An inventory of where the required data already exist (procurement, quality, supplier) and what is still missing or needs to be validated.
- A choice between building and hosting in-house or outsourcing, with the associated cost structure (one-time versus ongoing) explicitly set side by side.
- Agreements on who within the organization is responsible for keeping product passport data current, including the point at which a product change must lead to an update in the passport.
- A test setup before the obligation takes effect for your own product group, so that teething problems and underestimated cost items become visible before the moment they are required to be resolved — see can I make a test version of the product passport in advance
- A phased implementation plan, so that costs become visible in stages rather than as one large item afterwards — see How do I approach the product passport for products step by step?
What a product passport costs exactly is not a question that can be answered with a single figure — not because the answer is hidden, but because the legislation itself does not specify an amount and practice differs per company. What can be described, however, and what a company can control itself, is which choices determine the costs: how many variants, how much in-house development versus outsourcing, and how early the underlying data are put in order.
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.