The European logistics and sustainability community understands ISO 14083, the international standard for freight emissions, well. Sustainability teams at major logistics operators have read it. However, the gap between knowing the standard and operating under it is significant. For most organisations, it is wider than they expected.
This is not a knowledge problem. It is an implementation problem, and it appears as three specific barriers. In practice, the organisations that are closest to compliance are often the organisations that discovered the implementation gap first. They are not necessarily the organisations that studied the standard most carefully.
What the infrastructure gap looks like in practice
A sustainability manager at a freight forwarder or carrier receives a data request from a shipper customer. The customer is preparing for an assurance review of its Scope 3 Category 4 data under CSRD, the EU sustainability reporting law.
Without the right infrastructure: the manager collects PDFs from carriers in many different formats and retypes the numbers by hand. The methodology is undocumented, the chain of custody is broken, and the data quality is unclear. As a result, the auditor reports a material finding, which is a serious problem, in the assurance review of the customer.
With the right infrastructure: the manager exports shipment-level records from the calculation platform. Each record contains the input data, the ISO 14083 methodology that was applied and the version of the emission factor. It also contains an audit trail back to the original calculation, and nobody can edit this trail afterwards without leaving a trace. The assurance engagement of the customer ends without a material finding.
These outcomes are typical, and they are the practical result of building the right data infrastructure before the reporting cycle begins.
Three implementation barriers
Barrier 1: Data structure
ISO 14083 requires specific inputs for each transport leg. However, most logistics operators do not have this data in one place, in a structure that makes the calculation straightforward. The relevant data is spread across several systems:
- Transport management systems: routing and booking data
- Fuel management systems: consumption records
- Carrier systems: the own operational data of the carriers, which is only half the answer
These sources are not integrated, and nobody designed them for emissions calculation. Assembling the inputs for even a single ISO 14083 calculation can therefore take hours of manual data retrieval. This is not practical for thousands of shipments. For small and medium-sized enterprises (SMEs) and small logistics operators, this is often a barrier that they cannot overcome with internal resources alone.
Barrier 2: Digital workflow
Compliance with ISO 14083 is an operational requirement and not a one-time exercise: it applies to every shipment in every reporting period. The calculation workflow needs to be systematic, repeatable and scalable.
For most operators, the existing workflow looks like this: a small team calculates emissions with spreadsheets, periodically, usually at year-end. Compliance therefore depends on the effort of a few individuals, and not on the design of the system, which makes compliance fragile. Compliance breaks when a key person leaves, or when shipment volumes become larger than a spreadsheet process can handle. The core operational change is a digital workflow. It applies the ISO 14083 calculation to each shipment when the shipment is processed, and not afterwards at reporting time. Most logistics operators have not yet made this change.
Barrier 3: Exportable outputs
ISO 14083 calculations serve external purposes: CSRD Scope 3 reporting, data requests from the clients of carriers, assurance review and interoperable data exchange. Each of these needs the calculation result in a format that the receiving party can use. In practice, most operators that have built some calculation capability have not built the output layer. The calculation produces a number. However, the packaging that follows is not automated: the methodology documentation, the data quality disclosure, the audit trail and the customer-ready format. As a result, even operators that calculate correctly cannot fully use their data externally. The calculation is done, but the record is not ready for external use.
How CO2Path addresses the implementation gap
CO2Path addresses all three barriers. A step-by-step look at how shipment data becomes a trusted record covers the full mechanics.
Data structure: CO2Path accepts transport activity data in standard formats and validates the inputs according to ISO 14083 when it loads them. Sometimes primary data, which is measured data, is unavailable. Then CO2Path applies the default values of the GLEC Framework, the industry guide to applying ISO 14083, and shows this openly.
Digital workflow: CO2Path calculates at shipment level when the shipment is processed, and not afterwards.
Exportable outputs: CO2Path generates outputs with complete documentation. They contain the methodology reference, the emission factor version, the data quality tier, the allocation basis and the blockchain record identifier. The outputs are built on the same trust infrastructure that external reviewers expect, in formats designed for CSRD reporting and external data sharing.
The platform therefore resolves all three barriers, and the operator does not need to solve them with internal effort.
CO2Path is built for operators who need ISO 14083 in practice → Request a demo