furnipas.eu

can I modify data after the product passport has already been published

Changes are possible, but not retroactively just like that

Data in a published product passport can be adjusted, but the ESPR (Regulation (EU) 2024/1781) is based on a passport that follows the product throughout its entire lifecycle and whose information matches the current situation. This means that in practice, a change will more often involve supplementing or updating data than secretly rewriting what was there before. Article 9 of the ESPR requires that the data in the passport is accurate, complete and up-to-date, and that is an ongoing obligation — not something that only counts at the moment of publication.

Which data this applies to, and which does not

The distinction that matters here is between data that belongs to the product as it is placed on the market, and data that can change after sale. Think of repair history, changes of ownership, or additional certifications obtained later — that kind of information is meant to be supplemented as soon as it becomes available. Basic data that determines the identity of the product, such as the unique identification code by which the product is recognised, is fundamentally different: that code must continue to follow the product without change, because the entire recognition system is now built on that. Anyone wondering how that code is assigned in detail will find more information about it how each product receives a unique identification code. What this article does not address is the question of whether an error in the original conformity data can be corrected afterwards without consequences for the manufacturer's liability — that is a different question from the technical ability to adjust a data field, and the ESPR text does not provide a separate answer to it.

When this will apply is not yet determined

No delegated act has yet been published that specifically regulates how changes after publication should proceed for furniture. Articles 9, 10, 13 and 14 of the ESPR do establish the framework — that the passport must be up-to-date, that a register will be created, and that a web portal will be created to make data accessible — but the technical and operational details, including who may carry out a change and how it is recorded, still need to be worked out in product-specific regulations for furniture. Until that legislation is in place, there is no established date and no established procedure to point to. As soon as the delegated act for furniture is published, this will be updated here.

What this is likely to look like in practice

In practice, it is advisable to assume that a change to a passport does not mean that the old data disappears, but that a new, traceable version is created. This is consistent with Article 13, which provides for a register of digital product passports in which traceability plays a role. For those working with furnipas, this comes down to a few steps in practice. First: the data that needs to be adjusted is supplied in the same way as in the initial submission — via the manufacturer's or importer's own system. If the passport has already been linked to an ERP or inventory system, that link can also be used for later changes; how that works is described in linking the product passport to your own system. Subsequently, the change is processed in the hosted passport, without the QR code or the unique identification code on the product itself changing — after all, that remains the fixed reference to the passport, no matter how the content behind it is updated. What the manufacturer or importer can prepare for themselves here is an internal overview of which data has already been supplied and when, so that a later addition or correction can be submitted quickly and without fuss. This is also useful with regard to the period for which the passport must be maintained; more information on this is provided in how long a product passport must remain available.

The legal basis: Articles 9, 10, 13 and 14 of the ESPR

That a product passport must remain up to date follows from Article 9 of the ESPR, which describes the digital product passport as an instrument that makes data about a product accessible throughout its lifespan. Article 10 supplements this with the requirements that the passport must meet, including accuracy and completeness of the data. Article 13 introduces the register of digital product passports, which plays a role in making passports and the data within them traceable — which is relevant in the event of a later amendment. Article 14 regulates the web portal through which data from the passport is made accessible, which touches on the technical side of "amending": an adjustment in the underlying data must translate into what is visible through that portal. However, none of these articles yet provides a concrete procedure for amendments after publication specifically for furniture — that implementation is expected in a delegated act that does not yet exist.

Companies that already work with a product passport or are about to do so can find the most support by keeping their own source data well organised — so that a later addition or correction can be easily provided once a fixed procedure exists for it, and by monitoring when the delegated act for furniture is published, because that ultimately determines how amending will look like in practice.

What you concretely have to do

What is expected of you

The ESPR assumes a product passport that remains usable and up to date throughout the entire lifespan of the furniture. Article 9 of the ESPR (Regulation (EU) 2024/1781) mentions accessibility of data as a core requirement, and Article 10 sets out what requirements apply to that data. This means that a passport is not a snapshot that you publish once and then leave as is, but a data source that can change in practice. For a company with 10 to 100 employees, this translates into a number of separate obligations.

Ensuring that data remains correct

The basic expectation is that what is stated in the passport corresponds to the product as it actually is on the market. If a specification changes — a different type of wood, an adjusted coating, a new supplier of a component — the passport should reflect that. For a manufacturing company, this means that changes in procurement or formulation are not only recorded internally, but also translated into the published data. If linked with an ERP or inventory system this can partly happen automatically, but not every company has set up such a link.

Making a distinction between product and product version

Article 10 of the ESPR addresses the question of which data belongs to which variant of a product. This directly touches on the question of whether an amendment in the passport is a correction of existing data, or actually concerns a new product that deserves its own passport and its own identification code. This distinction is relevant once a piece of furniture is available in multiple variants on the market: each product receives a unique identification code prevents amendments from being inadvertently made to a passport that belongs to a different variant.

Keeping the link with the product recognisable

An amended passport must still be accessible via the same carrier on the furniture. If data changes but the QR code continues to point unchanged to the correct, updated page, nothing has visibly changed for the end user — the furniture maker or the component for placing the QR code on the product therefore simply remains in place. This is particularly relevant when a manufacturer considers having a new QR code printed in the event of an amendment: this is usually not necessary as long as the underlying identification code remains the same.

Being visible in the register

Article 13 of the ESPR describes the register of digital product passports, in which certain data about the passport is recorded. What exactly must be included there and how changes to the passport relate to it are described on the page about the European register of digital product passports. For a company, this means that a change to the passport is not only a correction in its own hosting environment, but may also affect a registration that has been recorded elsewhere.

Keeping it accessible via the web portal

Article 14 of the ESPR concerns a web portal in which data from digital product passports can be consulted. This is an additional layer above the passport itself: it confirms that the data must not only be correct with the manufacturer or on the hosting party's platform, but must also remain consistent at the level of this portal.

Where things go wrong in practice

A passport is updated following a product change, but the old QR code on furniture already delivered points to a passport that now describes a different version — while the physical product at the customer's location is the old version.

A company changes its supplier for a raw material and only updates this in its own ERP system, without checking whether this change is also reflected in the published passport.

For a seasonal colour change of upholstery fabric, an entirely new passport is created, whereas it actually concerns the same product identity — resulting in two passports existing side by side and creating confusion about which one is valid.

A correction is implemented on the hosting party's platform, but not reported to the party responsible for registration in the register, causing the data to diverge in two places.

A manufacturer assumes that a once published passport is "fixed" as soon as the furniture is sold, and therefore sees no reason to correct an error in the material information later.

What you can put in order now

  • An internal amendment protocol: determining within the company whether a product adjustment is a correction of the existing product passport, or gives rise to a new product passport with a new identification code.
  • An overview of which product data are linked to an external system and which are maintained manually, so that it is clear where a change in the process must be implemented.
  • A log of amendments per product passport: what has been changed, when, and by whom — useful if an importer or customer later asks why data differs from an earlier version.
  • Agreements with the hosting party on how and within what timeframe a correction request is processed, and whether that has consequences for the registration in the register or the web portal.
  • A fixed procedure for assessing whether a change in material, colour or composition constitutes a new product variant, in line with the approach also used when assigning a unique identification code per product.

This is not legal advice. This page provides general information about the legislation that this platform concerns. We do not know your situation. If 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-09-05. Is something not right? Let us know — corrections take priority.