The Food Miles Report a Co-op Can Actually Produce: Turning Routes, Producer Locations and Order Lines Into a Defensible Sustainability Statement

Why generic ESG tools cannot produce a food co-op's impact numbers

Generic ESG platforms are built to collect supplier questionnaires and apply industry-average emissions factors to spend categories. A co-op does not need averages. It already holds the exact producer address, the exact route the van drove and the exact kilograms on each order line, which are the primary data most ESG software spends money trying to estimate.

The mismatch shows up immediately. A spend-based ESG tool asked to assess a co-op would take the €4,200 paid to vegetable growers last month, multiply it by a national emissions factor for 'agricultural products', and return a number that is identical whether those vegetables came from 12 km away or 1,200 km away. That is precisely the distinction a short food supply chain exists to make, and it is the one the tool erases.

The other problem is scope. Frameworks like the GHG Protocol treat purchased goods and upstream transport as Scope 3, the category most organisations report as an estimate because they cannot see into their suppliers' operations. A co-op can see into them. The producer is on the platform, the pickup point is a coordinate, and the delivery leg is a recorded route. A co-op's Scope 3 transport data is closer to primary measurement than most large retailers will ever get.

What data a co-op already holds that can be turned into a report

Five data sources are usually enough: producer locations, order lines with weights, route records, hub throughput, and pack-down waste logs. Everything in a credible food miles and local impact report is derived from those, and most co-ops are already capturing four of the five without realising it is reportable.

The gap is almost always weight. Order lines are frequently stored in units the co-op sells in, bunches, punnets, heads, jars, and a food miles figure needs mass. The fix is a one-time exercise: add an average kilogram value to each product record. A bunch of chard is 0.25 kg, a jar of honey is 0.45 kg net plus 0.2 kg of glass. It takes an afternoon for a 300-line catalogue and it converts the entire order history into something measurable, retroactively.

The second gap is the producer's own inbound leg. If a grower drives to a drop-off point, that distance belongs in the report and the co-op's system rarely knows it. Ask producers once, at onboarding, for the distance from their holding to the hub and how they usually get there. One field, filled in once, closes the largest hole in the calculation.

Producer records: holding address or coordinates, and self-reported distance to the hub
Product records: an average net weight per selling unit, plus packaging weight where relevant
Order lines: product, quantity, producer, delivery date, destination postcode
Route records: stop sequence, actual or planned distance, vehicle type and fuel
Pack-down logs: unsold, damaged and redistributed items by weight and reason

How to calculate food miles without overclaiming

Calculate weighted average food miles as the sum of (kilograms x kilometres) for every order line, divided by total kilograms delivered. Report it in tonne-kilometres per delivery leg, state whether it covers the inbound producer leg, the hub, or both, and never compare it to a supermarket figure you did not calculate yourself.

Work in three legs and keep them separate in the output. Leg one is producer to hub. Leg two is hub to customer, which the routing data gives you directly. Leg three, customer to home, applies to pickup points and is usually excluded, but say so rather than silently dropping it. A report that shows 14 km inbound, 9 km outbound and an excluded final leg is more credible than a single unexplained '23 food miles' claim.

The trap is comparison. Food miles are a distance metric, not a carbon metric, and a full-load lorry from 500 km away can carry a lower per-kilogram footprint than a half-empty van doing a 40 km loop. If you want a carbon figure, apply a published emissions factor for your vehicle class to the tonne-kilometre total and cite the factor and its year. If you only want to state distance, call it distance. Both are defensible. Blending them is not.

Total tonne-kilometres = sum of (line weight in tonnes x leg distance in km)
Weighted average food miles = total tonne-km / total tonnes delivered
Load efficiency = tonnes carried / vehicle capacity, reported per route
Optional carbon estimate = tonne-km x a cited emissions factor for the vehicle and fuel

The two metrics that matter more than distance: local spend and waste avoided

Local economic retention and diverted waste are usually the strongest numbers a co-op has, and both come from data it already reconciles. Local spend is the share of shopper payments that reaches producers within a defined radius. Waste avoided is the weight of food that reached a person instead of a bin at pack-down.

Local spend is calculated from the settlement run, not from turnover. Take the total paid out to producers in the period, split it by the distance band of each producer's holding, and express it as a percentage of gross shopper spend. A co-op that pays out 68 cents of every euro to producers within 50 km can say that, and can show the payout ledger behind it. That figure is far more meaningful to a council or a rural development fund than a carbon estimate, because it maps directly onto the reason public money supports short supply chains. Multiplier claims are a separate matter: unless you have commissioned local economic research, report the retained spend and let others apply multipliers to it.

