Emissions tracking in delivery is the practice of calculating the greenhouse gas emissions of every shipment you send, in kilograms of CO2 equivalent, from the weight, the distance and the transport mode, using a recognized method such as ISO 14083. Done well, it gives a retailer one number per parcel, one total per carrier, and a report an auditor can follow.
One calculation, applied to every shipment whichever carrier moved it, with the method, the factors and the inputs written down, is what makes a delivery emissions figure reportable. Carrier spreadsheets, each in its own format and on its own method, can feed that calculation as evidence; on their own they cannot be added into one total.
What is emissions tracking in delivery?
Emissions tracking in delivery is the calculation of a CO2e figure for each shipment, based on what was shipped, how far, and by which mode, followed by the reporting of those figures over a period. The unit is kilograms of carbon dioxide equivalent, written kg CO2e, which folds the other greenhouse gases into a single carbon number so that road, air, rail and sea shipments can be compared and added.
Tracking differs from an estimate at shipment level, in the method, and in the record it keeps. A total for the year, divided by the number of parcels, tells you nothing about which lanes (each origin-to-destination pair), modes or carriers produced it; a figure per shipment does. A carrier's own figure is useful evidence, but twelve carriers with twelve methods give you twelve numbers that cannot be added, so tracking applies one method to every carrier. It also records which factor was used, which distance, which weight, and when the calculation ran, because the assurance process described later asks for that trail.
For an ecommerce retailer the shipments in question are mostly parcels: warehouse to home, warehouse to pickup point, store to home, and the return leg. Each of those is a transport chain with an origin, a destination, a weight and a mode, which is exactly the set of inputs the calculation needs. The same applies to a wholesaler moving pallets or a marketplace seller shipping cross-border, at a different scale.
Where do delivery emissions sit in scope 1, 2 and 3?
For a retailer that pays carriers to move its parcels, delivery emissions are scope 3, in the categories the GHG Protocol calls upstream and downstream transportation and distribution. The scopes come from the GHG Protocol, the accounting framework that most corporate reporting, including the European sustainability standards, builds on. In its words: "Scope 1 emissions are direct emissions from owned or controlled sources. Scope 2 emissions are indirect emissions from the generation of purchased energy. Scope 3 emissions are all indirect emissions (not included in scope 2) that occur in the value chain of the reporting company, including both upstream and downstream emissions."
Carrier deliveries are indirect because the vehicles belong to the carrier. If you run your own vans, their fuel is scope 1 and the electricity that charges them is scope 2; the moment a parcel goes to DHL, PostNord or a local courier, its emissions move into scope 3. The GHG Protocol's Scope 3 standard splits that into fifteen categories, and delivery falls into two of them. Category 4, upstream transportation and distribution, covers "transportation and distribution services purchased by the reporting company in the reporting year (including both inbound and outbound logistics)". Category 9, downstream transportation and distribution, covers the transport of sold products "between the reporting company's operations and the end consumer (if not paid for by the reporting company)".
For an ecommerce retailer, a delivery you pay the carrier for is category 4, even though the parcel is going out to a customer, because the rule turns on who bought the transport service. When the customer arranges and pays for the delivery themselves, it is category 9. Returns follow the same logic. A retailer that pays for its outbound and return parcels reports them under category 4, and that line multiplies a small number per parcel by every order of the year.
For a retailer that pays carriers to move its parcels, delivery emissions are scope 3: category 4 when you buy the transport, category 9 when the customer does.
GHG Protocol Corporate Value Chain (Scope 3) Standard, categories 4 and 9
How is transport emissions calculation standardized?
Transport emissions calculation is standardized by ISO 14083, an international standard published in March 2023, and by the GLEC Framework, the Smart Freight Centre's method that the standard grew out of. Carriers and shippers use the framework to apply the standard. In the words of the ISO page, ISO 14083 "establishes a common methodology for the quantification and reporting of greenhouse gas (GHG) emissions arising from the operation of transport chains of passengers and freight". It replaced the earlier workshop agreement IWA 16:2015, and in Europe it took over from EN 16258, the previous method many carriers had used.
The GLEC Framework describes itself as "the global standard for harmonized calculation and reporting of logistics emissions". In practice the two go together: ISO 14083 is the standard a method is measured against, and GLEC is the working guide that carriers, shippers and software providers follow to meet it. A tool described as aligned to both is claiming to follow the framework's method and to meet the standard's requirements.
Day to day, the data hierarchy is the rule you will use most. Primary data, measured by the carrier on the actual vehicle and route, ranks first. Modeled data, built from measured averages for a mode and vehicle class, comes second and is preferred over defaults whenever primary data is unavailable. Generic default values rank last. A retailer's figure is only as reliable as the source of the factor behind it. So the question to ask any carrier or tool is where the factor came from, and "an industry average" should appear in the report by exception. Our post on the EU environmental rules for ecommerce in 2026 covers what that hierarchy means for a claim that will face an auditor.
The weight used is the gross weight of the shipment, packaging included; the carrier's billing weight plays no part in the emissions figure. The calculation also covers the whole transport chain, so a parcel that goes van to hub to linehaul to van is accounted for across every leg of that chain.
What is an emission factor, and where does it come from?
An emission factor is the amount of CO2e produced by moving one tonne of freight one kilometer with a given mode and vehicle, expressed in kilograms of CO2e per tonne-kilometer. It comes from published datasets such as those of NTM, the Network for Transport Measures, or from a carrier's own measured data. It is the number that turns a shipment's weight and distance into an emissions figure. A diesel truck on a long lane, a delivery van on urban rounds, a container ship and a cargo flight each have their own factor, and factors also differ within a mode, by vehicle size, fuel and load factor.
Published datasets supply the factors. The source nShift Emissions Tracker uses is NTM, a Swedish non-profit initiated in 1993 that, in its own description, offers "a calculation method and relevant environmental data" for all modes of freight and passenger transport. NTM's factors are modeled datasets, the second rung of the ISO 14083 hierarchy, and NTM updates them regularly. Primary data ranks above a modeled factor: it is a carrier's own measured emissions for the actual shipments, and the method puts it first wherever a carrier can supply it. An organization-specific factor also replaces the modeled factor, for a particular flow such as a carrier running electric vans on its account, but it is a value the retailer defines and no measurement stands behind it.
Shipment emissions = emission factor (kg CO2e per tonne-km) x distance between zones (km) x gross weight (tonnes)
The calculation nShift Emissions Tracker writes to every shipment record, with the factor, distance, weight and timestamp stored on the row
Take a parcel with a gross weight of five kilograms, a road distance of three hundred kilometers between the origin and destination zones, and an illustrative road factor of 0.1 kg CO2e per tonne-kilometer, a round number chosen for the sum and not a published value. Convert the weight to tonnes: 0.005. Multiply by the distance: 1.5 tonne-kilometers. Multiply by the factor: 0.15 kg CO2e for that shipment. Run the same sum for every parcel of the year and the total is your category 4 figure for parcel delivery; run it per carrier, per lane or per mode and you have the breakdown that shows where the total comes from.
The distance in that sum is between origin and destination zones, worked out the same way for every shipment instead of taken from each carrier's own reported route, so that two carriers serving the same lane are compared on the same basis. The factor is applied per shipment too, so a change in the mix, more parcels to pickup points or a lane moved from air to road, appears in the total the following month. A carrier's own fleet improvement shows up only when the factor for that carrier changes with it, through primary data or an organization-specific factor.
What data do you need per shipment and per carrier?
Each shipment needs an identifier, an origin, a destination and a gross weight. The distance is modeled from the origin and destination, and the mode follows from the carrier service that moved the parcel, so per carrier you need to know which service was used. The distance model and the factors are part of the method, so the data you collect stays small.
The table below lists the inputs, where each one normally comes from, and what happens when it is missing.
| Input | Where it comes from | If it is missing |
| Consignment id | Order or shipping system | The shipment cannot be matched to a report row |
| From country and postal code | Warehouse or store record on the shipment | Distance cannot be modeled; the row is excluded |
| To country and postal code | Customer address on the order, pickup point on the booking | Distance cannot be modeled; the row is excluded |
| Gross weight | Warehouse scale at packing, written to the shipment | A product weight understates the figure; a default weight flattens every row to the same value |
| Carrier service and mode | The booking record | A generic road factor is applied, which misreads air and sea lanes |
| Primary carrier data (optional, as evidence) | The carrier's own ISO 14083-aligned report | The modeled factor stands; a report should state which source each row used |
Origin and destination postal codes matter more than street addresses, because the distance model works between zones; a warehouse code and the customer's code are enough. Weight is the input to check first, because an order system often holds the product weight and not the packed weight, and the standard asks for gross weight. Fixing that once in the warehouse system, so that the scale reading at packing is what goes on the shipment record, improves every emissions figure afterwards.
Per carrier, the useful extra is primary data. Where a carrier publishes shipment-level or lane-level emissions on its own ISO 14083-aligned method, the standard ranks that data above a modeled factor, and a report should say which shipments used which source. In nShift Emissions Tracker, every shipment is calculated on the NTM modeled factors or on an organization-specific factor the retailer defines. The consistent modeled figure for every shipment is the baseline, and a carrier's primary data is kept alongside it as evidence.
Returns are shipments too. A returned parcel has an origin (the customer), a destination (the warehouse or the store) and a weight, and it belongs in the same table. Leaving returns out understates delivery emissions by the return rate, whatever that rate is for the category.
How do you report delivery emissions?
Delivery emissions are reported as a total in kg or tonnes of CO2e for the period, broken down by scope 3 category. Alongside the total go the method, the factor sources and the share of primary versus modeled data, so that a reader can judge the number and an auditor can retrace it. The readers are the sustainability team that compiles the corporate inventory, finance, which owns the assurance process, and operations, which is asked what changed and why.
The regulation that sets the bar in Europe is the Corporate Sustainability Reporting Directive. As of the European Commission's CSRD page, updated 3 July 2026, the first wave of companies reported for the 2024 financial year, in 2025. The "stop-the-clock" directive, Directive (EU) 2025/794, postponed the second and third waves by two years, so large companies in those waves report for the first time in 2028 for the previous financial year. The Omnibus I package, adopted as Directive (EU) 2026/470 and in force since 18 March 2026, narrows the directive to companies with more than 1,000 employees and a net turnover above EUR 450 million, reporting from the 2027 financial year. A retailer near either line should check the directive's thresholds against its own group figures before assuming it is out of scope, and a retailer above them should plan for an audited scope 3 figure.
An auditor needs the shipment rows behind the total, with the factor and the distance on each, and that need sets the shape of the reporting. The practical form is an export, CSV or Excel, of every shipment in the period with its emissions columns, plus summaries by carrier, mode and lane. Feeding the same data into the business intelligence (BI) tool finance already uses keeps one set of numbers across the company, so the sustainability report, the annual report and the board deck quote the same figure. Because the calculation is the same every month, the report comes out of the monthly run, and the year-end figure is the twelve monthly runs added together.
How a delivery platform automates emissions tracking
A delivery platform automates emissions tracking by running the calculation on every shipment it already handles. The weight, the origin, the destination and the carrier service come from the booking record, with no second collection, and the emissions figure is written to the shipment alongside the label and the tracking events. The retailer keeps the packed weight accurate and decides which reductions to make with the numbers that come out.
This is what nShift Emissions Tracker does for shipments booked through nShift's multi-carrier shipping and delivery experience platform. It calculates shipment-level CO2e with NTM factors, aligned to ISO 14083, EN 16258 and the GLEC Framework, with mode-specific emission factors for road, air, rail and ocean. Where a carrier arrangement warrants one, a retailer can define an organization-specific factor. The methodology is certified by the Smart Freight Centre, which validated it against ISO 14083 and the GLEC Framework. The output is a report per shipment, with the factor, the distance, the weight and the calculation timestamp on every row: the trail an auditor asks for. It exports to CSV or Excel, or feeds a business intelligence stack through the API. One platform connects you to 1,000+ carriers, so the same calculation covers every carrier in the network without a per-carrier build.
Because every shipment carries its own figure, the report can be filtered down to the hotspots: a lane where air is used for parcels that could go by road, or a carrier whose service mix carries a high factor. A region where home delivery dominates is a third, because a pickup-point option there would cut the last-mile distance. Our post on how retailers and supply chains gain visibility on emissions shows how those hotspots turn into decisions, and the piece on the latest technologies for the ecommerce carbon footprint covers the sensor and telematics side that feeds primary data into the model over time.
How to start tracking delivery emissions
Start by checking the four inputs on your shipment records, then pick the method, then run the first month and read it by carrier and lane before you set a target. The checklist below is the order that avoids the usual rework, where a team builds a dashboard on weights that turn out to be product weights and has to start again.
Five steps to a first delivery emissions report
1. Check the four inputs. Consignment id, origin postal code, destination postal code and gross weight on every shipment record, returns included.
2. Fix the weight at source. The packed weight from the warehouse scale, not the product weight from the catalog.
3. Pick the method and the factor source. ISO 14083 with the GLEC Framework; modeled factors from NTM unless a carrier provides primary data.
4. Run one full month. Every carrier, every lane, with the data source marked per row.
5. Read it by carrier and lane before you set a target. Pick one reduction, change it, re-run the next month.
The first month's report is a baseline, and its value is in the breakdown. Sort it by carrier and by lane, mark which rows used primary data and which used modeled factors, and pick one reduction to test: a pickup-point option on the busiest urban lane, or a service change on the one lane that runs by air. Re-run the next month and compare. The at-a-glance table sums up what each part of the method contributes.
| Part of the method | What it settles | Where it comes from |
| Scope and category | Delivery is scope 3, category 4 (you pay the carrier) or 9 (the customer pays) | GHG Protocol Scope 3 Standard |
| Calculation standard | One method for every carrier and mode; primary data first, modeled second, defaults last; gross weight; whole transport chain | ISO 14083:2023, applied through the GLEC Framework |
| Emission factor | kg CO2e per tonne-kilometer by mode and vehicle class | NTM modeled datasets, carrier primary data where available, organization-specific factors by exception |
| Shipment data | Id, origin, destination, gross weight, carrier service | Your order, warehouse and booking records |
| Reporting | Per-shipment rows with factor, distance, weight and timestamp; summaries by carrier, lane and mode; CSV, Excel or API | The delivery platform's emissions report |
| Regulation | CSRD waves; the 1,000-employee and EUR 450 million turnover thresholds under Omnibus I, Directive (EU) 2026/470; the ESRS, the European Sustainability Reporting Standards | European Commission CSRD page, 3 July 2026, and Directive (EU) 2026/470 |
The reductions need the tracking in place first. If your shipment records already run through a delivery platform, the calculation can be switched on for them. nShift Sustainability Reporting shows how the method described here is applied to every shipment, and what the report looks like, before you commit to a target.
FAQ
What is emissions tracking?
What is ISO 14083?
What is the GLEC Framework?
Are delivery emissions scope 3?
How accurate is emissions tracking for parcels?
Does CSRD apply to my company?
About the author
Thomas Bailey
Thomas plays a key role in shaping how new features and platform improvements deliver real value to customers. With a background spanning product, tech, and go-to-market strategy, he brings a pragmatic view of what innovation looks like in practice and how to make delivery experiences work harder for your business.