Home/ DPP
DPP

DPP for Aluminium: evidence, data source history and status

For aluminium, DPP work concerns product information, identity, source history 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 record may need to connect the product and its identifier to the responsible operator, the required data field, the source system or supplier, the supporting document and the version shown in the passport. If one of those links is missing, the data may be available but difficult to justify.

What the evidence needs to connect

A Digital Product Passport makes product information accessible, but accessibility alone does not make the information reliable evidence. Product identity, unique identifiers, the responsible economic operator, source data, supporting records and version history still need to line up.

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.

What Weetra looks for in the documents

CBAM remains Weetra’s main operational service. EUDR and DPP are covered as developing areas of regulatory evidence work, not as equivalent commercial services with the same pricing model.

Official sources

The legal information on this page is drawn from official EU sources. Weetra explains what those rules mean for the documents and records a business may need; this is not legal advice.

Related pages

Specific evidence focus

Aluminium DPP evidence focus

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