must someone also be able to view the product passport without internet connection
The passport is an online service, not an offline file
No, not in the sense that a copy without internet connection needs to exist. The digital product passport works via a unique identification code and a data carrier — in the case of aluminium typically a QR code — that directs the user to an online environment. Anyone wishing to consult the passport scans the code and arrives at a web page or in a system that displays the data up to date. That presupposes a connection at the moment of consultation. The ESPR contains no obligation to additionally provide an offline version, for example as a file that works independently of the internet.
What does and does not fall under this question
This question concerns access to the passport at the moment someone wishes to view it — a technician at a location without coverage, a buyer in a building with poor wifi, an inspector in a warehouse. For that situation: the data is online, and without a connection there is no direct access. That is different from the question of how long the data remains available over time — that is a matter of retention period, not connection, and you must not confuse the two. Nor does this concern what happens if the company behind the passport ceases to exist; that affects the continuity of the data, not the question of whether internet is needed to view it. Anyone wishing to delve deeper into this reads how long a product passport must remain available or what happens to the passport if a company stopsBoth topics revolve around sustainability of the data, not about offline accessibility.
When this will apply is not yet established
For aluminium semi-finished products, no delegated act has yet been published that sets the exact requirements for the passport — including the technical operation of the data carrier — for this product group. The ESPR itself (Article 11) describes the technical design and operation of the digital product passport in general terms, but the concrete rules per product group follow from separate delegated acts. Until one is published, there is no legal obligation for a product passport for aluminium, and therefore no concrete requirement on how consultation must technically work. As soon as that act is published, the date will be mentioned here.
What this means for those already working with a passport
Anyone already setting up a product passport — in anticipation of the obligation, or because a customer requests it — can assume an online setup without having to worry about an offline variant. The practical sequence usually looks like this: first it is determined how each product receives a unique identification code, something that an explanation of how to assign that code goes into further. Then follows the choice of how that code appears on the product — for example as a QR code on a profile or coil, see the options for applying a QR code to aluminiumNext, it is determined what is waiting online behind that code: a web page, a connection with an existing system, or a connection to the European register. For anyone with an existing ERP or inventory system, it is worth checking whether that system can be connected directly, as described in linking the passport to your own system. Anyone concerned about poor connectivity at a location would be best advised to look at the robustness of the data carrier itself — a well-applied, clearly legible code, and a QR code that also works with a simple camera without requiring a special app that itself requires internet. That does not concern whether the data is offline, but does concern how smoothly consultation works in practice.
The basis: Articles 10, 11 and 12 of the ESPR
Article 10 of the ESPR sets out the general requirements for the digital product passport, including that data must be accessible via the data carrier. Article 11 specifically addresses the technical design and functioning of the passport, and describes that the data carrier points to an online location where the data can be consulted up to date — an approach that by nature assumes that a connection is available at the time of consultation. Article 12 governs the unique identification code that belongs to each product and which forms the link between the physical product and the digital data. Article 13 describes the register of digital product passports, the central facility in which (part of) the data is also maintained by the Commission — more on this is set out at the explanation of the European register. Nowhere in these articles is there an obligation for an offline copy or file; the emphasis is always on an up-to-date, online consultable dataset.
Anyone who wants to start working with a product passport for aluminium now would be best advised to begin with the choice of the data carrier and the unique identification code, and to leave the actual setup of the online environment to a party that provides hosting and updating — so that the question "does this also work without internet" becomes primarily a question about the quality of the QR code on the product, not about the architecture of the passport itself.
What this is based on
- Regulation (EU) 2024/1781 (ESPR), Article 10 (requirements for the digital product passport)
- Regulation (EU) 2024/1781 (ESPR), Article 13 (register of digital product passports)
- Regulation (EU) 2024/1781 (ESPR), Article 11 (technical design and operation of the digital product passport)
- Regulation (EU) 2024/1781 (ESPR), Article 12 (unique identification code)
The regulation itself is on EUR-Lex. We refer per statement; you do not have to take our word for it.
What you must concretely do
What is expected of you
The ESPR governs how a digital product passport must work, but an explicit obligation that the passport must also be accessible without an internet connection does not appear as such in the text. What there is, however, are a number of technical requirements that determine how accessible and how robust the passport must be — and from these it can be inferred what is expected in practice from a provider such as alupas.eu and from a manufacturer.
Access via the data carrier, not via a separate file
Article 11 of the ESPR (Regulation (EU) 2024/1781) describes the technical design and functioning of the digital product passport. The passport is unlocked via a data carrier on the product — in practice a QR code. That code points to data that is held online; the passport itself is not a file that you download and take with you. For a company of 10 to 100 employees, this means that the question "offline or online" actually shifts to a different question: is the data carrier on the product itself always readable, even without an internet connection being available at the time to the person scanning? How that carrier comes to be placed on the aluminium and remains in place is described on How does the QR code for the digital product passport get onto my aluminium?.
Availability of data, not of the connection
Article 10 of the ESPR (Regulation (EU) 2024/1781) sets requirements for the product passport itself: what data it must contain and how that data must be accessible to different user groups — consumers, economic operators, supervisory authorities. These requirements concern the content and accessibility of the data at the time someone consults it, not the question of whether a user must be able to keep a local copy in case there is no network. For a production company, this means that attention should be focused primarily on the question of whether the correct data is unlocked at the right time, not on building an offline copy of the passport.
Uniqueness of identification remains necessary, connection or not
Article 12 of the ESPR (Regulation (EU) 2024/1781) requires a unique identification code per product. This code is the key by which a passport is found, and that code is physically on the product — even if there is no connection, the code itself is readable or scannable. What is then still missing in the absence of internet is the link to the underlying data. How such a code is assigned and managed is explained on How do I give each product a unique identification code?.
Findability via the register
Article 13 of the ESPR (Regulation (EU) 2024/1781) governs the register of digital product passports. This register is an online facility in which (part of) the passport data is entered so that supervision and control can take place centrally. This register is also by definition an online system; the regulation does not describe any offline equivalent. What exactly ends up in that register and who has access to it is addressed on What is the registry of digital product passports and what do I need to enter into it?.
Where things go wrong in practice
A number of situations recur in practice at aluminium-processing companies when it comes to passport accessibility.
At a production location with limited or shielded wifi, an employee or inspector can scan the QR code, but does not establish a connection to the underlying data. This is often incorrectly interpreted as an error in the passport itself, whereas it is a local network issue.
When exporting to locations with variable connectivity — a storage facility at a port, a shipyard without a fixed network — a customer sometimes expects the passport to be "simply" accessible like a PDF stored locally. That is a different usage model than what the data carrier offers.
A third situation: a profile manufacturer copies the passport data to a separate PDF file "in case the website goes down" and distributes that file. Such a copy may contain outdated or incorrect data once the passport is amended after publication — see also how do I update data in a product passport that is already published — so that two versions of the truth exist side by side.
A fourth situation arises when the QR code on the aluminium itself becomes damaged or unreadable through transport, coating or wear. In that case it is not a question of an offline problem, but of a physical problem with the carrier; that scenario is described on what happens if the QR code on my aluminium becomes illegible.
Finally: a foundry that links the passport to its own ERP system sometimes assumes that internal system access is equivalent to compliance with external accessibility requirements. Both things go hand in hand, but they are not identical — see Can I link the digital product passport to my ERP or inventory system? for how that coupling works properly while keeping external accessibility in view.
What you can document now
- An overview of the locations and circumstances in which the aluminium and the associated QR code are physically scanned, including known network limitations at those locations.
- Agreements with customers about what they expect in terms of passport accessibility at their own location, before a delivery takes place.
- A procedure for the event that the data carrier is damaged, including who within the company is responsible for repair or replacement.
- An internal agreement about whether or not to distribute local copies of passport data, and if so, how to prevent an outdated copy from remaining in circulation.
- Documentation of the chosen technical setup of the data carrier and the link to the underlying data, so that if a customer or supervisor has questions, it is clear how access to the passport is technically arranged.
This is not legal advice. This page provides general information on the legislation that this platform covers. 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 incorrect? Let us know — corrections are prioritised.