Home/ DPP
DPP

DPP for Aluminium: evidence, data provenance and status

For aluminium, DPP work concerns product information, identity, source provenance and operator responsibility under ESPR measures. It must remain distinct from CBAM embedded-emissions requirements even where some supply-chain actors overlap.

Why the documentary record matters

The documentary chain can run from product and identifier to an economic operator, a required data field, a source system or supplier, a supporting source and the version ultimately exposed through the passport. A broken link can make a technically available data field difficult to defend.

What the evidence needs to connect

A Digital Product Passport makes product information accessible, but accessibility is not the same as evidentiary quality. Product identity, unique identifiers, responsible economic operator, source data, supporting records and version history still have to remain coherent.

Aluminium

product / model / variant identity

responsible economic operator

source data

supporting evidence

version and update history

Common documentary risks

Current regulatory status

The Commission’s current indicative ESPR Working Plan timing places Aluminium around 2027. This is a planning priority, not by itself an applicable product-specific DPP obligation. Binding requirements depend on subsequent measures or other applicable product legislation.

WEETRA documentary-review perspective

CBAM remains WEETRA’s primary operational review application. EUDR and DPP are presented as regulatory documentary-evidence domains; this content does not create an identical commercial service or pricing model.

Official sources

Official EU sources are used to describe the current regulatory position. WEETRA commentary explains documentary implications and is not legal advice.

Related pages

Specific evidence focus

Aluminium DPP evidence focus

Aluminium product identity can depend on alloy, form, recycled/primary content claims, operator information and source-system records. Any future product-specific DPP field still requires attributable provenance and controlled versioning; a passport interface is not itself proof of the underlying claim.