Food Waste Cost Calculator
Estimate the purchase cost of food waste by item and cause, then compare audit and annual savings under your chosen reduction target.{{ summaryTitle }}
{{ summaryLine }}
{{ exportStatus }}
| Food / cause | Audit cost ({{ currency }}) | Discarded amount | Purchase basis | Cost share (%) | Target saving ({{ currency }}) | Annual cost ({{ currency }}) | Copy |
|---|---|---|---|---|---|---|---|
| {{ row.name }}{{ causeOptions[row.cause] }} | {{ amount(row.cost) }} | {{ number(row.quantity) }} {{ unitLabel(row.unit) }}× {{ row.frequency }} occurrence{{ row.frequency === 1 ? '' : 's' }} | {{ number(row.pack_quantity) }} {{ unitLabel(row.pack_unit) }}{{ money(row.price) }} per pack | {{ Number(row.share).toLocaleString('en-US', { maximumFractionDigits: 2 }) }} | {{ amount(row.savings) }} | {{ amount(row.annual_cost) }} |
Purchase-cost opportunity
- {{ row[0] }}
- {{ row[1] }}
Where to start
Largest item: {{ computation.values.ledger[0].name }}, {{ money(computation.values.ledger[0].cost) }} in this audit ({{ Number(computation.values.ledger[0].share).toLocaleString('en-US', { maximumFractionDigits: 2 }) }}% of purchase loss).
{{ computation.values.advice }}
Trial one change, then repeat an audit covering comparable operating days and demand. Savings become cash savings only when purchasing falls.
Calculation and assumptions
Each row: discarded quantity ÷ purchase-pack quantity × pack cost × occurrences, after converting both quantities to the same unit.
{{ money(computation.values.period_cost) }} ÷ {{ computation.normalizedInputs.audit_days }} audited days × {{ computation.normalizedInputs.annual_days }} annual operating days = {{ money(computation.values.annual_cost) }} annualized purchase loss.
The {{ computation.normalizedInputs.target }}% scenario saves {{ money(computation.values.period_savings) }} in this audit, or {{ money(computation.values.annual_savings) }} annually, if the same share of purchase cost can be prevented.
Share of sales uses {{ money(computation.normalizedInputs.sales) }} of sales for these same audited days. It is not the percentage of food purchased or physical food wasted.
Prices and waste per operating day are held constant. These are gross purchase-cost estimates, excluding labor, disposal, implementation costs, tax and revenue effects. No cooked/raw yield or density conversion is assumed. Review unavoidable waste separately; a target does not establish what is preventable.
Method context: EPA waste-audit guidance and ReFED tracking guidance. Your quantities and invoice costs determine the results.
{{ chartExportStatus }}
The chart could not load. The waste ledger still contains every cost.
The heaviest food in a waste bin is not necessarily the most expensive. A small amount of a costly ingredient can represent more purchase money than a larger amount of cheaper food. Recording what was discarded, how much it cost to buy and why it was discarded helps a restaurant or café identify the losses worth investigating.
Purchase-cost loss values discarded food at its ingredient purchase cost, not at the selling price of a dish. Part of a purchased pack is valued in proportion to that pack's quantity and price. Prepared portions need a corresponding ingredient cost per portion or batch. Using menu prices instead would answer a different question about potential revenue, not the money spent on the food itself.
When different foods share an audit, their purchase costs can be added even when one is weighed, another measured by volume and another counted. Their physical quantities cannot be added into one meaningful amount. Each record still needs to exclude containers and packaging and compare the discard with a matching purchase quantity. All prices must use the same currency.
A week's total for one ingredient and a single day's waste for another do not describe comparable periods. The audit period needs to cover the same operating days for all records. An average loss per operating day can then support an annual estimate, although closures, seasonal demand and changing prices affect how representative that average will be.
Once the costs are comparable, the reasons for discarding food help direct the investigation. Spoilage invites a review of storage and ordering. Overproduction invites a comparison between prepared amounts and demand.
A reduction scenario expresses an assumed decrease in purchase-cost loss, not a finding about what can be prevented. Unavoidable preparation waste may still carry a purchase cost. Preventing one-fifth of the recorded loss does not mean cutting all food purchases by one-fifth. Estimated avoided purchase costs become cash savings only when purchasing falls, and the costs of making a change still matter.
How to Use This Tool:
Replace the illustrative audit with your own records before using the estimates for your business. Valid edits update the results immediately without a Calculate action.
- Set Audited operating days and Currency for the entire audit. The starting values are 7 days and USD. Every entry must cover those same operating days, and changing currency does not convert any amounts.
- Enter each food or category using a weighed, liquid or counted entry from Add item. Supply its Discarded quantity, Purchase-pack quantity and Purchase-pack cost, then choose a Loss reason. For counted portions, use the ingredient cost of the stated number of portions.
Leave Occurrences in this audit at 1 when the discarded quantity is already the audit total. For repeated discards, enter the amount per occurrence and the number of occurrences. Changing a quantity unit converts the existing number within that measurement type.
- Choose a Reduction target to compare assumed savings. The initial 25% is illustrative, not a recommended target or an assessment of how much waste is avoidable.
- Open Advanced and set Annual operating days to match the operation rather than automatically accepting the default 365. Optionally enter Sales during the audit in the same currency and for the same audited days.
Blank or zero sales omit the sales percentage. Invalid sales make only that percentage unavailable; the waste costs and reduction estimates remain usable. Correct the sales entry or clear it to remove the warning.
- Review the highest-cost entry in the Waste ledger against its discarded amount and purchase basis. A zero day count or zero purchase-pack quantity blocks the calculation. Correct the value identified by Check the audit; the purchase-cost figure and ledger return when the required entries are valid.
Interpreting Results:
Purchase cost lost in this audit is the estimated ingredient purchase cost represented by the recorded discards. The Annual loss badge extrapolates that amount to the selected annual operating days. The Potential saving badge is for the audit period, not the year; Potential annual saving appears in the reduction plan.
The Waste ledger ranks items from highest to lowest audit cost. Its Cost share (%) is each item's share of the total recorded purchase loss. Waste by cause adds costs under Spoilage, Preparation, Overproduction, Plate waste and Other. These are money comparisons, not comparisons of waste weight or volume.
The suggestion in Reduction plan follows the reason with the largest combined cost, which need not be the reason attached to the single largest item. It is a starting point for a trial, not a finding that the waste is preventable. Repeat the audit over comparable operating days and demand to evaluate a change.
Waste purchase cost / audit sales compares recorded waste purchase cost with sales from the same audit period. It is neither the percentage of food purchased that was wasted nor a physical waste percentage. It can exceed 100% when the recorded purchase loss exceeds the supplied sales, so check both the sales amount and the period before interpreting a high value.
An exact zero total means no purchase-cost loss was recorded. A displayed zero can also be a small amount rounded to currency precision. Zero quantities, zero prices or missing discards can produce a misleading impression of no waste. Check the completeness of the records and their purchase prices before treating zero as evidence of improvement.
Technical Details:
Purchase-cost valuation first expresses a discard as a fraction of the quantity covered by a purchase price. Multiplying that fraction by the pack cost values one occurrence; multiplying by the occurrence count values the whole entry. Comparable units and a matching food basis are essential because a unit conversion cannot supply a missing ingredient cost.
Purchase-cost valuation and operating-day estimates
For item i, the purchase-cost loss is the discarded fraction of a pack multiplied by its price and the number of occurrences.
Here qi is Discarded quantity and bi is Purchase-pack quantity after both have been converted to the same unit. The price pi is Purchase-pack cost, and ni is Occurrences in this audit. The quantity ratio has no unit, leaving ci in the selected currency.
The audit total C adds every entry's cost. With d audited operating days and a annual operating days, the daily and annual estimates are:
Cday is loss per audited operating day, in currency per day. Cyear is annualized purchase-cost loss, in currency for the entered annual operating period. The multiplier is a divided by d, not a fixed number of weeks or months. Changing either day count does not change the purchase cost already recorded in the audit.
For an entered reduction target t, the fraction used is t divided by 100. S is potential saving in the audit and R is remaining audit loss; the annual amounts use the same fraction.
Each item's target saving uses that same percentage of its own cost; there are no separate reduction rates by item or cause. A 0% target gives zero savings and leaves all loss remaining. A 100% target assigns all recorded purchase loss to potential savings and leaves zero remaining loss. Neither boundary establishes feasibility, and changing the target does not change the original costs or their ranking.
Two percentages use different denominators. The item cost share wi uses total audit loss C, while the sales percentage h uses valid positive sales V from the same audit.
When total audit loss is zero, every item cost share is set to zero. The sales percentage is omitted for blank or zero sales and is unavailable for invalid sales or a percentage too large to represent as a finite number. None of those sales conditions changes the independent purchase-cost calculations. Cause totals simply sum the entry costs assigned to each reason; changing a reason reallocates cost without changing the overall loss.
Units and purchase basis
Multiply each discarded and purchase-pack quantity by its unit factor before taking their ratio. Weight quantities are compared in kilograms, volumes in liters and counted quantities in each.
| Entered unit | Multiplier | Common unit |
|---|---|---|
| kg | 1 | kg |
| g | 0.001 | kg |
| lb | 0.45359237 | kg |
| oz | 0.028349523125 | kg |
| L | 1 | L |
| mL | 0.001 | L |
| US gal | 3.785411784 | L |
| US qt | 0.946352946 | L |
| each | 1 | each |
The ounce here measures weight, not fluid volume. Gallons and quarts are US liquid measures, not Imperial or dry measures. Weight cannot be paired with volume or count within an entry. There is no ingredient-density conversion and no conversion between raw purchase weight and cooked yield. Counted prepared portions require an ingredient cost for the same portion size and number.
The supported currencies are USD, EUR, GBP, CAD, AUD, NZD, SGD, MYR, JPY and INR. They label and format the amounts; they do not supply exchange rates or change the numerical costs.
Accepted ranges and precision
An audit needs 1 to 30 entries, each with a nonblank food or category name of at most 80 characters and a listed loss reason. The numerical limits below apply in the selected quantity units or currency.
| Quantity | Minimum | Maximum | Condition |
|---|---|---|---|
| Audited days, annual operating days and occurrences | 1 | 366 | Whole numbers; each count has its own limit. |
| Discarded quantity | 0 | 1,000,000 | Decimals are accepted, including fractions of counted portions. |
| Purchase-pack quantity | > 0 | 1,000,000 | Must be greater than zero because it is the divisor. |
| Purchase-pack cost | 0 | 1,000,000 | In the audit currency; zero prices are accepted. |
| Reduction target | 0% | 100% | Fractional percentages are accepted. |
| Optional audit sales | 0 | 1,000,000,000,000 | Blank or zero omits the sales comparison. |
Limits are inclusive except for the strictly positive purchase-pack quantity. Accepted numerical values must be finite. Occurrences count repeated discards, not necessarily separate days, so more than one occurrence can fall on an audited day. The calculated audit total must also be finite and no greater than 1,000,000,000,000 in the selected currency. This cost limit applies to the audit total, not the annualized estimate.
Calculations use 64-bit floating-point arithmetic without rounding intermediate values. Quantity displays and the sales percentage use up to six decimal places; item cost shares use up to two. Money displays use the selected currency's precision: two decimal places for the supported currencies other than JPY, which uses none. Adding rounded displayed rows can therefore differ slightly from the displayed total.
Model limits
Annual estimates hold purchase prices and waste cost per operating day constant. The reduction scenario assumes the chosen share of purchase-cost loss can be prevented and does not distinguish unavoidable waste automatically. The purchase-cost arithmetic and operating-day extrapolation are an authored budgeting model, not an official accounting standard. These are gross purchase-cost estimates, excluding labor, disposal, the costs of making changes, tax and revenue effects. They do not reconcile inventory shrinkage or calculate net profit, payback or guaranteed savings. The estimates are for budgeting and comparison, not financial advice.
Privacy Notes:
Cost calculations run in the browser, but audit inputs can be carried in the page address for restoration on reload. A populated link may include food names, quantities, purchase prices and sales figures. Treat that address as containing audit data rather than as a confidential way to store or share commercially sensitive figures.
Worked Examples:
A mixed audit with prepared portions
The illustrative seven-day audit records 5 kg of leafy greens at USD 4 per kg, 3 L of milk at USD 2 per L and 12 cooked portions with an ingredient cost of USD 2.50 each. With one occurrence per entry, the respective losses are USD 20, USD 6 and USD 30, totaling USD 56. Cooked portions rank first in the ledger. Spoilage combines the greens and milk into USD 26, while Overproduction accounts for USD 30. At 365 annual operating days, the USD 8 daily loss becomes USD 2,920 annually. A 25% target gives a potential saving of USD 14 in the audit or USD 730 annually. Those are illustrative opportunities, not measured savings.
Repeated discards with different weight units
During a six-operating-day audit, 2 kg of tomatoes are discarded on each of three occasions. The purchase price is USD 10 per 500 g pack. Since 500 g is 0.5 kg, each 2 kg discard represents four packs costing USD 40, and three occurrences produce USD 120 of audit loss. The daily loss is USD 20; with 300 annual operating days, annual loss is USD 6,000. A 20% target gives USD 24 of audit savings and USD 1,200 of annual savings, leaving USD 96 and USD 4,800 respectively. Sales of USD 1,200 for the same audit give a sales percentage of 10%. Entering the full 6 kg audit total instead requires one occurrence, not three, to avoid counting the same waste again.
References:
- Food Waste Logbook, U.S. Environmental Protection Agency.
- NIST Guide to the SI, Appendix B.8: Factors for Units Listed Alphabetically, National Institute of Standards and Technology.