For your role

CBAM Pulse for SME importers

CBAM (Carbon Border Adjustment Mechanism) workflow for SME importers: identify goods, track annual mass, request supplier data, and escalate gaps; not legal, tax, or customs advice.

Last updated: 2026-08-11 · Sources: Regulation (EU) 2023/956 (consolidated text) · Regulation (EU) 2025/2083 · EC DG TAXUD — Carbon Border Adjustment Mechanism · Commission Implementing Regulation (EU) 2025/2547 — emissions calculation · Commission Implementing Regulation (EU) 2025/2546 — verification

Who this is for

Small and mid-sized EU importers who are new to CBAM and want a clear, practical starting point without a dedicated trade or customs team behind them.

First questions to answer

• Do the goods I import fall within CBAM scope?
• Could the 50-tonne de-minimis threshold keep my imports outside the main obligations?
• Which 2026–2027 dates and readiness steps apply to me?

Recommended starting path

1. 1. Check your goods

   Look up a CN code to see whether it is in scope and which sector it sits in.

2. 2. Check the threshold

   See whether your cumulative annual net mass could fall under the 50-tonne de-minimis exemption.

3. 3. See the dates

   Put the key 2026–2027 CBAM dates on your calendar, each with its source.

4. 4. Work the checklist

   Walk through the practical preparation areas at your own pace.

Choose one owner and one backup

A smaller importer does not need a large CBAM team. It needs one named owner, one backup, access to the customs and purchasing facts, and a clear list of questions that require a broker, adviser, verifier, or National Competent Authority.

Choose the person who can coordinate imports, supplier contact, and finance, even if CBAM is only part of their role. Record a backup so the file does not disappear when that person is away. Give the owner permission to request customs extracts, contact the purchasing owner, and open external questions. Write a one-page responsibility note: who provides the CN codes and net mass, who contacts suppliers, who reviews cost planning, and who approves escalation. The owner manages the process; they do not become a customs classifier or emissions specialist.

Keep the operating setup deliberately small. Use one controlled register, one folder or approved reference system, one open-action list, and one recurring review slot. Avoid buying complexity before the goods population and supplier problem are understood. CBAM Pulse's free tools can support initial screening, threshold context, dates, supplier-request drafting, and evidence organisation. The authenticated workspace can organise continuing preparation, but it does not remove the need for human ownership or the importer's normal records and review channels.

• Owner keeps the register current, coordinates requests, records gaps, and schedules reviews.
• Backup can find the source data, understand statuses, and continue urgent follow-up.
• External route covers classification, interpretation, actual-emissions verification, and authority questions.

Build the minimum viable import register

For a small goods population, a compact register is enough if every row has traceable customs facts, supplier context, review status, and a next action. Simplicity should remove duplication, not provenance.

Start with the imports for the relevant calendar year. Record the importing legal entity, declaration or shipment reference, import date or period, CN code used, plain product description, supplier, origin, and net mass. Add the invoice, purchase order, or internal SKU only to help locate the transaction. If the customs broker supplies an extract, preserve the original and note when it was received. Do not rebuild quantities from invoices if a customs source is available without first reconciling the difference.

Give each row a small set of states: scope screening not started, current-scope match, no current-scope match, code needs review, threshold context to update, supplier request needed, evidence received, clarification needed, or external review needed. One row can carry more than one open action, so avoid a single green status. Keep proposal-stage products in a separate watch note and never treat a proposal as adopted current scope. A goods lookup supports screening of a known code; it does not choose or confirm the code.

• Required facts: entity, period, customs reference, CN code, description, supplier, origin, and net mass.
• Required control: source, received date, owner, review status, next action, and target date.
• Optional enrichment: purchasing reference, sector, supplier contact, evidence reference, and planning note.

Check scope and annual threshold context in the right order

First identify whether the known CN codes match current CBAM scope. Then review the applicable annual threshold context across the importing entity's relevant goods. A small company is not outside scope simply because it is small.

Run the scope screen on the code used in the customs record and keep the tool's source date with the result. If the code is missing, incomplete, or disputed, ask the customs broker or appropriate adviser through the normal classification route before relying on the lookup. Do not screen only the largest purchase or the product name. Include the full relevant import population for the entity and year so occasional or low-value shipments are not overlooked. Keep excluded or cancelled declarations documented rather than deleting them without an explanation.

After current-scope rows are identified, use the source-linked threshold checker to organise cumulative annual net-mass context and note any categories the tool treats separately under the current rules. Update the total when new imports arrive. The result is a preparation indicator based on the user's inputs, not an official determination. If the business is close to a boundary, has unusual customs procedures, imports through several entities, or cannot reconcile the mass, escalate early instead of stretching the spreadsheet until it gives the desired answer.

• Scope question uses the known customs code and the reviewed current goods list.
• Threshold question uses the relevant annual mass for the importing entity and the current source-linked rules.
• Escalation question states the facts, missing information, source checked, and exact decision needed.

Send a focused supplier request and keep the history

Small importers can reduce supplier effort by sending one clear request tied to recognisable goods, then recording partial answers and missing fields instead of launching a broad carbon-data project.

