CountEmissionsEU is in force: what it actually means for cargo owners and LSPs

What is CountEmissionsEU, and why now?

CountEmissionsEU establishes the EU's first harmonized methodology for calculating greenhouse gas emissions from freight and passenger transport, across all modes. The reference methodology is EN ISO 14083:2023, the international well-to-wheel (and well-to-wake, for shipping and aviation) standard for quantifying transport chain emissions.

The regulation's own path through the EU legislative process ran for about three years: the Council reached its first-reading position in February 2026, Parliament gave final approval on 28 April 2026, and the text was published in the Official Journal on 12 May 2026 as Regulation (EU) 2026/1030. It entered into force on 1 June 2026 – but per Article 20, general application (when the rules actually bind transport and hub entities, data intermediaries, tool developers, and conformity assessment bodies) starts only on 2 December 2030, 54 months later.

A short list of provisions apply earlier, from entry into force – these obligate the Commission, not the market, to build the EU's two default-value databases (due 2 June 2028 and 2 December 2029), get the free SME calculator ready (by 2 June 2030), and adopt the implementing and delegated acts the system needs, including the certification regime for external calculation tools. The Commission must evaluate the regulation and report to Parliament and Council by 3 December 2034, four years after full application begins.

Crucially, the co-legislators settled on a disclosure-based rather than a universal mandate. Companies will not be required to calculate their transport emissions. But once the regulation applies, the moment they choose to disclose – in a public claim, a contract, or a tender – they will need to use the common methodology and label the disclosure accordingly.

Entry into force vs. application: why the distinction matters

It's a common point of confusion in EU law, and CountEmissionsEU is a clean example of it. “Entry into force” (1 June 2026) is the date a regulation becomes a legally existing act. “Application” (2 December 2030) is the date its rules actually start binding the people and companies it addresses. Between those two dates, only a specifically named set of provisions apply – and every one of them is a Commission rule-making or infrastructure-building power, not a market obligation. That's why the regulation can be accurately described as “in force” today while also being accurate to say no transport or hub entity is yet legally required to use ISO 14083 under CountEmissionsEU specifically.

What actually triggers your CountEmissionsEU duty

Once the regulation reaches general application on 2 December 2030, its duty is disclosure-triggered, not size- or sector-triggered. There's no revenue or employee threshold that determines whether CountEmissionsEU applies to a company, unlike CSRD. Instead, the trigger is behavioral: the moment a transport or hub entity discloses output emissions data – whether required to by another law, agreed to in a contract, or simply chosen as a marketing or procurement claim – that disclosure will need to be calculated per the ISO 14083 methodology and carry the mandatory statement: “Greenhouse gas emissions calculated in accordance with Regulation (EU) 2026/1030.”

Before 2 December 2030, none of this is yet a legal requirement under CountEmissionsEU specifically. That doesn't make disclosures made today risk-free, though: other frameworks a company may already be in scope for – CSRD/ESRS, SBTi's Corporate Net-Zero Standard, or simply a counterparty's own procurement criteria – increasingly reference ISO 14083 or the closely related GLEC Framework independently. A voluntary disclosure made now that can't be reconciled with ISO 14083 is already a claim a counterparty, auditor, or competitor can challenge on those grounds – even before CountEmissionsEU itself has teeth.

For cargo owners: how this interacts with CSRD

For most cargo owners, the primary sustainability reporting duty still comes from CSRD, not CountEmissionsEU. The two regimes are designed to avoid stacking a second, parallel obligation on top of the first. If your transport emissions are reported only in aggregate, as part of your CSRD Scope 3 category disclosure, that disclosure will generally be carved out of CountEmissionsEU's trigger once that trigger takes legal effect in December 2030.

The carve-out has a limit, though. It covers aggregated, CSRD-style disclosure – not every use you make of transport emissions data. Green procurement comparisons, supplier CO₂ scorecards, and lane-level marketing claims are disaggregated by nature, and will fall squarely under CountEmissionsEU's disclosure trigger, mandatory label included, from 2030.

It's also worth rechecking who's actually in CSRD scope. Following the Omnibus simplification, fewer companies are captured than under the original 2023 proposal: broadly, EU companies need to clear both a 1,000-employee and a €450 million turnover threshold, while non-EU groups are assessed on a €450 million/€200 million parent-subsidiary test. Confirming where you land under the revised thresholds should come before any CountEmissionsEU planning. It determines which of your transport disclosures are CSRD-aggregated (and likely carved out) versus standalone (and squarely in scope).

For LSPs: primary data, iLEAP, and the free EU tool

For logistics service providers and carriers, the regulation's center of gravity is the primary-data-priority principle. The agreed text establishes a hierarchy that favors primary data – actual fuel consumption, real load factors, verified carrier inputs – over secondary data such as industry averages, while stopping short of making primary data mandatory across the board.

Member States get a specific lever here, effective from the regulation's 2030 application date: they may require primary data for domestic transport operations carried out by large operators above a national employee threshold. That stricter layer explicitly excludes cross-border operations, transit movements, and SMEs, which can continue relying on secondary data. National authorities can also introduce incentives – administrative, financial, or operational – to encourage primary data use beyond what's mandatory.

To support smaller operators, the European Commission will make a free, simplified calculation tool available, alongside two EU-level default-value databases (for emission intensities and emission factors), developed with the European Environment Agency's technical support. Unlike the market-facing obligations, this is a duty on the Commission that runs now: the calculator has to be ready by 2 June 2030, 48 months after entry into force, and it's designed as a compliance floor for micro, small, and medium-sized transport operators, not a competitive differentiator. Large cargo owner customers and competitive tenders will generally expect more granular, primary-data-backed reporting than the free tool alone provides.

