How to control food waste and inventory shrinkage in your restaurant
Food cost leaks out three ways — spoilage, over-prep and shrinkage. Here's how to find the gap between what you should have used and what you actually did, and close it.
Food cost is where thin restaurant margins are won or lost, and most of the loss is invisible — it doesn’t show up as a line item, it just quietly disappears. The fix isn’t buying cheaper; it’s stopping the leaks. And there are only three of them.
The three buckets of loss
Every dollar of wasted food falls into one of these:
- Spoilage — product that expires before it sells. Over-ordering, poor rotation, bad storage.
- Over-production — prepping or cooking more than demand. Guesswork prep, oversized batches.
- Shrinkage — theft, over-portioning, comps and errors that never get recorded.
You can’t fix what you can’t separate. The first job is knowing which bucket is bleeding most.
Find the gap: theoretical vs. actual
The single most useful number in food cost is the variance between theoretical and actual usage. Theoretical is what your recipes say you should have used for the sales you made; actual is what a physical count says you really used. The difference, in dollars, is your waste and shrinkage. Measure it, and the vague problem of “food cost is high” becomes a specific, fixable list.
Recipe-based depletion and par levels
This is the engine. Tie every menu item to a recipe, and each sale automatically deducts its ingredients — giving you live theoretical usage without manual tallying. Set par levels so the system flags items before you run short, and ordering stops being a guess. Now your counts have something to be measured against.
Prep discipline: FIFO and portioning
Two low-tech habits move the needle hard. FIFO (first in, first out) rotation kills spoilage by making sure older product sells first. Portion control — scoops, scales, standardized builds — kills the silent over-portioning that inflates cost a few grams at a time, all day long.
Log the waste
What gets logged gets managed. A simple waste log — what was thrown out, why, and roughly how much — turns spoilage and over-prep from a feeling into a pattern you can act on. A week of honest logging usually reveals one or two repeat offenders you can fix immediately.
Tighten the shrinkage controls
Shrinkage hides in voids, comps and uncounted portions. Watch the patterns: who’s voiding, when comps spike, where counts drift. The point isn’t suspicion — it’s that unrecorded giveaways and errors are real cost, and visibility alone tends to shrink them.
Prep to the forecast, not to habit
Over-production is really a forecasting problem. Your POS sales history tells you what actually sells, by day and daypart — so you can prep to expected demand instead of to “what we always make.” Less over-prep, less spoilage, same service.
Where KPOS fits
KPOS supports recipe-based depletion, par levels and low-stock alerts, so usage tracks automatically against sales and variance becomes visible instead of vanishing. That’s the foundation a real waste program needs. For the broader system view, see our restaurant POS buyer’s guide or request a quote.
Frequently asked questions
What causes the most food waste in restaurants?
Three buckets: spoilage (food that expires before it's sold), over-production (prepping or cooking more than demand), and shrinkage (theft, over-portioning, errors and unrecorded comps). Most kitchens have all three; the only way to know the mix is to measure, because each is fixed differently.
What's the difference between theoretical and actual food cost?
Theoretical food cost is what your recipes say you should have used for the sales you rang up. Actual food cost is what your inventory counts say you really used. The gap between them — the variance — is your waste and shrinkage, in dollars. Shrinking that gap is the whole game.
How does recipe-based inventory help reduce waste?
When each menu item is tied to a recipe, every sale automatically depletes the right ingredients. That gives you a live theoretical usage to compare against real counts, flags items running low before you're caught short, and turns 'we ran out' and 'where did it go' from mysteries into numbers.
How often should I count inventory?
Count high-cost and high-theft items most often — often weekly, sometimes daily for the few items that drive cost. A full count is commonly weekly or monthly. The right cadence balances the labor of counting against how fast a problem would otherwise hide; high-variance items earn more frequent counts.
Does KPOS track inventory and waste?
Yes. KPOS supports recipe-based depletion, par levels and low-stock alerts, so usage is tracked automatically against sales and you can see variance instead of guessing. That's the data a waste-reduction program runs on.
See KPOS in your restaurant
One AI-powered platform for ordering, payments and operations.
Request a Demo