★★★★★Bespoke software for B2B·One-off build fee, low monthly retainer·You own the software

Sector

Restaurant inventory management: controlling food cost with real numbers

Restaurant inventory management is really food cost control wearing a stock system's clothes. Counting deliveries in and stock on the shelf tells you what you've got, but not why your food cost percentage is drifting - for that you need recipe costing and yield tied to every dish sold.

Haystak · 12 August 2026 · Updated 12 August 2026 · 8 min read

A chef checking ingredient stock levels in a restaurant kitchen store

Restaurant inventory management has to connect three things that are usually kept separate: deliveries coming in, ingredients being used against recipes as dishes are sold, and physical stock actually counted in the kitchen. Most restaurants track the first and last of those reasonably well. It's the middle one - what a recipe should have used, compared with what actually left the store - that tells you where food cost is really going.

A restaurant losing margin on food cost almost never has a delivery problem. It has a portioning, waste or recipe-accuracy problem that a simple stock count won't reveal on its own, because the stock is genuinely gone - it's just gone in a way nobody's measuring.

Theoretical usage vs actual usage

Theoretical usage is what a recipe says an ingredient should consume, multiplied by how many of that dish were sold. Actual usage is what genuinely left the store, measured by stock counts and deliveries. The gap between the two - the variance - is where over-portioning, waste, spoilage or theft shows up, and it's the single most useful number in restaurant inventory management.

MeasureWhat it tells youWhere it comes from
Theoretical usageWhat ingredients should have been used, based on recipes and salesRecipe cost card x dishes sold
Actual usageWhat ingredients genuinely left the storeOpening stock + deliveries - closing stock
VarianceThe gap between the two, and where the problem sitsActual usage minus theoretical usage

Recipe costing has to be kept current

A recipe cost card is only useful if it reflects the actual recipe being cooked and the current ingredient price. Menus change, chefs adjust portions, and ingredient prices move - if the cost card isn't updated alongside those changes, every theoretical usage figure calculated from it drifts from reality, and food cost percentage reporting starts telling you a story that doesn't match what's happening in the kitchen.

  • Update recipe cost cards whenever a recipe or portion size genuinely changes, not on a fixed schedule regardless.
  • Refresh ingredient costs against actual supplier invoices, not list prices that may not reflect what you're actually paying.
  • Cost sub-recipes (a house sauce, a stock, a marinade) properly rather than treating them as a fixed, unchanging cost.
  • Review high-cost or high-volume dishes first if you can't cost the whole menu at once.

Yield and prep loss

A kilogram of raw fish or a whole vegetable rarely turns into a kilogram of usable product once it's trimmed, filleted or peeled. Yield percentage - how much of a raw ingredient is actually usable after prep - needs to be built into recipe costing, or theoretical usage will always understate what a dish genuinely costs to make, and margin will look better on paper than it actually is.

Waste and spoilage need recording, not just accepting

Some waste is unavoidable, but if it isn't recorded separately from normal usage it gets absorbed silently into the variance figure, making it look like a portioning problem rather than a waste problem. Recording waste at the point it happens - a dropped dish, spoiled stock, a failed prep batch - with a reason, is what turns a vague variance figure into something you can actually act on.

Stock counts across a working kitchen

Unlike a warehouse, a kitchen can't easily close for a full stocktake, and ingredients move in and out constantly during service. Regular, focused counts of high-value or fast-moving items - meat, fish, alcohol - done at a consistent time, usually work better than an infrequent full count of everything, in the same way cycle counting is generally more practical than an annual stocktake for any business that can't stop trading to count.

Multi-site restaurant groups

Running more than one site adds central purchasing, supplier consistency, and comparing food cost percentage and variance across sites to spot which kitchen is under control and which isn't. That comparison is only meaningful if every site is costing recipes and recording waste the same way - inconsistent recording between sites is a common reason head office numbers don't match what any one kitchen manager believes is true.

Off-the-shelf platforms vs a bespoke build

Established restaurant management and inventory platforms handle recipe costing, theoretical usage and multi-site reporting well, and are the sensible starting point for most restaurant groups. Where they run into limits is unusual supply arrangements, complex central production kitchens supplying several sites, or integration with a bespoke booking or delivery system that a standard platform doesn't support out of the box.

In those situations, a bespoke system or integration built around your actual kitchen and supply process is usually more reliable than forcing an unusual setup through a standard product. Get in touch and tell us how many sites you run and where your current food cost reporting stops being trustworthy.

✦ Where this fits

More on this from us: our bespoke systems built round your process.

Questions we get asked

Common questions

What's the difference between theoretical and actual food usage?

Theoretical usage is what recipes say should have been consumed based on dishes sold. Actual usage is what genuinely left the store, based on deliveries and stock counts. The gap between them is the variance worth investigating.

How often should recipe costs be updated?

Whenever a recipe, portion size or ingredient price genuinely changes. A cost card that isn't kept current will quietly understate or overstate food cost until it's next reviewed.

Why does yield percentage matter in recipe costing?

Because raw ingredients lose weight or volume during prep. Without a yield percentage built into the cost card, theoretical usage understates the true cost of a dish.

Should waste be recorded separately from normal stock usage?

Yes. Unrecorded waste gets absorbed into the variance figure and makes a waste problem look like a portioning problem, or the other way round.

How often should kitchen stock be counted?

Rolling counts of high-value items like meat, fish and alcohol, done regularly, tend to work better than one infrequent full stocktake for a kitchen that can't close to count.

Does a multi-site restaurant group need a different approach?

The principles are the same, but every site needs to cost recipes and record waste consistently, otherwise comparisons across sites and head office reporting won't be reliable.

Food cost drifting and you can't see why? We'll tell you what we'd build.

Tell us how recipes, usage and waste are currently tracked and we'll tell you where the variance is likely coming from and whether a standard platform will fix it.

No pitch deck · We map your process · You own the software