CBAM software buyer guide: choose by workflow, evidence and cost

Who needs CBAM software?

Start with the bottleneck and the accountable organisation. Software can organise work and produce outputs, but a supplier's estimate, an adviser's review, accredited verification and an authorised declarant's submission are distinct steps.

• Importers: map goods, installations, data gaps and reporting responsibilities. A small portfolio with a few missing records may need preparation tools before a large reporting suite; recurring supplier coordination or reporting can justify a broader platform.
• Exporters and suppliers: evaluate installation-level data capture, production routes, precursor inputs and controlled sharing with multiple customers. Ask whether each customer needs its own account and whether sharing carries a fee.
• Customs brokers: separate customs/import-record handling from emissions evidence and the agreed representation or filing role. Ask which customer and entity permissions the software actually supports.
• Advisers: evaluate client separation, review history, evidence portability and the ability to explain assumptions. An adviser-facing landing page is not proof of client-isolated tenancy or a licence to file for clients.

What types of solutions can buyers choose?

These categories overlap. Ask a vendor to identify the purchased deliverable, not simply claim an end-to-end platform. The same supplier record can move through several tools without making those tools interchangeable.

• Regulatory intelligence and preparation tools: source-linked updates, scope checks, planning assumptions, evidence organisation and review packs. Useful before filing, without implying a declaration service.
• Supplier-data coordination platforms: requests, reminders, permissions and data exchange across suppliers and installations. Value depends on supplier participation and usable evidence, not just invitations sent.
• Reporting and declaration software: data mapping, supported report versions and exports or submission workflows. Distinguish a downloadable file, portal upload, direct integration and an outsourced filing service.
• Emissions accounting and calculation platforms: installation activity, production routes, precursor treatment and documented methods. A company-wide carbon footprint or generic factor is not automatically a usable CBAM dataset.
• Managed or expert-assisted services: onboarding, data review, calculations or filing assistance supplied by people. Specify the service contract and responsibility; software access alone does not establish professional advice or accredited verification.

What should a buyer evaluate before a demo?

Write a one-page requirements brief for your own workflow. For each criterion, ask the vendor to show a representative output and state what is included in the quoted package. Keep an unconfirmed capability as an open question, rather than marking it absent.

• Relevant functionality and period: name the goods, installations, reporting period and output version. Separate currently orderable functions from a roadmap, transitional screens and optional modules.
• Supplier participation: who enters data, which accounts are needed, what happens when a supplier does not respond, and who pays for access? Test a missing-data case alongside a complete example.
• Provenance and evidence: retain the source record, unit, period, method, assumptions, reviewer and revision history. Ask whether an export preserves these references and makes missing or superseded evidence visible.
• Forecasting: distinguish planning scenarios, default values and supplier actuals. Request source versions, effective dates, calculation boundaries and a reproducible explanation of changes between runs.
• Reporting and export: inspect a sample in the purchased format. Ask who reviews it, what remains to upload or submit, how errors are corrected and which party is accountable for the final filing.
• Roles and organisations: confirm entity limits, client separation, seats, permissions and supplier/customer relationships. Demonstrate the required role rather than assuming a multi-company label covers it.
• Pricing and onboarding: compare currency, billing period, entities, tonnage, suppliers, seats, support, setup and integration costs. Confirm taxes, renewals, overages and any supplier-side licence requirements.
• Ownership and portability: ask who owns uploaded records, what can be exported with its evidence/history, and what happens at termination. Confirm retention, deletion, hosting and data-processing terms in the contract.
• Availability and limits: obtain a written list of live functions, excluded deliverables and service dependencies. A demo, educational article or trial is not proof of production availability for your contract.

What questions should go into the buying checklist?

Use the same small, synthetic example in every permitted demo: one organisation, a goods row, an identified installation, a missing supplier field and a revised evidence record. Stay within the vendor's trial terms and avoid sharing real customer data. This is a suggested buyer exercise; CBAM Pulse has not run these vendor demos.

• Can you show the exact purchased workflow from the original import or installation record to its reviewable output, including a missing-data case?
• Which steps are available now, which need another module or human service, and which are still upcoming?
• What must suppliers do, can they share data with more than one customer, and what do they or we pay?
• Can we see the source, units, method and version behind an emissions or forecast value, and explain a changed result?
• Which report period and output schema are supported? Who performs the final review, upload or submission?
• Who provides professional advice or accredited verification if needed, and what separate engagement or evidence establishes that role?
• What is the full annual cost for our entities, suppliers, tonnage and users, including onboarding, integrations and support?
• Can we export the underlying data, evidence references and revision history, and what happens when the contract ends?

Where does CBAM Pulse fit?

CBAM Pulse is an intelligence, preparation and monitoring workspace. Public goods, threshold and cost-planning tools sit alongside source-linked guides, certificate-price context and reviewed updates. The signed-in workspace organises profiles, supplier requests and follow-up history, metadata-only evidence references, open gaps and a copyable or browser-printable Preparation Pack.

In-app watchlist matching helps users find relevant human-published updates. It is not an automated source watcher or live email-alert service. Supplier requests remain a preparation workflow rather than automatic supplier outreach; evidence references are not hosted document uploads.

CBAM Pulse does not generate or submit CBAM declarations, integrate with the Registry, provide accredited verification or replace professional advisers. Its preparation output does not establish legal sufficiency or readiness for filing.

Use the free tools to identify the next question, then decide whether preparation, supplier coordination, emissions calculation, reporting software or a contracted expert is the missing layer. Review the public workspace tour before creating an account; access and evaluation terms are separate from this comparison.

How was this guide researched?

The original six-vendor research brief was a discovery sample, not a complete market directory. Five vendors with a CBAM offer advertised on the checked public pages appear in the active comparison. This inclusion does not independently establish operational availability. Public product, pricing and service pages were checked on 16 October 2026; no logins, purchases, trials or customer-outcome tests were performed.

Coolset remains a historical research lead. The former CBAM URL redirects to the homepage; current public plans and educational Academy pages did not establish an active CBAM software offer. This does not establish discontinuation.

An advertised function, an upcoming function, an expert service and an unconfirmed capability are kept separate. Vendor data review is not proof of accreditation. Vendor regulatory explanations are not the authority for legal requirements. Reconfirm volatile claims and contractual terms directly before purchasing.

The checked date records this research snapshot; vendor pages can change. Use the linked sources to review the current offer, and use the contact page to flag a factual attribution error with its source and date.