CBAM supplier emissions data request: exact fields and workflow

The job is to create a reviewable supplier record

The goal of a supplier data request is to produce a record that can be reviewed later: what was asked, what the supplier gave back, what evidence supports it, and what remains open. A reply that says only 'carbon data attached' is usually not enough to understand the production installation, period, basis, or calculation path.

This is why the request should be specific. It should give the supplier the product context and ask for the fields that matter for CBAM preparation, while preserving the boundary that the importer and its advisers still need to review the material received.

Start with the goods context the supplier can recognise

The supplier is more likely to answer correctly when the request identifies the goods clearly. Include the import year, CN code if known, commercial description, purchase order or internal reference if helpful, and the supplier name or site that produced the goods.

Do not assume the supplier uses the same internal product language as the importer. The request should connect the importer's customs or purchasing record to the supplier's production record without asking the supplier to guess which shipment or product family is meant.

• Import year and reporting period covered by the request.
• CN code and commercial description, with a note if the CN code is still under review.
• Supplier name, production site, purchase reference, and any product identifier shared between buyer and supplier.
• Requested response deadline and contact for questions.

Ask for the production installation and production route

CBAM data is tied to how and where the goods were produced. The request should ask for the production installation name, address, country, and the production route or process relevant to the goods. That information is different from the supplier's sales office, export entity, or invoice address.

If the supplier cannot identify a specific installation or route, capture that as an open issue rather than forcing the row into a false complete state. The unresolved status is useful because it tells the importer where follow-up is needed.

Request direct and indirect embedded emissions separately

The request should ask for direct embedded emissions and indirect embedded emissions separately, with units, reporting period, and method notes. Combining them into one unlabelled number makes later review harder and can hide whether electricity-related assumptions were handled consistently.

The supplier should also say whether the emissions values are actual values, official default values, or a mixed basis. This field is central because a supplier-reported actual value has a different review path from a row that still relies on official defaults.

• Direct embedded emissions per tonne of goods.
• Indirect embedded emissions per tonne, electricity consumption, and emission factor used.
• Data basis: actual values, official default values, mixed, or unknown.
• Reporting period and whether it aligns with the goods supplied.

Do not skip precursor detail

For goods where precursors matter, the request should ask for each precursor's description, quantity used in each production process, source installation and process, reporting period, and whether its emissions data uses actual values or an official default value. This mirrors the practical fields already used in CBAM Pulse's supplier request draft.

A common weak reply gives a finished-product value but no precursor basis. That may be a useful starting point, but the importer should not label the supplier row as review-ready. Keep precursor questions visible in the gap log until they are answered or deliberately escalated.

Ask for evidence, not just a number

The supplier should be asked for the calculation or monitoring methodology behind the figures, supporting documentation or a reference link, details of any independent third-party check where available, and a follow-up contact. This is a request for traceability, not a demand that the supplier fit one preferred document format.

CBAM Pulse's public supplier request template is based on the European Commission's Communication Template, but it is still a working draft the user reviews and adapts before sending. It is not a legally required format and it is not sent by CBAM Pulse.

• Calculation method, monitoring plan, or explanation of how values were derived.
• Supporting evidence reference, document name, link, or source system.
• Third-party check or verifier involvement, if one exists, labelled carefully.
• Named contact for follow-up questions.

Capture origin-country carbon price information separately

If a carbon price was already paid or is due in the country of origin for the goods, ask the supplier to provide the statement and basis separately from the emissions values. Do not bury it inside the emissions number or treat it as an automatic deduction decision.

Keeping this field separate preserves the evidence trail. It also prevents a supplier's general carbon-market statement from being mistaken for a reviewed CBAM cost adjustment.

Supplier-reported data is not the same as verification

Definitive-period actual-emissions preparation can involve accredited verifier rules and verification materials. But a supplier email, spreadsheet, or calculation note should still be labelled as supplier-reported unless the relevant verification status and scope have been reviewed.

The request workflow should therefore use statuses such as requested, received, missing, needs clarification, reviewed internally, sent to adviser, or verifier path to review. Avoid a single 'done' flag that hides the difference between data collection and verification.

A follow-up cadence that keeps pressure without creating noise

For repeated suppliers, one clean request and a visible follow-up log is better than several disconnected emails. Record the send date, supplier contact, requested fields, response date, missing fields, and next follow-up owner. When the supplier replies partially, update the status by field rather than treating the whole row as complete or failed.

A practical cadence is initial request after the in-scope goods row is identified, first follow-up after the agreed response window, evidence review when material arrives, and escalation only for rows that are still material and unresolved.

Use GSC language without turning it into keyword stuffing

Search Console already shows useful language around CBAM supplier data, CBAM carbon data supplier, supplier carbon data, CBAM template, and CBAM checklist queries. Those phrases point to a real operational problem: people do not just need a definition of embedded emissions; they need a practical way to ask suppliers for the information.

The guide answers that observed intent with a field-level workflow and then sends the reader to the live supplier request template and evidence checklist, instead of creating several near-duplicate articles for each query wording.