alupas.eu

What happens to the passport if I process aluminium further?

Further processing may require a new passport

The digital product passport that accompanies the aluminium semi-finished product is created for that product as it leaves the manufacturer or importer. If the aluminium is subsequently further processed into another product — a profile that becomes a window frame, a casting that becomes part of a machine, packaging aluminium that becomes a can — then the question changes in character: is this still the same product with the same passport, or does a new product emerge for which its own passport is required? That answer is not fixed in the ESPR itself, but is determined per product category in a delegated act. Such a delegated act is expected for aluminium semi-finished products; for the end products into which further-processed aluminium ends up, different trajectories apply, with their own timeline. What the ESPR does establish: actors in the supply chain have obligations to pass on passport information and keep it accessible (Article 38), and each product or batch receives a unique identification code that links the passport to that specific product (Article 12). These two elements together determine in practice what happens to the data when the material changes form.

For the semi-finished product, not automatically for the end product

The passport that is compiled via alupas.eu belongs to the aluminium semi-finished product: the profile, the casting, the coil or sheet as it leaves the manufacturer or importer. That passport contains the data that is known at that time — origin, composition, recycling content, and what is otherwise established in the delegated act for aluminium. As soon as the material is sawn, cast, extruded into a new profile, anodised, or combined with other materials into an end product, a new product is in fact created. Whether that new product also falls under the ESPR passport obligation depends on the product category in which it ends up — windows, packaging, machine components — and on the question of whether a delegated act has already been established for that category. That is a different trajectory from that of the aluminium semi-finished product itself, with its own timeline that cannot be derived from the sources here. What therefore does not apply: the passport of the semi-finished product does not automatically 'move with' it as a ready-made passport of the end product. It is rather a building block: the data in it may be relevant for a passport of the end product, but that is a separate exercise.

No fixed date yet for further-processed end products

For the aluminium semi-finished product itself, the passport obligation is expected around 2029, with a delegated act anticipated for 2027; that date is not yet fixed and will be updated here as soon as the act is published. For end products made from further-processed aluminium, a separate track applies within the ESPR work plan, with its own — possibly later or earlier — planning per product group. As long as no delegated act has been established for such an end product category, no passport obligation yet applies to that end product, regardless of whether the aluminium semi-finished product used is itself already under the obligation. Until then, what Article 38 and Article 12 regulate in general terms remains in place: obligations to pass information on through the supply chain and to make products uniquely identifiable, as soon as and insofar as a product category falls under the ESPR rules.

What this means for those who further process aluminium

When you purchase and process aluminium semi-finished products, you can first of all keep the digital product passport of that semi-finished product and take the data in it — origin, composition, recycling content — as basic information for your own process. This data may be needed once your end product becomes subject to its own passport obligation, and it is more practical to have it on hand than to reconstruct it afterwards. Secondly, it is useful to monitor which product category your end product is intended for, and to check whether a delegated act is already in preparation for it within the ESPR work plan — that determines whether and when a passport obligation arises there. Thirdly: as long as your own end product does not fall under an established delegated act, there is no legal obligation to draw up a passport yourself, even though the aluminium you are working with is itself passport-certified. And fourthly, if the processed product is resold to the next party in the chain, the thinking behind Article 38 remains relevant: information that is needed to meet obligations further down the chain must remain available, even though the precise form of it is not yet defined for every product category.

The basis: Article 38 and Article 12 of the ESPR

The fact that passport information must be able to flow through the chain follows from Article 38 of Regulation (EU) 2024/1781 (ESPR), which imposes obligations on actors in the supply chain with regard to making available and passing on product information. The fact that each product or batch is linked to a specific passport via a unique identification code follows from Article 12 of the same regulation. Together, these provisions explain why a passport is in principle attached to a concrete product, and why processing into a new product raises the question of whether a new passport is needed — a question that is answered per product category in the delegated act that applies to it, and not in the ESPR itself.

Anyone currently processing aluminium semi-finished products is well advised to keep the passport and underlying data of the purchased semi-finished product, monitor whether there is any movement in the ESPR work plan for their own product category, and in case of doubt about a concrete situation, consult the official texts or the work plan of the European Commission — this page will be updated as soon as the delegated act for aluminium has been published.

