CBAM Supplier Data Request: Template and Checklist

Requesting CBAM data from your overseas suppliers is one of the most important steps in your compliance process. The more complete the data you receive, the lower your CBAM liability is likely to be. A well-structured request makes it easy for your supplier to respond with the right information.

For each product, you need the following minimum data: total embedded emissions per tonne of product (kg CO2e per tonne), Scope 1 and Scope 2 emissions stated separately, the production method and energy sources used, electricity consumption during production (MWh per tonne), any carbon price paid in the country of production, and the verification status of the emissions data.

The emissions intensity figure is the most important piece of data. It must be expressed as kg CO2e per tonne of product, covering both precursor emissions and final processing emissions. If your supplier reports in different units, convert carefully. Oremly's data collection portal handles unit conversion automatically, but if you are collecting data manually, double-check every conversion.

Use the following template as a starting point for requesting CBAM data. The key is to be clear about what you need, why you need it, and how the supplier can provide it with minimal effort.

Subject: UK Carbon Border Adjustment — emissions data request for [product name / product code]

Body: Dear [Supplier Name], As part of our compliance with the UK Carbon Border Adjustment Mechanism (CBAM), we need emissions data for the products we import from your facility. This is a government requirement that applies to all UK importers of [steel/aluminium/cement/fertiliser/hydrogen]. Please provide the following for each product: 1) Total embedded emissions (kg CO2e) per tonne of product; 2) Direct emissions (Scope 1) per tonne and indirect emissions (Scope 2) per tonnes separately; 3) The main energy sources used in production and electricity consumption in MWh per tonne; 4) Any carbon price paid under a government scheme in your country; 5) Whether the data has been verified by an independent third party, and if so, please attach the verification report.

You can attach a spreadsheet, PDF, or use our secure supplier portal at [link]. We would appreciate a response within 30 days. If you need help calculating the figures, we can provide guidance. Thank you for your cooperation. Best regards, [Your name]

Suppliers have no legal obligation to provide CBAM data. Many may not understand what you are asking for, or may not have the data readily available. Your strategy should include escalation steps and a fallback plan.

First, send a gentle reminder after 14 days with a simplified request form attached. If no response after 30 days, escalate to a senior contact and explain that without the data, the UK government will apply a default emissions value that is significantly higher, which will increase your costs and may affect your pricing. After 60 days with no response, accept that you will need to use HMRC default values for that supplier, but document your efforts carefully as evidence of reasonable attempts.

Oremly automates this whole process. The system sends initial requests, auto-reminders, and escalation emails on a schedule you set. Suppliers upload data through a no-login portal, and Oremly's AI extraction reads the data from whatever format they provide. If the supplier never responds, Oremly flags the gap and applies defaults with documented evidence of your requests.

Before sending a data request, run through this checklist: Have you identified all covered products for this supplier? Is the request in the supplier's preferred language? Have you confirmed the correct contact person? Is your deadline realistic (minimum 30 days)? Have you provided a response method (email, portal, spreadsheet template)? Have you explained what happens if data is not provided (default values)? Have you attached a simplified one-page data sheet? Are you prepared to handle the data when it arrives?

Successful CBAM data collection is a repeatable process, not a one-off event. You will need fresh data for each reporting period. Establish the cycle, automate where possible, and always have a default fallback plan ready.