Food loss and food waste sit at different points in the food system. FAO and UNEP materials show why a useful market view keeps the supply-chain stage, quality change, destination, and cause visible.
Food loss and food waste sit at different points in the food system. FAO and UNEP materials show why a useful market view keeps the supply-chain stage, quality change, destination, and cause visible.
Food loss needs a different measure from food waste because the events occur at different points in the food system. FAO describes food loss as a decrease in quantity or quality resulting from decisions and actions by food suppliers in the chain, excluding retailers, food service providers, and consumers. UNEP’s Food Waste Index focuses on later-stage food waste measurement.
The market insight is that one total can hide two businesses. Harvest handling, storage, processing, and transport may create loss before retail. Ordering, display, date management, and household behaviour may create waste later. The interventions are not interchangeable.
At a glance
| Field | Question | Use |
|---|---|---|
| Stage | Where in the chain did the quantity or quality change? | Assigns the right owner |
| Product state | Was food rejected, damaged, spoiled, or downgraded? | Clarifies the event |
| Cause | What physical or commercial condition drove it? | Supports prevention |
| Use | Was it sold, recovered, donated, or discarded? | Shows the final outcome |
Put the stage in every record
A record should identify where the event occurred, not only where it was noticed. A processor may discover that incoming produce was damaged, while the supplier or transport stage created the condition. A retailer may find a product out of date, while a forecast or delivery decision created the excess earlier.
Stage information supports fair accountability. It does not excuse a business from managing what it can control, but it prevents a team from treating every outcome as a local failure. The right response can involve a supplier, carrier, facility, store, customer, or policy owner.
Measure quality as well as quantity
Food loss is not always a missing kilogram. A product can lose quality, grade, shelf life, or marketability while remaining physically present. The measure should state which attribute changed and whether the product was rejected, downgraded, reworked, sold through another channel, or discarded.
Quality data can explain why a volume number moved. A crop that reaches a processor late, a package with cosmetic damage, or an ingredient outside specification may have different remedies. The record should not force them into one generic “waste” bucket.
Connect physical and commercial causes
Causes can be physical, operational, commercial, or regulatory. Poor storage, damage, pests, equipment failure, forecast error, buyer specification, market cancellation, or a safety hold may each produce a different action. The cause list should be short enough to use and detailed enough to guide a decision.
Review the cause with the people who own the preceding step. If a retailer sees short shelf life at delivery, the useful question is not only how much was thrown away. It is whether the order cycle, transport, pack date, supplier specification, or receiving rule can change.
Use recovery without hiding prevention
Recovery routes matter, but they should not erase the original event. Donation, animal feed, reprocessing, composting, and energy recovery can reduce the harm of an outcome while leaving the cause untouched. Record the route and the preventable loss separately.
A business can then set two targets: prevent the event and improve the fallback. The first reduces the need for recovery. The second protects value when prevention is not yet possible. Reporting both is more honest than using a diversion rate as a substitute for source control.
Build a supply-chain conversation
FAO’s platform provides a useful shared language for food loss and waste work. A buyer, supplier, processor, carrier, and retailer can use the same basic questions: where did quantity or quality change, what evidence shows it, who decided the next use, and which step can prevent repetition?
The conversation should be grounded in examples rather than only annual totals. Follow one product from origin to customer, keep the failed handoffs, and compare the measured loss with the commercial promise. That creates a practical branch for the next improvement.
How to read the signal
The useful reading of Food Loss Needs a Different Measure From Food Waste is not a promise that one rule, supplier, test, or system will solve the whole food operation. It is a way to connect a visible market or compliance change to the next piece of evidence. Ask what changed for the food, which record proves it, which team owns the exception, and what a supplier, regulator, customer, or operator could check independently. That sequence keeps a headline practical.
Keep three labels separate in the working file: confirmed fact, interpretation, and open question. A source can establish what a rule, standard, or public body says. The food business still has to decide how that evidence fits its products, markets, processes, suppliers, and risk appetite. Recording the boundary is not hesitation. It is how a market desk avoids confusing a useful direction with a completed result.
A strong food brief also records what was not checked. State whether the evidence covers one country or several, one facility or the whole network, a current rule or a planned change, and a sample or a complete population. Readers can then use the article as a starting point without mistaking a practical framework for legal advice, a safety guarantee, or a measured commercial result.
The source ledger should travel with the working decision. Record the document title, issuing body, access date, relevant section, product or process scope, and the question the source can answer. If a source does not answer the commercial question, mark that gap instead of stretching the citation.
A practical first 30 days
For Food Loss Needs a Different Measure From Food Waste, the first month should produce a small working control rather than another strategy deck. Choose one product family, ingredient, line, supplier, or transaction flow. Define the boundary, name the owner, and record the evidence already available. The first result should be narrow enough to inspect and useful enough to change a decision.
In week one, write down the current path for stage. Include the system that creates the record, the people who change it, the handoffs that rely on it, and the customer or operator who sees the result. Mark each point where the record can become incomplete, late, ambiguous, or inaccessible.
In week two, test the path against real examples rather than ideal diagrams. Take a small set of products, ingredients, batches, labels, or inspections and follow them from source to outcome. Keep the failed examples. They show where the process needs a rule, a field, an alert, a permission, or a human decision.
In week three, agree the minimum operating measures and the exception route. A measure is useful only when somebody can act on it. Give the owner a clear response, a deadline, and a place to record the correction. If the team cannot decide what to do when the data is missing, the process is not ready to scale.
In week four, review whether the control changed the intended outcome without creating a new blind spot. Keep the source evidence, the decision, the limitation, and the next review date together. Then extend the pattern to the next branch only if the first flow is understandable to a new team member and explainable to the customer when needed.
What does not matter on its own
- A recovery destination does not tell you where the loss originally occurred.
- One supply-chain total does not show which actor can change the outcome.
Read the wider food desk
For more reporting on food production, processing, sourcing, and distribution, browse the Food & Beverages category or open the latest news archive. The site’s editorial policy explains how source and interpretation are kept distinct.
Frequently asked questions
Why separate food loss from food waste?
They generally describe different stages of the food chain, with different causes, data owners, and prevention methods.
Can food loss include quality decline?
Yes. FAO describes a decrease in quantity or quality, so the measure should state what changed and how the product was handled.
How should recovery be reported?
Record recovery destination separately from the original loss or waste event so diversion is not mistaken for prevention.
Where should a supply chain start?
Follow one product across stages, define the handoffs, capture the evidence, and identify the first controllable cause.
Sources and further reading
- FAO: Food Loss and Waste Platform Source checked 14 September 2026.
- FAO: What is Food Loss? Source checked 14 September 2026.
- UNEP: Food Waste Index Report 2024 Source checked 14 September 2026.
Bottom line
The practical decision is to make food loss needs a different measure from food waste an owned operating question, not a loose marketing promise. Start with one defined flow, record the evidence at each handoff, and give one team the authority to correct the source data.
When the process is ready to scale, use the VM Intelligence sign-in to move from a headline to a structured market workflow.