If you have read anything about CountEmissionsEU, you will have run into an acronym the regulation cites but never explains: EN ISO 14083:2023. It is the standard that defines how greenhouse gas emissions from transport operations are calculated, and it has become the mandatory European reference for anyone who chooses to declare those numbers.
The trouble is that almost everything written about ISO 14083 is aimed at ESG consultants, not at someone with forty vehicles in the yard. Let us tell it from the other side.
Where it comes from
ISO 14083 was published in March 2023. It did not appear from nowhere: it is the formalisation of the GLEC Framework, the standard developed by the Smart Freight Centre that part of the industry had already been using voluntarily for years.
The difference between the two is one of status more than content. The GLEC Framework remains the working tool — the one with the tables, the factors and the instructions for applying the methodology to daily operations. ISO 14083 is the technical standard that gives it formal weight and makes it citable in a contract or a tender document.
Before, there was good practice. Now, there is a standard.
What it actually covers
The full title refers to “transport chain operations”, and every word carries weight.
Chain, not leg. The boundary is the whole service from origin to destination, not the portion you handle. If goods pass through a warehouse, are transhipped and completed by another carrier, the calculation covers all of it.
Operations, not just vehicles. Hubs are inside the boundary too: warehouses, terminals, transhipment points. Energy consumed by a distribution centre is part of the transport chain, not a separate line.
Multimodal. Road, rail, sea, air and combinations of them. Irrelevant if you only do road distribution, but it explains why the standard is more complex than you strictly need.
The unit of measure that changes habits
Here is the first practical hurdle. ISO 14083 does not think in kilograms of CO₂ per kilometre, but in grams of CO₂ equivalent per tonne-kilometre (g CO₂e/tkm).
The difference is not cosmetic. It means load enters the calculation: a hundred kilometres with a full vehicle and a hundred kilometres with a half-empty one produce roughly the same absolute emissions but a very different emissions intensity. And intensity is the number a customer compares across suppliers.
The operational consequence is counter-intuitive but important: filling your vehicles improves your figure even if you drive the same kilometres. This is the point where calculation methodology and operational efficiency stop being separate conversations — and, not coincidentally, load factor is also one of the biggest levers on real cost per kilometre.
Primary and secondary data: the distinction that matters
If you take away one thing about ISO 14083, this is the one.
The standard distinguishes two ways of feeding the calculation.
Primary data is measured on the actual operation: the litres that vehicle actually burned on that trip, the actual load, the actual distance. It is data you only have if something records it while it happens.
Secondary data is default values: average consumption by vehicle type, assumed load factor, estimated distance. It is permitted, and for many SMEs it remains the only workable starting point.
The standard does not forbid secondary data. But it sets a clear hierarchy — primary is preferred wherever it is available — and it requires the quality of the data to be declared. In other words: you may use averages, but you have to state that you are using averages.
And this is where real competitive distance opens up. Two suppliers presenting the same number are not presenting the same thing, if one measured it and the other estimated it. The moment a customer has to put those numbers into their own report and defend them to an auditor, the difference stops being theoretical.
Why telematics changes the game
Fuel consumption is the heaviest single item in any road transport emissions calculation. Everything else is trimming.
The way most companies know that figure today is the supplier invoice: a monthly total, aggregated across the whole fleet. There is no way back from that. You cannot know how much the vehicle serving that customer on that round consumed, because the information never existed in that form.
A device connected to the vehicle’s diagnostic port solves the problem at the root, because it reads consumption from the vehicle instead of inferring it. Alongside consumption come actual distance, stops and driving style — which are, incidentally, the same data you need to see where fuel is being wasted.
This is why aligning with ISO 14083 is rarely a standalone project: anyone who already has telematics for efficiency reasons finds the primary data already in hand. Anyone who does not has to build the measurement infrastructure — and at that point it may as well pay for itself in fuel too. We looked at the numbers in the article on the ROI of route optimisation software.
The subcontracted boundary
The most awkward part, and the one no purchase solves.
If a share of your transport goes to third-party hauliers, those trips stay inside the boundary of the service you sell your customer. The data has to be collected there too, and that depends on parties you do not control and who often have no measurement infrastructure at all.
There are three workable routes, in decreasing order of robustness: ask the haulier for primary data, if they have it; reconstruct it from the trip data you hold anyway (origin, destination, weight, vehicle type); or use default values and declare them as such.
None of the three is quick. Which is why it is worth opening the file before the request arrives, not after.
Four things to do, in order
One. Look at how you know your fuel figures today. If the answer is “from the invoices”, that is the bottleneck and it comes before everything else.
Two. Check whether you have actual distance or only planned distance. The gap between the two is almost always in double digits, and all of it lands in the final number.
Three. Work out how much of your transport is subcontracted. That is the long part: start it now.
Four. Only then choose who produces the report. It is the last step, not the first, because without the previous three the reporting software receives estimates and returns estimates.
An honest clarification
ISO 14083 is a calculation methodology, not a piece of software. No tool “is ISO 14083” in the way a vehicle is Euro 6: conformity is about how data is turned into a number, and how that is verified.
Optivo does not certify ISO 14083 conformity and does not issue the report. It does the upstream part: measuring real consumption, distance and trips vehicle by vehicle — the primary data the standard prefers, and which no methodology can manufacture if it was never collected. If you are working out how to hold measurement and reporting together, we cover it on the sustainable logistics page.
FAQ
Is ISO 14083 mandatory?
The standard itself is voluntary, as all ISO standards are. It has become binding indirectly, though: the European CountEmissionsEU regulation, in force since 2 June 2026, establishes that anyone choosing to declare the emissions of a transport service must calculate them under EN ISO 14083:2023. Declaring remains optional; the method does not.
What is the difference between ISO 14083 and the GLEC Framework?
The GLEC Framework, developed by the Smart Freight Centre, is the technical basis ISO 14083 was built on, and it remains the working tool for applying it: it contains tables, emission factors and practical guidance. ISO 14083 is the formal technical standard. In practice they are used together: the standard says what is required, the framework says how to do it.
Can I use averages instead of measuring?
Yes. ISO 14083 permits secondary data — default values by vehicle type and standard factors — and for many SMEs it is the realistic starting point. The standard does set a hierarchy, though: primary data is preferred where available, and the quality of the data used must be declared. A figure based on averages remains valid, but it is openly less robust than a measured one.
Why measure in grams per tonne-kilometre?
Because the unit has to allow comparison across different transport services, and kilometres alone are not enough: moving twenty tonnes a hundred kilometres is not the same as moving two. The tonne-kilometre normalises the figure for load, and it has a useful practical consequence: improving vehicle fill improves your emissions intensity even at the same distance driven.
Are warehouses included?
Yes. ISO 14083 covers transport chain operations, and hubs fall inside the boundary: warehouses, terminals and transhipment points the goods pass through. Energy consumed by these facilities is part of the calculation, not a separate line.
What about trips given to subcontracted hauliers?
They stay inside the boundary of the service you sell your customer, so they have to be included. The options are to ask the haulier for primary data, reconstruct it from the trip data you already hold, or use default values and declare them as such. It is the part of the work that takes longest, because it depends on third parties: it is worth tackling first.