Restaurant Recipe Costs Wrong or Zero: How to Fix Each One

A wrong recipe cost is a setup problem, not a maths problem
A restaurant recipe cost showing zero or reading wrong almost always comes from how the ingredient was set up, not from a broken calculation. A dish that should cost $4.20 shows $0.00 the moment one ingredient has no received purchase order behind it. A 25 kg sack of flour entered as 1 kg throws off every recipe that touches it. This article shows the six setup mistakes that make a recipe cost wrong, and the fix for each one.
The symptom looks like a software bug, so operators go hunting for one. The cause sits one level down, in the ingredient, its units, or its supplier packaging. You can check and correct every one of these causes yourself.

Six reasons your recipe cost reads wrong or zero
Work down the list and match each cause to what you see on the screen.
- The cost reads zero because the ingredient has no purchase history. A plate that should cost $4.20 shows $0.00. The ingredient has never been priced, because no purchase order for it was received and matched, so the system has nothing to cost from. Check that the purchase order was received and matched first, because that is usually the whole problem. If you genuinely have no purchases yet, give the ingredient a fixed cost per unit in your recipe costing setup. That fixed price stands in for the purchase-order price, so the recipe reads a real number from day one.
- The base unit and the buying unit are mixed up. Every recipe that uses the ingredient is off by the same factor. The base unit is how you count and cost the ingredient, such as grams or millilitres. The buying unit is the pack you order from the supplier, such as a case or a sack. Enter one where the other belongs, and every cost built on it inherits the error. Set the base unit to how you use the ingredient in recipes. Set the buying unit to how the supplier sells it, and let the conversion between them do the maths.
- The pack-to-base conversion ratio is wrong. One ingredient costs far too much or far too little while the rest look fine. The ratio between the buying unit and the base unit is wrong. Map a 25 kg sack of flour as 1 kg, and every recipe that uses flour inflates. Map a loaf that yields 20 slices as 1 slice, and the bread cost comes out wrong. Open the ingredient and correct the conversion so one buying unit equals the real number of base units.
- The same ingredient exists two or three times, once per pack size. The cost jumps around depending on which supplier delivered last. The same olive oil might arrive as a 5 litre case from one supplier and a 1 litre bottle from another. Operators often create a separate ingredient for each pack, and that splits the moving-average cost across the duplicates. Keep one ingredient master and link every supplier product and pack size to it, so all purchases feed one moving average and recipes read a single blended cost.
- The cost is years old and no longer matches what you pay. Food cost on paper sits inside your 28% to 32% target while the bank balance disagrees. The recipe was costed once and never refreshed, so it still carries last year's prices. Let supplier price updates cascade into the ingredient's average cost, or record a recent purchase so the cost catches up. Either way the recipe cost and your reports move with the prices you actually pay.
- A prepped sub-recipe reads zero even though its ingredients are costed. A sauce or a batch prep shows no value in a dish or a stock count. The sub-recipe has ingredient costs but no yield set, so there is nothing to divide the cost across. Cost the sub-recipe the way you cost any recipe, then set how much it yields. Each portion then carries its share of the batch cost into the dishes that use it.

Which cause to check first
Start with the symptom on the screen, because the reading itself points at the cause. Match what you see to the most likely cause below, then check that part of the setup first.
| What you see | Most likely cause | Check first |
|---|---|---|
| Cost is exactly zero | No purchase history, or an uncosted sub-recipe | The item's receiving, and the sub-recipe's yield |
| Cost is wrong but not zero | Base and buying units mixed up, or a bad conversion | The item's units, and its pack-to-base ratio |
| Cost no longer matches what you pay | Duplicate items, or prices never refreshed | One ingredient master per item, and recent purchases |
Fix the one that matches what you see, re-cost the affected recipes, and the food cost percentage you report starts matching the money you actually spend.


.jpg)




