Same shipment, three unsolved problems: why shippers, forwarders, and carriers can't agree on one emissions number
Ask a shipper, a freight forwarder, and a carrier to describe their biggest freight emissions data problem, and each will describe something that sounds specific to their seat at the table. It isn't. It is the same problem, seen from three different vantage points, and it stays unsolved for as long as each party assumes it is theirs alone.
The shipper's seat
Scope 3 Category 4 is not a future line item in a shipper's CSRD disclosure, it is a current one. What lands on the sustainability team's desk to support it, though, rarely looks the same twice: one forwarder replies with a spreadsheet built on an internal emission factor nobody outside their office can name, another sends a PDF summary with no stated methodology at all, a third has no shipment-level answer yet and falls back to an industry average. None of this is bad faith. It is what happens when there is no shared standard upstream of the request.
The forwarder's seat
The forwarder sits in the middle of this and inherits the worst of it. A forwarder routing freight across several carriers and modes for one shipper has to take whatever each carrier in that chain can actually produce, in whatever format that carrier happens to use, and turn it into one coherent answer before it can go anywhere near the shipper. One leg reports in kilometres, another in miles. One carrier's number includes a stated allocation method, another's doesn't say. The forwarder becomes an unpaid data-reconciliation department for a problem they didn't create and can't fix from their seat alone.
The carrier's seat
The carrier, meanwhile, is the one actually asked to produce a number, and not just once. A carrier serving five shipper relationships gets five different requests for what is functionally the same information: one customer wants a per-lane spreadsheet, another wants raw activity data so they can calculate it themselves, a third simply emails asking "what's your carbon footprint." This is not unique to freight. It is a well-documented pattern across supply chains generally, sometimes called supplier or questionnaire fatigue, where the same organisation answers overlapping sustainability data requests from multiple buyers in as many different formats, at real cost to both the time spent and the quality of what gets reported back, a pattern documented in a multiple-case study analysis of sustainable supply chain management tools. Freight carriers are living a freight-specific version of exactly this.
There's a second cost hiding in this fragmentation: it discourages carriers from investing in primary data at all. Collecting actual fuel and route data primary data instead of falling back on regional defaults only pays off if that better number can be reused. If every customer relationship still needs its own bespoke reformat, there's little incentive to go beyond the default tier for any one of them. A shared standard changes that calculus: primary data collected once, under ISO 14083, answers every customer's request at once, and it's the only tier that doesn't require justifying itself later under CSRD reasonable assurance.
The convergence: one problem, not three
Look at all three seats together and the pattern is obvious. The shipper's inconsistency problem, the forwarder's reconciliation burden, and the carrier's repeated-answer fatigue are not three separate frictions. They are the same missing piece showing up at three different points in the chain: there is no shared calculation standard and no shared output format, so every handoff between shipper, forwarder, and carrier requires manual translation. Fix that once, upstream, and all three problems shrink together, because they were never three problems.
How this actually gets solved
The fix is not better communication between the three parties. It is removing the need for translation in the first place: a carrier calculates once, under ISO 14083 and the GLEC Framework, and the output is structured well enough that a forwarder can pass it straight through without reconciling it, and a shipper can drop it straight into their CSRD workflow without translating it either. Methodology consistency between operators is what makes that possible: the same shipment, calculated the same way, is the same number no matter who is asking.
How CO2Path is built for this
CO2Path calculates at shipment level under ISO 14083 and GLEC, and every output carries its methodology reference and data quality tier attached, the same way, every time. That means a carrier using CO2Path answers the underlying question once, in a format any shipper or forwarder can use directly, instead of producing a bespoke reply for every relationship in the chain. The same shipment-level record that satisfies one customer's CSRD workflow satisfies the next one too, because nothing about it needed to change.
See how CO2Path turns one calculation into an answer every party in the chain can use → Request a demo
Frequently asked questions
Because each party experiences the same root cause from a different position in the chain. Shippers see inconsistent replies to their data requests. Forwarders see the manual work of reconciling whatever each carrier can produce. Carriers see the burden of answering the same underlying question in a different format for every customer. All three are downstream effects of the same missing piece: no shared calculation standard and no shared output format.
Supplier fatigue describes the documented pattern, seen across supply chains generally, of the same organisation receiving overlapping sustainability data requests from multiple buyers, often in different formats, with a real cost to accuracy and response time. Freight carriers experience a freight-specific version of this: the same emissions question, asked differently by every shipper or forwarder relationship.
A forwarder can reformat what a carrier gives them, but reformatting is not the same as fixing the underlying inconsistency. If one carrier's figure carries no stated methodology and another's does, no amount of relabelling makes the two comparable. The fix has to happen at the calculation step, not the reporting step.
If every carrier in a chain calculates under the same standard (ISO 14083 and GLEC), the resulting figures are already comparable and already documented. The forwarder has nothing left to reconcile, and the shipper receives a number that already carries the methodology reference their CSRD disclosure needs. The manual translation step disappears because there is nothing left to translate.
No. The requirement is a shared standard, not a shared vendor. A carrier calculating correctly under ISO 14083 and GLEC produces a figure any forwarder or shipper can use, regardless of what tool produced it. CO2Path's role is making that calculation, and the structured output that carries it, straightforward for the carrier to produce in the first place.
Under fragmentation, there's little reason to: a better number still has to be reformatted separately for every customer, so the extra effort doesn't compound. Once every customer relationship is answered by the same standardised output, primary data collected once pays off across all of them at the same time, and it's also the only data quality tier that doesn't require justifying itself later under CSRD reasonable assurance review.