Waste needs a discipline the co-op may not have yet: weighing at pack-down and recording a reason code. Unsold surplus, damage in transit, customer no-show, over-forecast. Once those exist, the report can state total kilograms handled, kilograms diverted to food banks or staff, kilograms composted and kilograms landfilled. It also stops being purely a reporting exercise, because the reason codes tell you which producers are over-supplying and which routes are damaging stock.

Writing the statement so it survives scrutiny

A defensible sustainability statement has four parts: the number, the boundary, the method and the data source. Omit any one of them and an assessor is entitled to discount the whole claim. The goal is not the most impressive figure, it is a figure someone else could reproduce from your records.

State the boundary in plain language. Which period, which producers, which delivery legs, what is excluded and why. If 6 of your 38 producers never returned a distance figure, say that their volume was excluded and give the percentage of tonnage that represents. If you estimated packaging weight rather than weighing it, say estimated. Named limitations make the rest of the report more believable, not less.

Then keep it comparable over time. Freeze the method for at least a year, version it, and when you change something, restate the prior period on the new basis. A co-op that reports 11.4 weighted average food miles in year one and 9.8 in year two, on a stated and unchanged method, has told a real story. One that changes its distance definition between reports has told nothing at all.

Number: the metric, its unit and the reporting period
Boundary: producers, legs and product categories included and excluded
Method: the formula, any emissions factor used, and its published source and year
Source: which system the underlying records came from and whether they are measured or estimated
Limitations: missing data, estimates and the share of volume they affect

Turning the report into an operating habit, not an annual scramble

Impact reporting only stays accurate if the inputs are captured during normal work rather than reconstructed at year end. That means the producer distance field is mandatory at onboarding, product weights are required before a line goes live in the catalogue, and pack-down weighing is part of closing the hub, not an extra task.

The payoff is that the same fields serve two purposes. Load efficiency per route is a sustainability metric and a cost metric. Waste reason codes feed a food loss figure and a producer forecasting conversation. Producer distance bands support a local spend claim and a decision about which new grower to recruit for a thin category. None of this is separate ESG overhead if it is wired into the operational data model from the start.

This is where a platform that already holds producer locations, routes, order lines and pack-down records has an advantage over a bolt-on reporting tool. Plodie captures those records because the co-op needs them to run deliveries and pay producers, which means the sustainability report is an aggregation of operational truth rather than a separate exercise in estimation.

Key Takeaways

A co-op holds primary data, exact producer locations, route distances and order weights, that large ESG tools can only estimate with spend-based averages.
Weighted average food miles = total tonne-kilometres divided by total tonnes delivered, reported leg by leg with the boundary stated.
Food miles are a distance metric, not a carbon metric. Apply a cited emissions factor if you want carbon, and never blend the two.
Local spend retention from the payout ledger and weighed pack-down waste are usually more persuasive to funders and councils than a carbon estimate.
A claim survives scrutiny only when the number is published alongside its boundary, method, data source and named limitations, and the method stays frozen year to year.

Many of these inputs overlap with the operational view we set out in 9 metrics a short food supply chain administrator should track, several of which feed straight into the impact report described here.

Frequently Asked Questions

Are food miles actually a good measure of environmental impact?

On their own, no. Transport is often a small share of a food product's total footprint compared with production method, heating for greenhouse crops and refrigeration, and a full lorry can beat a half-empty van per kilogram. Food miles are still worth reporting as a transparent distance metric and as an input to load efficiency, but present them as distance rather than as a carbon claim.

How do I calculate food miles if some producers won't give me their location?

Exclude their volume from the calculation and state the exclusion as a percentage of total tonnage in the report. Do not substitute a guessed distance or a regional average, because that turns a measured figure into an estimated one without flagging it. In practice, making the distance field mandatory at producer onboarding closes the gap within one recruitment cycle.

What emissions factor should a small food hub use for its delivery van?

Use a published government or recognised national factor for your vehicle class, fuel type and load state, and cite the publication and its year in the report. Many countries publish annual conversion factors for freight and light commercial vehicles. Recalculate when the factor is updated, and restate prior periods if you want the trend to remain comparable.

Does a small co-op legally have to report sustainability metrics?

Most small co-ops and food hubs fall below mandatory sustainability reporting thresholds such as those in the EU's corporate sustainability rules. The pressure usually comes instead from grant applications, public procurement tenders, local authority partnerships and retail or restaurant buyers with their own Scope 3 targets. Voluntary reporting done well is often what wins those contracts.

How is a local economic multiplier different from local spend retention?

Local spend retention is what you can measure directly: the share of shopper payments that reaches producers inside a defined radius, taken from your payout ledger. A local economic multiplier estimates how many times that money recirculates in the area and requires separate economic research to establish. Report the retention figure as fact and treat any multiplier as a cited external estimate.