CountEmissionsEU is now in force: what it means for shippers, forwarders, and carriers
On 1 June 2026, Regulation (EU) 2026/1030, known as CountEmissionsEU, entered into force. It is the EU's first harmonised methodology for calculating greenhouse gas emissions from freight and passenger transport, across every mode, door-to-door, aligned with EN ISO 14083:2023.
That headline is easy to misread in two opposite directions: either "nothing happens yet, ignore it," or "this is mandatory now." Neither is right. Here is what actually changes, for whom, and when, and why the standard this regulation just wrote into EU law is the same one CO2Path was already built on.
Two dates, not one
1 June 2026: entry into force. The regulation legally exists, as the European Commission's own announcement confirms. Right now, it applies to companies that voluntarily disclose transport emissions, giving them one methodology to use instead of a patchwork of internal, national, or vendor-specific approaches.
2 December 2030: general application. This is when the substantive obligations actually become enforceable for everyone in scope. Between now and then, the Commission and the European Environment Agency are building the supporting infrastructure: two EU-level reference databases (default emission intensities and transport energy-carrier emission factors, due 2028–2029) and a free calculation tool with a manual, aimed at micro, small, and medium operators, due around 2030.
The gap between those two dates is where most of the confusion sits. It's also where the real exposure already starts.
The part that matters before 2030
General application isn't triggered by company size. It's triggered by disclosure. Once the substantive obligations apply, one voluntary emissions claim in one tender is enough to bring that specific disclosure into scope of the regulation's methodology and labelling requirements. Once triggered, that disclosure has to carry a specific line: "Greenhouse gas emissions calculated in accordance with Regulation (EU) 2026/1030."
Put plainly: the companies already making emissions claims today, whether in RFPs, sustainability reports, or customer pitches, are the ones building the track record that this regulation will eventually hold them to. Waiting for 2030 to start thinking about methodology means retrofitting years of disclosures after the fact.
What it means for shippers
A shipper's Scope 3 disclosure obligation under CSRD doesn't wait for 2030. It's a current-year problem, and it's exactly the kind of voluntary disclosure that CountEmissionsEU is built to standardise. The regulation's promise to shippers is comparability: emissions figures from different carriers and forwarders, calculated the same way, that can actually be benchmarked against each other for procurement decisions. The European Shippers Council has welcomed exactly this framing, pointing to benchmarking and low-carbon procurement as the direct payoff for shippers. The practical gap between now and that promise is getting every partner in the chain onto that same methodology before the comparison is asked for.
What it means for forwarders
A forwarder sits in the middle of exactly this handoff, and CountEmissionsEU raises the stakes on a problem this space already has: reconciling whatever each carrier in a multi-leg shipment can actually produce. A regulation that specifies one methodology doesn't remove the reconciliation work by itself. It just makes inconsistency between carriers a compliance question instead of only an operational annoyance, a shift that CLECAT's own coverage of the legislative process has been tracking closely on behalf of the forwarding sector. Forwarders who get ahead of this now are the ones who won't be caught reformatting five years of records once general application lands.
What it means for carriers
Carriers get the sharpest end of two provisions. First, the regulation prefers primary data over secondary defaults: actual fuel, route, and load data instead of regional averages. It also allows Member States to mandate primary data for large domestic operators (smaller carriers, cross-border operations, and transit movements are excluded from that specific mandate). Second, once a carrier's figure is used in a customer disclosure, it may need to carry the regulation's compliance label. That means the methodology behind it needs to be defensible, not just plausible.
Both provisions point the same direction: a carrier calculating under ISO 14083 now, with primary data captured once and reused across every customer relationship, is simply years ahead of a carrier that waits for a mandate to force the change. IRU has already welcomed the regulation as "the foundation for technology-neutral policymaking, fair competition and credible measured progress towards decarbonisation," while pushing for practical guidance so it doesn't become an administrative burden: precisely the tension smaller carriers are weighing right now.
How CO2Path helps
CO2Path was built on ISO 14083 and the GLEC Framework from the start. That wasn't in response to this regulation, but the regulation now confirms the direction was right. Every CO2Path calculation is shipment-level, carries its methodology reference and data quality tier attached, and distinguishes primary from default data by design. That means:
- Shippers get figures that are already comparable across carriers and forwarders, without waiting for a Commission database to standardise the inputs.
- Forwarders get outputs structured well enough to pass through without reconciling formats leg by leg.
- Carriers get a calculation that's reusable across every customer relationship: collect the primary data once, and it answers this year's tender question and the 2030 compliance question with the same number.
Knowing what CountEmissionsEU requires and actually implementing it are two different problems, the same gap that shows up whenever a standard becomes law. For logistics service providers of every kind, forwarders coordinating multiple carriers, carriers running mixed fleets, smaller operators without an internal data team, the practical barriers are usually the same three: getting transport activity data into a consistent structure, running that calculation as part of the daily workflow rather than retrofitting it at report time, and producing an output that's actually exportable into a customer's disclosure or a tender response. CO2Path handles all three by design, so an LSP doesn't need to build that infrastructure just to meet a regulation that was only ever asking for the methodology to be right.
None of this requires waiting for the free Commission tool or the EU reference databases due later this decade. The methodology they'll be built around is already the one CO2Path runs on today. We're continuing to track how the regulation's remaining detail lands, so CO2Path keeps pace with it rather than needing to catch up later.
See how CO2Path already produces CountEmissionsEU-aligned records → Request a demo
If you're a logistics service provider working through what CountEmissionsEU means for your operations, whatever your size or seat in the chain, we want to hear from you → Get in touch
Sources: EUR-Lex, Regulation (EU) 2026/1030; European Commission, DG MOVE; IRU.
Frequently asked questions
Yes. Regulation (EU) 2026/1030 entered into force on 1 June 2026. What's not yet in force is general application: the point at which its obligations become enforceable for everyone in scope, which is set for 2 December 2030.
Because the trigger for scope isn't a date, it's a disclosure. Once general application begins, any voluntary emissions claim already made, whether in a tender, a report, or a customer pitch, can bring that disclosure into scope. Companies making claims today are setting the track record the regulation will eventually measure against.
No. It establishes a preference for primary data over secondary/default values, and allows individual Member States to mandate primary data specifically for large domestic operators. SMEs, cross-border operations, and transit movements are excluded from that mandatory requirement, and secondary/default data remains available where primary data isn't practical.
The Commission is required to publish a free calculation tool and manual, aimed at micro, small, and medium transport operators, expected around 2030 alongside two reference databases (default emission intensities and energy-carrier emission factors). It's a support mechanism for operators without existing tooling. It isn't a reason to delay adopting ISO 14083-aligned methodology now, since the tool itself will be built around that same standard.
Once a disclosure falls within scope, it's expected to carry the line "Greenhouse gas emissions calculated in accordance with Regulation (EU) 2026/1030." That label is only credible if the methodology behind the figure actually holds up, which is a stronger reason to get the calculation right now than to add a label to an uncertain number later.
It isn't, in substance. CO2Path's shipment-level, ISO 14083/GLEC-aligned calculation approach was built before this regulation existed. CountEmissionsEU is the EU formally adopting the same methodology as law: validation of the approach, not a reason to change it.