Identify the highest-priority in-scope goods with missing data and ask the existing purchasing contact to introduce the right supplier person. Include the product, purchase reference, import year, known CN code and review status, and the producing site if known. Ask for the operator and installation, production route, reporting period, direct and indirect emissions information where relevant, data basis, method or monitoring references, precursor context where relevant, supporting evidence references, and a follow-up contact. Review the wording before sending it from the company's own email.

Keep a short request log with sent date, contact, goods covered, fields requested, response date, missing items, next follow-up, and owner. Treat a partial response as progress, not failure, but do not mark the row complete. A supplier spreadsheet remains supplier-reported until the relevant basis and verification context are reviewed. The public CBAM Pulse template builds a fixed copy-and-paste draft in the browser; it does not send the email, keep the draft, collect files, assess the response, or verify the supplier's emissions.

• Ask once with enough product and installation context for the supplier to identify the right record.
• Chase only the missing or conflicting fields and preserve the original response and revisions.
• Escalate strategic non-response through procurement, management, or an adviser rather than inventing replacement data.

Keep a simple evidence and gap folder

An SME evidence set can be modest: a register, source references, supplier replies, calculation or monitoring references, planning assumptions, and an open-questions log. The control is the index, not the volume of documents.

Give every evidence item a reference that can be found again. Record the file name, email subject, link, provider, received date, version, reporting period, goods or supplier row, and what it appears to support. Keep files in the company's approved storage and use CBAM Pulse for metadata references where appropriate; do not assume the software stores the underlying document. If a supplier sends a revised file, keep the earlier version and note which value changed. If an attachment cannot be opened or understood, list that as a gap rather than a received-evidence success.

Maintain one open-question log. Use plain labels such as missing code confirmation, mass not reconciled, supplier not identified, installation unknown, emissions basis unclear, evidence reference missing, adviser question, verifier question, or NCA question. Rank actions by practical dependency: a missing code may block the scope screen, while a missing installation may block a useful supplier-data review. Give each gap an owner and next date. Working through the list is preparation only; a zero-gap view would not itself prove completeness, verification, or acceptance.

• Index says where the record is, who supplied it, which version and period it covers, and why it matters.
• Gap log says what is missing, which goods are affected, who owns it, and what happens next.
• Review note says whether the item was only recorded, checked internally, or sent to a qualified reviewer.

Escalate when the question exceeds the small workflow

A minimal process is effective only when it knows when to stop. Escalate disputed classification, unusual customs treatment, unclear entity boundaries, unresolved data methods, actual-emissions verification, or authority interpretation to the appropriate qualified or official route.

Prepare the escalation before paying for review time. State the importing entity, goods and code used, import period, affected entries, supplier and origin, source already checked, records available, conflicting facts, and the exact question. Separate several questions if they need different actors. The customs broker or classification specialist may address code provenance; an adviser may analyse a situation within an engagement; an accredited verifier handles independent verification where applicable; the National Competent Authority handles official questions within its remit.

Do not ask software to bridge a missing decision. A tool can screen a code, total user-entered mass, calculate a scenario from displayed assumptions, or organise an evidence reference. It cannot resolve a customs dispute, select an emissions method, confirm a supplier's data, grant an exemption, provide a verification opinion, or speak for an authority. A concise, well-evidenced escalation often saves more time than another internal spreadsheet version because the reviewer receives the facts and the unresolved boundary together.

• Escalate immediately when the operating team lacks the decision authority or specialist competence.
• Escalate after one controlled follow-up when a material supplier gap cannot be resolved internally.
• Escalate with a question pack, not a folder dump: facts, source, evidence, conflict, affected rows, and requested decision.

Use a lightweight month-end and year-end routine

The SME routine can fit into existing bookkeeping or import reviews: update new rows, reconcile mass, follow suppliers, refresh source-linked assumptions, and carry unresolved questions forward with owners.

At each chosen review point, add new customs entries, confirm amendments or cancellations, update the cumulative mass context, screen new codes, and open supplier actions for new goods. Review requests awaiting response and evidence that needs clarification. Check whether an official source used by a tool or planning note has changed, but do not rewrite current operations from a proposal announcement. Record the review date even when nothing changed. A regular no-change record is more useful than an undated spreadsheet that may or may not be current.

At year end, reconcile the register to the customs source, freeze a dated copy, list the supplier-data and evidence status for each relevant row, version the planning assumptions, and prepare the unresolved-question pack for review. Keep the output proportional; a smaller importer may have only a few pages and references. CBAM Pulse does not turn that pack into an official declaration, connect it to the CBAM Registry, confirm an exemption, verify actual emissions, or approve the business. It gives the owner a clearer preparation trail for the next human or official step.

• Recurring: new imports, code changes, cumulative mass, supplier requests, evidence, source dates, and gaps.
• Year-end: customs reconciliation, frozen register, supplier status, evidence index, assumptions, and escalation list.
• Boundary note: preparation completed to a stated date; no software filing, verification, advice, or authority decision.

Questions sme importers ask about CBAM