Supply chain emissions
at shipment level
CSRD requires per-activity emissions data with verifiable methodology. Your spreadsheet of annual estimates won't survive an audit. Calculate emissions for every shipment, compare carriers, analyse lanes, and export disclosure-ready Scope 3 Category 4 data — with a full source trail your assessor can verify.
Transparent pricing · 500 free requests/month · No sales calls
Annual estimates aren't good enough anymore
CSRD and ISO 14083 changed the game. Here's what assessors expect now.
What most companies do
Take last year's total freight spend, multiply by an industry-average emission factor, report a single number for Scope 3 Category 4.
No visibility into which lanes, carriers, or modes drive emissions. No way to track reductions. No audit trail.
Why assessors reject it
CSRD's European Sustainability Reporting Standards (ESRS E1) require activity-based calculation methods where feasible. Spend-based estimates are a last resort, not a default.
What per-shipment data gives you
Calculate emissions for every shipment using distance, weight, mode, vehicle type, and fuel source. Aggregate however you need — by lane, carrier, quarter, or product.
50,000 shipments per quarter? No problem.
Export your TMS or ERP shipment data. Pass each record through the API. Get back emissions with GLEC-compliant methodology and a source trail for every single calculation. Then aggregate by whatever dimension matters to your report.
The API returns raw per-shipment data. You control how it's grouped, filtered, and reported. No rigid dashboard — just clean data that fits your existing reporting workflow.
# Calculate emissions for all Q4 shipments
import requests
from collections import defaultdict
def process_shipments(shipments, api_key):
results = []
for s in shipments:
resp = requests.get(
"https://api.emissions.dev/v1/freight/emissions",
headers={"Authorization": f"Bearer {api_key}"},
params={
"origin_country": s["origin_country"],
"origin_location": s["origin_city"],
"destination_country": s["dest_country"],
"destination_location": s["dest_city"],
"weight": s["weight_kg"],
"transport_mode": s["mode"],
"vehicle_type": s.get("vehicle", "average"),
"fuel_source": s.get("fuel", "diesel"),
}
).json()
emissions = resp["data"]["attributes"]["emissions"]
results.append({
"lane": f"{s['origin_country']}→{s['dest_country']}",
"carrier": s["carrier"],
"co2e_kg": emissions["co2e"],
"source_trail": emissions["source_trail"],
})
# Aggregate by lane
by_lane = defaultdict(lambda: {"co2e": 0, "n": 0})
for r in results:
by_lane[r["lane"]]["co2e"] += r["co2e_kg"]
by_lane[r["lane"]]["n"] += 1
# Top 5 lanes = likely 60%+ of total
return sorted(by_lane.items(),
key=lambda x: x[1]["co2e"], reverse=True)
Compare carriers on carbon, not just cost
Same lane, same weight, same schedule — but your carriers use different vehicles, fuels, and routing. That means different emissions. Quantify the difference and use it in your next tender.
London → Berlin, 5,000 kg. Same origin, same destination, same weight. The difference is vehicle type, fuel source, and whether the trunk leg goes by road or rail.
// Compare carrier emissions for the same lane
const base = {
origin_country: 'GB',
origin_location: 'London',
destination_country: 'DE',
destination_location: 'Berlin',
weight: 5000,
};
const carriers = [
{ name: 'Carrier A', transport_mode: 'road',
vehicle_type: 'articulated', fuel_source: 'diesel' },
{ name: 'Carrier B', transport_mode: 'road',
vehicle_type: 'articulated', fuel_source: 'hvo' },
{ name: 'Carrier C', transport_mode: 'rail',
vehicle_type: 'average', fuel_source: 'electric' },
];
const results = await Promise.all(
carriers.map(async (c) => {
const r = await fetch(
'https://api.emissions.dev/v1/freight/emissions?' +
new URLSearchParams({ ...base,
transport_mode: c.transport_mode,
vehicle_type: c.vehicle_type,
fuel_source: c.fuel_source,
}), { headers: { Authorization: `Bearer ${key}` }}
).then(r => r.json());
return {
carrier: c.name,
co2e: r.data.attributes.emissions.co2e,
fuel: c.fuel_source,
};
})
);
results.sort((a, b) => a.co2e - b.co2e);
// "Carrier C saves 69% CO₂e on this lane"
Your top 10 lanes are probably 60% of your footprint
Logistics emissions follow a power law. A handful of high-volume or long-distance lanes dominate your total. Identify them, and you know exactly where to focus your reduction strategy.
Once you've identified the hotspots, test scenarios: what if Shanghai→Hamburg switches from air to sea for non-urgent shipments? What if Hamburg→London moves to an HVO carrier? The API lets you model both.
// Find top emitting lanes, then model a reduction
$shipments = Shipment::whereYear('shipped_at', 2025)->get();
$lanes = $shipments->groupBy(
fn($s) => "{$s->origin_country}→{$s->dest_country}"
);
// Calculate current emissions per lane
$laneEmissions = $lanes->map(function ($group, $lane) {
return [
'lane' => $lane,
'shipments' => $group->count(),
'co2e_kg' => $group->sum(fn($s) =>
$this->getEmissions($s)
),
];
})->sortByDesc('co2e_kg');
// Model: switch top lane from air → sea
$topLane = $laneEmissions->first();
$asIs = $topLane['co2e_kg']; // 186,000 kg (air)
$toBe = $lanes[$topLane['lane']]->sum(fn($s) =>
Http::withToken($apiKey)
->get('/v1/freight/emissions', [
'origin_country' => $s->origin_country,
'origin_location' => $s->origin_city,
'destination_country' => $s->dest_country,
'destination_location' => $s->dest_city,
'weight' => $s->weight_kg,
'transport_mode' => 'sea', // ← changed
])->json('data.attributes.emissions.co2e')
);
$reduction = round((1 - $toBe / $asIs) * 100);
// "Switching CN→DE from air to sea saves 97%"
Digital Product Passport: transport emissions per unit
The EU's Digital Product Passport regulation requires per-product carbon footprint data, including transport. That means calculating emissions for every leg of your supply chain and allocating them to individual products.
500 units × 2.5 kg each. Four transport legs. Each calculated separately with the correct mode and distance, then allocated by mass to individual products.
# Calculate per-product transport footprint
# for EU Digital Product Passport compliance
import requests
legs = [
{"from": ("CN", "Shenzhen"),
"to": ("CN", "Shanghai"),
"mode": "road", "stage": "A2"},
{"from": ("CN", "Shanghai"),
"to": ("DE", "Hamburg"),
"mode": "sea", "stage": "A2"},
{"from": ("DE", "Hamburg"),
"to": ("GB", "Bristol"),
"mode": "road", "stage": "A4"},
{"from": ("GB", "Bristol"),
"to": ("GB", "Customer"),
"mode": "road", "stage": "A4",
"vehicle": "van"},
]
units = 500
weight_per_unit = 2.5 # kg
total_weight = units * weight_per_unit
dpp_transport = {}
for leg in legs:
resp = requests.get(
"https://api.emissions.dev/v1/freight/emissions",
headers={"Authorization": f"Bearer {API_KEY}"},
params={
"origin_country": leg["from"][0],
"origin_location": leg["from"][1],
"destination_country": leg["to"][0],
"destination_location": leg["to"][1],
"weight": total_weight,
"transport_mode": leg["mode"],
"vehicle_type": leg.get("vehicle", "average"),
}
).json()
co2e = resp["data"]["attributes"]["emissions"]["co2e"]
per_unit = co2e / units
stage = leg["stage"]
dpp_transport[stage] = dpp_transport.get(stage, 0) + per_unit
# dpp_transport = {"A2": 0.055, "A4": 0.039}
# Total per unit: 0.094 kg CO₂e
Freight buyer or asset owner? Both perspectives in one call.
The GLEC Framework requires different scope allocation depending on whether you're the freight buyer (shipper) or the asset owner (carrier). We return both in every response — no extra configuration.
Freight buyer (shipper)
All transport emissions sit in your Scope 3 — upstream and downstream.
Asset owner (carrier)
Combustion is Scope 1, fuel production is Scope 3.
If you're a 3PL reporting to shippers, you need the asset owner view. If you're a brand reporting your supply chain, you need the freight buyer view. Both are in every response.
{
"emissions": {
"co2e": 156.78,
"co2e_unit": "kg",
"lifecycle_breakdown": {
"vehicle_operation": 125.42,
"energy_provision": 31.36
},
"ghg_protocol_scopes": {
// Shipper perspective (you buy transport)
"freight_buyer": {
"scope_3_category_4": 156.78
},
// Carrier perspective (you operate vehicles)
"asset_owner": {
"scope_1": 125.42,
"scope_3_category_3": 31.36
}
}
}
}
// The same 156.78 kg, allocated differently
// depending on who's reporting
What your assessor will ask for
CSRD limited assurance means your methodology must be documented, consistent, and verifiable. Here's how emissions.dev delivers each requirement.
"Which emission factors?"
Every response names the exact factor, source dataset, year, and region. GLEC Framework v3.1 default values with DEFRA supplements where applicable.
source_trail"Which GWP values?"
IPCC AR6 GWP100 across all calculations. Stated in every response via co2e_calculation_method. No mixing of AR4 and AR5 factors.
"What boundary?"
Well-to-wheel by default with TTW/WTT split in lifecycle_breakdown. Maps to Scope 1 and Scope 3 Category 3 for asset owners.
"Is it reproducible?"
Same inputs produce the same outputs. Pin to a factor year if needed. Re-run any historical period and get identical results for your baseline comparison.
DeterministicFits your logistics stack
A REST API that plugs into the systems you already use.
TMS / WMS
Calculate emissions when shipments are created or completed. Add CO₂e as a field on every shipment record.
ERP Systems
Enrich purchase orders and goods receipts with transport emissions for procurement reporting.
ESG Platforms
Feed shipment-level data into your carbon accounting platform. Pre-categorised by GHG Protocol scope and category.
Custom / Data Pipeline
REST API with JSON responses. Process shipment exports from CSVs, data warehouses, or event streams.
Build it yourself, or don't
Here's what CSRD-grade supply chain emissions reporting actually requires.
Do it yourself
Parse GLEC Framework PDFs, license data, build lookup tables by mode/vehicle/fuel, update annually
Road routing API, maritime lane database, great circle for air, rail network distances
Build dual-perspective logic (freight buyer vs asset owner), WTT/TTW split, category mapping
Refrigeration surcharges, empty return legs, partial loads — all edge cases you'll hit
Factor provenance, version control, methodology documentation for CSRD limited assurance
Estimated effort: 3–6 months engineering time + ongoing maintenance
Use emissions.dev
GLEC v3.1 defaults, 13 fuel types, 6 vehicle classes — always current, applied automatically
Pass origin + destination. We handle road routing, sea lanes (Suez, Panama), and air distances
Both perspectives in every response. WTT/TTW split, Category 4 and 9 mapping. Done.
Add refrigerated=true or include_empty_return=true. One parameter each.
source_trail in every response. Factor name, dataset, year, region. Hand it to your assessor.
Estimated effort: One afternoon to integrate. We handle the rest.
See the full Freight API
Road, rail, sea, and air freight with 13 fuel types, 6 vehicle classes, real road routing with polyline output, and sea lane distances via Suez, Panama, and Cape routes. Full technical reference with interactive demo.
Start reporting supply chain emissions
Get your API key in 30 seconds. Process your first shipment in under a minute. 500 free requests per month — enough to test with real data before committing.
No credit card · No sales calls · No procurement