CountEmissionsEU: What Shippers Need from Their TMS to Comply
If you ship goods across Europe, there’s a regulation heading your way that deserves a spot on your radar. It’s called CountEmissionsEU, and while it might not sound as dramatic as a tariff war or a canal blockage, it’s going to fundamentally change how transport emissions are measured, reported, and compared across the continent.
The good news? If you’re already working with a decent TMS, you’re in a better position than you think.
What you’ll learn:
- What is CountEmissionsEU?
- Who does it apply to?
- What does it actually require?
- The CSRD connection: why this matters right now
- What this means for your TMS
- Five things you can do today
What is CountEmissionsEU?
CountEmissionsEU is an EU regulation that introduces a single, harmonised methodology for calculating greenhouse gas (GHG) emissions from transport services. It covers all modes — road, rail, air, sea, and inland waterways — for both freight and passenger transport.
Why does this matter? Because right now, everyone measures transport emissions differently. One carrier reports well-to-wheel numbers, another only counts tank-to-wheel. One shipper uses distance-based estimates, another relies on actual fuel consumption data. The result is a mess: numbers that look different even when the underlying transport is identical.
Good luck comparing carrier sustainability performance with that kind of inconsistency.
CountEmissionsEU solves this by mandating EN ISO 14083:2023 as the common standard. Once it applies, everyone — carriers, shippers, freight forwarders — will use the same methodology. Finally, an apples-to-apples comparison. For a detailed legislative overview, see the European Parliament Research Service briefing.
The European Council and Parliament reached political agreement on CountEmissionsEU in November 2025. Formal adoption is expected in the first half of 2026, with the main obligations applying approximately 48 months after entry into force — roughly around 2030.
Four years might sound comfortable, but if you’ve ever tried to roll out a new data process across your entire carrier portfolio, you know how quickly that time evaporates.
Who does it apply to?
CountEmissionsEU uses what the EU calls a “binding opt-in” model. Here’s what that means in plain language:
- Transport service providers (carriers, freight forwarders, 3PLs) who choose to share emissions data with their customers must use the harmonised ISO 14083 methodology. No cherry-picking a more flattering calculation method.
- Shippers aren’t directly forced to request emissions data. But when they do — or when it’s needed for CSRD sustainability reporting — the data must follow the same standard.
- The regulation covers all transport modes within the EU: road freight, parcel, express, rail, maritime, air cargo, and inland waterways.
The practical implication? The moment emissions data enters your supply chain — whether you’re sharing it, receiving it, or reporting on it — it needs to be CountEmissionsEU-compliant.
What does it actually require?
The regulation doesn’t just say “calculate your emissions.” It prescribes how:
-
Well-to-wheel scope — Emissions must cover the full energy chain, from fuel extraction and production through to combustion. No more hiding behind tank-to-wheel numbers that conveniently leave out upstream emissions.
-
Standardised allocation — When a carrier transports goods from multiple shippers on the same vehicle (the norm for LTL and parcel), the emissions must be allocated to each shipper using defined rules based on weight, volume, or tonne-kilometres.
-
Data quality hierarchy — The regulation favours primary data (actual fuel consumption, actual distances) over default values and estimates. Companies using real operational data will produce more accurate — and probably more favourable — numbers.
-
Transparency — When emissions data is shared, it must include information about the methodology, data sources, and quality level used. No more black-box numbers that nobody can verify.
The CSRD connection: why this matters right now
Here’s where it gets practical. If your company falls under the Corporate Sustainability Reporting Directive (CSRD), you’re already required to report on Scope 3 emissions — and that includes the emissions from your transport activities, both upstream and downstream.
The problem? Getting reliable transport emissions data has been a nightmare. You ask your carriers, and each one uses a different calculation method. Some can’t provide numbers at all. Your Scope 3 transport figures end up being a patchwork of estimates, defaults, and carrier-specific calculations that simply don’t add up.
CountEmissionsEU directly addresses this by creating a standardised data pipeline: carrier to shipper to sustainability report, all using the same methodology. Your CSRD Scope 3 reporting for transport becomes dramatically more reliable and — crucially — auditable.
Even though CountEmissionsEU’s main obligations won’t apply until around 2030, CSRD reporting is already mandatory. Companies that get ahead of this will have better data, better reports, and a genuine basis for optimising their transport footprint.
What this means for your TMS
This is where it all comes together. Your TMS already captures most of the data you’ll need for CountEmissionsEU compliance:
- Shipment details — origin, destination, weight, volume, dimensions
- Carrier and service data — which carrier moved what, on which route, using which mode
- Operational data — distances, transit times, and increasingly, fuel consumption or emissions data returned by carriers via API
A well-integrated TMS becomes the central hub for emissions data. Instead of chasing carriers for quarterly emissions reports, the data flows in alongside the tracking updates and proof-of-delivery confirmations you’re already receiving.
Here are five capabilities to look for in your TMS — or to ask your TMS provider about:
- Carrier emissions data ingestion — Can the TMS receive and store emissions data from carriers through existing API integrations?
- ISO 14083 calculation support — Can the system calculate or validate emissions using the EN ISO 14083 methodology?
- Allocation logic — For shared transport (LTL, groupage, parcel), can the TMS allocate emissions to individual shipments using the correct parameters?
- Reporting and export — Can you extract emissions data per shipment, carrier, lane, or time period in a format that feeds your CSRD reporting?
- Data quality tracking — Does the system distinguish between primary data (actual consumption) and secondary data (default values), so you can measure and improve data quality over time?
Five things you can do today
You don’t need to wait for the formal deadlines to start preparing:
-
Audit your current emissions data — What transport emissions data are you collecting today? How is it calculated? Map the gaps between your current approach and the ISO 14083 standard.
-
Talk to your carriers — Ask about their emissions reporting capabilities. Are they preparing for CountEmissionsEU? Carriers investing in this now will be better partners down the line.
-
Evaluate your TMS — Does your current system support emissions data collection and reporting? If not, get it on the roadmap — or factor it into your next TMS evaluation.
-
Align with your CSRD team — If you’re subject to CSRD reporting, make sure your transport emissions data strategy connects to your broader sustainability reporting. These shouldn’t be separate workstreams.
-
Start with what you have — Even before the regulation applies, using consistent emissions calculations across your carrier portfolio gives you a genuine basis for comparing and optimising your transport footprint. The regulation provides the push, but the business value exists regardless.
The companies that treat CountEmissionsEU as a strategic opportunity — rather than just another box to tick — will be the ones that turn sustainability data into a real competitive advantage. Your TMS is where that starts.
- FedEx API Migration: What Shippers and Software Providers Need to Do Before June 2026
Prev
Next