CBAM downstream products: current scope vs 2028 proposal

Current law and proposal scenarios are separate datasets

A commercial product name such as bracket, fastener, machinery inputs, automotive components, or fabricated articles is not a current-scope answer. Current EU CBAM scope follows the exact CN code and description in the adopted Annex I source. The portfolio record therefore starts with the customs-classification source and the reviewed current Annex I version.

COM(2025)989 is a legislative proposal, not current law. It proposes applying the selected downstream extension from 1 January 2028. The Council general approach and the European Parliament first-reading work are institutional positions inside the ongoing ordinary legislative procedure, not final adopted scope. Keep each source as a separate dated scenario rather than merging candidate rows into one predicted future list.

The safe operating rule is asymmetric: a current adopted match can enter the current supplier/evidence workflow, while a proposal-only match remains a proposal watch item and monitoring record. Proposal monitoring can create an owner, trigger, and preparation note, but it cannot by itself change the current goods checker, calculations, supplier requests, declaration records, or applicability state.

This page owns the portfolio comparison and change-impact queue. The downstream-expansion proposal guide owns the legislative explanation and procedural narrative; the goods-scope guide and current goods checker own current Annex I discovery.

Institutional status and source ledger

Pin the institutional status before matching portfolio rows. A source that is newer or politically important does not automatically outrank adopted law for current operations.

As reviewed on 20 August 2026, the European Parliament Legislative Observatory recorded the file as awaiting Parliament's first-reading position. The ENVI committee voted on 6 July 2026 and its report was tabled on 9 July 2026; the listed 14 September 2026 plenary date was indicative and had not occurred. The procedure had no final adopted and published amending act.

Portfolio comparison field manifest

Each saved goods row needs enough source and version context to reproduce the comparison later. A yes/no proposal flag is too weak because the answer depends on classification state, current source, selected scenario source, and any `ex` or material-content condition.

These fields are a product-designed monitoring structure, not an official classification or Registry form. Preserve the source record and reviewer state rather than replacing them with a generated conclusion.

Current-versus-proposed states and actions

Use one combined state that preserves the current-law answer and the selected scenario answer separately. The state is a routing aid, not an official classification or future-scope prediction.

Current action always comes from the current adopted source. A proposal candidate can create monitoring work in parallel, but it cannot upgrade or downgrade the current state.

Direct CN rows and conditional ex rows

Current Annex I and the proposal texts contain different row shapes. A direct CN row can be compared against a reviewed code. An `ex` row limits the candidate description to the part of a code meeting the stated condition, such as containing specified input materials. Code-prefix presence alone is therefore not enough.

The Commission proposal contains direct rows and `ex` or material-dependent rows for selected steel- and aluminium-intensive downstream goods. The Council general approach is a separate institutional text with its own candidate annex. Do not assume the lists or conditions are byte-identical.

CBAM Pulse must fail closed on conditional rows. It can record the selected source row and an unresolved condition; it does not determine composition, classify goods, or auto-promote the row to affected.

Compare source versions without inventing final scope

A buyer may reasonably want to see how a row behaves under the Commission proposal, Council general approach, Parliament position, and eventual final act. That comparison is useful only if every column names its source and date.

The Council reached a general approach on 12 June 2026. The Parliament procedure then progressed through committee, but on 20 August 2026 the file still awaited Parliament's first-reading position. Neither stage is a final adopted and published amendment.

When another institutional text appears, add a new scenario version. Do not overwrite the Commission or Council scenario and do not label a committee or plenary event as final adoption.

Synthetic portfolio change-impact example

This fictional example demonstrates state routing only. The names, classifications, match states, and references are synthetic; they do not classify a real product or predict the final legislative outcome.

Rows Birch and Copper use familiar current Annex I examples—a steel bolt and an aluminium article—to show that downstream-looking goods can already be current-scope. Row Elm demonstrates a proposal-conditional `ex` row whose material condition remains unresolved. Row Fir shows a reviewed no-match against the selected source versions. Row Grove has only a product description and stays blocked.

No proposal-only row enters current calculations or supplier requests. The scenario columns support monitoring, portfolio triage, and future recheck work only.

Change-impact queue and owner actions

A proposal comparison becomes actionable when it produces a bounded queue: which saved rows may need future recheck, why, under which source, and after which official trigger. It should not create a speculative mass supplier-data campaign.

Prioritise rows by evidence state and operational dependency rather than by headline interest. Current affected rows already have current work. Proposal candidates need source/version monitoring. Conditional rows need scenario evidence. Unknown and blocked rows need classification or source resolution first.

• Current affected: keep current supplier, evidence, mass, cost-planning, and preparation owners moving.
• Proposal candidate: assign a monitor owner and next official trigger; do not alter current operations.
• Proposal conditional: capture the exact `ex` condition and missing scenario evidence.
• Checked-no-match: preserve source version and reviewer; recheck only on a defined trigger.
• Unknown: obtain a reviewed CN code before any current or proposal match.
• Blocked: record the conflict, affected row, owner, and resolution path.

Update triggers and no-action-before-adoption

The monitor should wake on official events, not rumours or target dates. An indicative plenary date is a calendar watch item, not proof that a vote occurred. A provisional agreement is not the same as an adopted and published act.

Even after final adoption, the portfolio dataset should change only after the final text, annex, application dates, transitional provisions, and implementation material are reviewed. This prevents a headline from silently rewriting current deterministic tools.

Route current rows and monitor proposal rows

Current affected rows can move through the current goods, supplier request, evidence checklist, verification, mass, cost-planning, and preparation-pack workflow. That route is justified by current adopted source state, not by proposal language.

Proposal-only and conditional rows remain in a separate monitor. Do not request full supplier emissions data solely because a row appears in one proposal scenario unless another current business or legal reason independently requires it.

A buyer may choose low-cost readiness work such as confirming the portfolio row, owner, classification source, material description, and upstream contact. Label that work commercial preparation, not a current CBAM obligation or prediction of final scope.

• Current route: exact current source, classification state, supplier/evidence action, and review date.
• Proposal route: selected scenario source, match type, monitor owner, and official trigger.
• Conditional route: exact `ex` condition and unresolved evidence.
• No-action boundary: no current calculation, filing, supplier-request, or tool-state change solely from proposal status.

Common mistakes and held conclusions

The first mistake is treating all finished goods as outside current CBAM. Current Annex I already contains downstream-looking rows such as CN 7318, CN 7326, and CN 7616. The opposite mistake is treating every steel, aluminium, automotive, or machinery product as current or future scope.

The second mistake is merging the Commission proposal and Council general approach into one candidate list. The third is calling a committee report or indicative plenary date final. The fourth is treating an `ex` row as a simple code-prefix match.

Hold conclusions where classification, source version, material condition, or institutional status is unresolved. Record what would close the gap; do not fill it with a model guess, supplier marketing description, or adoption forecast.

How CBAM Pulse fits portfolio monitoring

CBAM Pulse can keep source versions, portfolio row references, current/proposal states, owners, blocked reasons, and official recheck triggers visible. The current goods checker remains tied to reviewed current scope; proposal scenarios stay outside current deterministic results.

CBAM Pulse does not classify goods, determine material composition for `ex` rows, score anti-circumvention, infer intent, predict adoption, set a future date, file declarations, or decide current/future applicability or liability.

Use the current goods checker for current-scope discovery, the procedural downstream-expansion guide for legislative context, sector/buyer guides for current workflows, and updates for source-backed status changes.