Why does the GHG Protocol matter for logistics?
The GHG Protocol is the shared language of corporate carbon reporting. It decides where transport emissions sit: a carrier's own fuel is Scope 1, while a shipper's outsourced transport is Scope 3. Reporting frameworks such as ESRS build on its scope definitions.
Where does transport fit in the GHG Protocol?
- Scope 1: fuel burned in vehicles a company owns or controls.
- Scope 2: purchased electricity, including for charging electric vehicles and running hubs.
- Scope 3 category 4: upstream transportation and distribution bought by the company.
- Scope 3 category 9: downstream transportation and distribution.
For transport calculations, ISO 14083 and the GLEC Framework provide the detailed method.
The MIXMOVE perspective
The GHG Protocol sets where transport emissions are reported, while ISO 14083 sets how they are calculated. MIXMOVE DI applies ISO 14083 methodology and records emissions per trip and consignment from the same operational data that runs the network. The carbon engine covers road transport today, including temperature-controlled transport, and supports CSRD and ETS2 reporting. MIXMOVE DI structures Scope 3 transport reports from execution events.
MIXMOVE works alongside an existing TMS, WMS and ERP as an orchestration layer, or as a standalone platform.
Frequently asked questions
Is transport Scope 1 or Scope 3?
Scope 1 for fuel in vehicles a company operates itself, Scope 3 for transport it buys from others.
How does the GHG Protocol relate to ISO 14083?
The GHG Protocol sets the reporting scopes. ISO 14083 provides the detailed method for calculating transport emissions.