Theoretical vs actual consumption
The recipe says one thing; your kitchen consumes another
Compare what you should have consumed with what you actually did, by dish and by site.
What theoretical vs actual consumption is (and why it separates the profitable groups from the rest)
Theoretical consumption is what your operation should have used: the sales recorded at the POS multiplied by each dish's recipe costing. Actual consumption is what really left the storeroom, measured through purchases, stock counts and transfers. The gap between the two is the consumption deviation — and that is where the margin leak lives that no sales report will ever show: generous portions, unrecorded waste, outdated recipe costings, theft or stock-count errors. In multi-site groups the comparison is even more revealing: we have measured food cost deviations of more than 1.5 points between sites working with the same menu. Measuring this gap continuously, by ingredient and by site, is what turns food cost from a number you observe into a lever you manage. The full guide to theoretical vs actual consumption →
Where does the gap between theoretical and actual come from?
Four causes explain almost all of the difference — and each one is fixed differently, which is why they must be told apart.
Inconsistent portioning
The recipe says 180 g; the cook on duty serves 200. Twenty grams per plate, multiplied by hundreds of covers and several sites, is an invisible extra cost that only appears when theoretical and actual are compared. Food cost per location →
Inventory that lies
If counts are irregular or the theoretical stock cannot be trusted, actual consumption is calculated on sand. Without reliable inventory there is no comparison worth making. Why your inventory lies →
Outdated recipe costing
If the recipe's cost or grammage no longer reflects real purchasing and real kitchen practice, the "theoretical" is born wrong and the measured deviation means nothing. The cost of outdated recipe costing →
Unrecorded waste and movements
What gets thrown away, given away or transferred between sites without a record shows up as phantom consumption. Recording in the moment — not reconstructing at month end — is what separates useful data from noise. Goods transfers done right →
How to measure it continuously, without waiting for month end
Three pieces feed the comparison — connected to your POS and ERP, without replacing them.
Kitchen
Living recipe costings: grammages, yields and costs updated with the real price of every delivery note. The theoretical side is computed on true data. Kitchen →
Inventory
Guided counts on a mobile app, stock per site and movement traceability: actual consumption stops depending on the monthly close. Inventory →
Groups
The deviation, comparable across sites: which site deviates, in which product family and since when — so you correct where it matters. Groups →
Results measured with clients
Data from real projects with multi-site groups, measured against each client's own baseline.
>1.5 pts
of food cost deviation between sites with the same menu — what this comparison uncovers
−20-30%
waste when the deviation is measured and its cause corrected in production
1-3%
of purchased volume in delivery-note deviations that pollute actual consumption if left unvalidated
Your food cost already tells you how much you lose — theoretical vs actual tells you where
Request a Free DemoFrequently asked questions about theoretical vs actual
How is theoretical consumption calculated?
By multiplying each dish's sales (recorded at the POS) by its recipe costing: if you sold 40 portions and each takes 180 g of tenderloin, theoretical consumption is 7.2 kg. Added up by ingredient and period, it tells you what should have left the storeroom. Its reliability depends on two things: well-recorded sales and up-to-date recipe costings.
And actual consumption?
With the stock equation: opening inventory + purchases (validated delivery notes) − closing inventory ± transfers. That is why actual consumption is only as good as your counts and your goods-in: an irregular inventory or an unvalidated delivery note distorts it. With guided counts and reconciled goods-in, the figure computes itself.
What deviation is normal, and when should I worry?
There is always a physiological deviation — kitchen trim, rounding — but it should be stable and known. The alarm signals are the trend and the difference between sites: if two sites with the same menu drift more than 1.5 food cost points apart, there is a specific operational cause to find, not bad luck.
How often should theoretical and actual be compared?
The monthly close arrives too late: the first week's deviation is already unrecoverable. With the data connected — sales, recipes, delivery notes, counts — the comparison can be weekly or even daily by product family, and the correction lands while it can still change the month's result.
Does this replace my ERP or POS?
No. Controliza reads sales from the POS, validates purchases at goods-in and guides the counts; with that it builds the theoretical-vs-actual comparison that neither the POS nor the ERP does on its own. Both remain your sales and accounting systems.
Results measured with active Controliza clients, against each client's own baseline.