What this is based on

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

Aluminium that enters a company with a product passport often changes shape before it leaves again: profiles are sawn, coated, rolled, cast into a new component. The question that then arises is simple — does the old passport remain valid, or does a new obligation arise? Article 38 of the ESPR (Regulation (EU) 2024/1781) regulates the role of actors in the supply chain, and from this it can be inferred what is expected in practice from a processing company.

Checking whether the passport still fits the product after processing

A passport is linked to a product as described at the time of issue: a specific alloy, shape and composition. As soon as the aluminium changes significantly in shape or composition, the original information no longer applies directly to the result. For a company of this size, this means that for each processing step, it is checked whether the received passport still provides the correct basic data — alloy, origin, recycled content — or whether a new passport is drawn up for the processed product.

Passing on basic data to the next link in the chain

Article 38 is based on a chain in which every actor keeps available the information needed to compile a passport further down the line. For a processing company, this means that the data received from the supplier — composition, origin, possibly recycled percentage — do not disappear after their own processing, but are passed on or remain accessible to whoever takes the product off their hands. Practically speaking, this is often nothing more than maintaining administrative records that match what was requested at the time from the aluminium supplier. requested from the aluminium supplier.

Taking along or replacing the unique identification code

Article 12 of the ESPR regulates the unique identification code assigned to a product. In the case of further processing, the question is whether that code goes with the new product, or whether a new code — and thus a new passport — is needed. For simple processing that does not significantly change the identity of the product, the existing code and the associated passport can in many cases be retained. In the case of major processing, where a new product is created that itself falls under the passport obligation again, a new code and a new passport are more likely. This consideration is comparable to the question that arises with the product passport for aluminium from outside the European Union: the extent of processing determines what happens to the existing data.

Keeping an eye on outsourced work

Many processing companies have part of the process — anodising, coating, precision machining — carried out by a third party. Even then, the question remains of who keeps the passport data up to date. Whether a subcontractor supplies data themselves, or whether this remains the responsibility of the contracting company, is a point that can be clarified in advance; see whether a subcontractor processing aluminium must also provide data.

Where things go wrong in practice

The passport is passed on one-to-one without thinking. A profile is sawn and coated, and the passport of the raw material is passed on unchanged to the customer — while the coating has altered the composition and thus part of the information in the passport.

Multiple batches of aluminium are combined without the data being combined. When mixing material from different origins for one casting process, a new product is created whose composition can no longer be derived one-to-one from a single source passport; this applies particularly to data for mixed batches.

The link with the original supplier is lost. After a number of processing steps, it is no longer possible to trace which batch the aluminium originally came from, making it impossible to substantiate the origin data in the new passport — a situation comparable to no access to source data.

Subcontractors work with their own, different data. An external processor delivers its own certificate or dataset that does not align with the product passport format of the client, resulting in missing or conflicting data when compiling the final passport.

No new identification code is created for a substantially new product. The old number remains in circulation while the product is factually no longer the same as the product for which the code was originally assigned.

What you can document now

  • An overview per processing step of what happens to the composition and form of the aluminium, and whether this has consequences for the passport.
  • The basic data received from the supplier, stored in a way that can be linked to the batch being processed further.
  • Agreements with subcontractors on who supplies which data, to be documented in the same way as agreements on the supply of passport data in a purchase contract.
  • A fixed procedure to check whether received data align with the material that actually arrives, as described in checking the data of the supplier for accuracy.
  • A decision rule — even if only a brief internal note — on when a processing step is considered "significant" and thus gives rise to a new passport with a new identification code, and when the existing passport is retained.
  • A file per product group in which it is documented how data from multiple suppliers for the same alloy are combined, see processing data from multiple suppliers for the same alloy in one passport.

As long as the delegated act for aluminium has not yet been published, it is not certain at what level of detail this documentation will be required. Record-keeping that already aligns with the structure of Article 38 and Article 12 of the ESPR is a preparation that retains its value once the final requirements become known.

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-08-22. Is something not right? Let us know — corrections are prioritised.