For LSPs already building shipment-level, ISO 14083-aligned data flows, iLEAP – the data-exchange framework developed by Smart Freight Centre and the SINE Foundation – offers a standardized way to deliver that data to customers automatically, rather than assembling a bespoke spreadsheet per client relationship.

Timeline: 2026 to 2030 at a glance

• 2026 (now): Regulation in force since 1 June, but not yet applicable. The Commission's preparatory obligations are running – building the two EU default-value databases (due 2028 and 2029), developing the free SME calculator (due 2030), and adopting the implementing acts needed to make certification and verification workable by 2030. None of the substantive obligations for transport and hub entities – the ISO 14083 mandate, the primary-data hierarchy, the disclosure label – are legally binding yet.

• 2027–2029: Implementing and delegated acts refine technical detail, including certification requirements for external calculation tools (Article 11). The EU default-value databases and free SME calculator are developed. Commercial pressure builds well ahead of the legal deadline, as CSRD-obligated cargo owners push their logistics providers for standardized, auditable data ahead of their own FY2027 filings.

• 2 December 2030: General application. The mandatory disclosure label, primary-data prioritization, and verification duties become legally enforceable for the first time. Companies relying on non-aggregated, disaggregated emissions disclosures need audit-ready, ISO 14083-traceable data and correct labelling in place from this date.

The real question isn't when – it's whether you're ready

CountEmissionsEU won't be in effect until 2030, but the data discipline it demands starts paying off now – in tenders, new contracts, or sustainability claims. The question every leader at an LSP or cargo owner should be asking isn't “when does this apply to us,” but “would our numbers survive an audit today – and will they still in 2030?”

FAQ

Q1: Does CountEmissionsEU require my company to measure its transport emissions?

No – and not yet, in any case. CountEmissionsEU does not create a general obligation to calculate transport emissions; it only applies once a company chooses to disclose transport emissions data, whether voluntarily, contractually, or as part of a tender. That disclosure trigger, along with the ISO 14083 mandate and the mandatory disclosure label, only becomes legally binding once the regulation reaches its general date of application on 2 December 2030 (Article 20). Before that date, the Commission's preparatory obligations – building the default-value databases and the free SME calculator – are running, but no transport or hub entity is yet bound by CountEmissionsEU's substantive rules.

Q2: What's the difference between CSRD and CountEmissionsEU for a cargo owner?

CSRD is a corporate sustainability reporting directive with its own size-based scope (broadly, over 1,000 employees and over €450 million turnover for EU companies, following the Omnibus revision). It requires aggregated Scope 1, 2, and 3 disclosures, including a Scope 3 transport category. CountEmissionsEU is not a reporting directive with a size threshold – it's a methodology regulation triggered by disclosure, applicable from 2 December 2030. In practice, aggregated CSRD transport figures are generally carved out of CountEmissionsEU's trigger, but any disaggregated transport emissions figure a cargo owner discloses outside that aggregated CSRD reporting – in procurement comparisons, supplier scorecards, or marketing claims – falls under CountEmissionsEU.

Q3: When does CountEmissionsEU actually become enforceable?

The regulation entered into force on 1 June 2026 – but entry into force and application are different things in EU law. Under Article 20, general application (when the ISO 14083 mandate, primary-data rules, mandatory disclosure label, and verification/certification duties actually bind transport and hub entities, data intermediaries, tool developers, and conformity assessment bodies) starts only on 2 December 2030. A short list of provisions apply earlier, from entry into force: these obligate the European Commission, not the market, to build the EU's default-value databases (due by 2 June 2028 and 2 December 2029, respectively), get the free SME calculator ready (by 2 June 2030), and adopt the implementing and delegated acts the system needs – including the certification regime for external calculation tools (Article 11).

Q4: Do small transport operators need to use primary data under CountEmissionsEU?

Not by default – and not yet in any case, since the primary-data hierarchy set out in Article 4 only becomes legally binding at the regulation's general application date, 2 December 2030. From that date, the rule favors primary data over secondary data (such as default emission factors) but doesn't make primary data mandatory for everyone. Member States may require primary data specifically for large domestic operators above a national employee threshold operating purely domestic services – a stricter layer that explicitly excludes cross-border operations, transit movements, and SMEs. In the meantime, the European Commission is already required to build a free calculation tool and default-value databases aimed specifically at micro, small, and medium-sized transport operators.

Q5: What is iLEAP, and how does it relate to CountEmissionsEU?

iLEAP is a data-exchange framework developed by Smart Freight Centre and the SINE Foundation, with WBCSD's PACT initiative as a supporting partner. It's designed to let logistics companies exchange shipment-level, ISO 14083-aligned emissions data in a standardized, machine-readable way. It isn't part of the CountEmissionsEU regulation itself, but it addresses the same underlying methodology (ISO 14083) and offers LSPs a practical way to deliver audit-ready, primary-data-backed figures to customers automatically, rather than building bespoke reporting for each client relationship.

Q6: What's the difference between CountEmissionsEU's “entry into force” and its “application” date?

“Entry into force” is the date an EU regulation becomes a legally existing act – for CountEmissionsEU, that was 1 June 2026, twenty days after publication in the Official Journal. “Application” is the date its rules actually start binding the people and companies it addresses. Article 20 of the regulation sets 2 December 2030 as that general application date for transport and hub entities, data intermediaries, calculation-tool developers, and conformity assessment bodies. A short, specifically listed set of provisions – mostly ones empowering the European Commission to build databases, a free calculator, and implementing rules – apply from entry into force instead, so that infrastructure is ready before the rest of the regulation switches on in 2030.