Inventory variance is the difference between the stock your recipes and sales say you should have used and the stock you actually used. It is the single most honest number in a restaurant, because it does not care about excuses. If your dishes should have consumed 8 kg of paneer this week but the shelf says 10 kg is gone, that 2 kg gap is your variance, and it is quietly eating your margin. This guide shows Indian restaurant owners how to find it, read it, and close it.
Theoretical versus actual usage
Variance analysis rests on comparing two numbers. Theoretical usage is what your recipes say you should have consumed, given everything you sold. Actual usage is what a physical stock count shows really left your store. The gap between them is where the money hides.
- Theoretical usage: Sales multiplied by each dish’s recipe, item by item.
- Actual usage: Opening stock plus purchases minus closing stock.
- Variance: The difference, ideally small and stable, item by item.
Getting theoretical usage right depends on recipe-level tracking, which is where a proper restaurant inventory management approach earns its keep. Without recipes tied to sales, you are guessing.
Where variance actually comes from
A gap does not tell you the cause, only that one exists. Your job is to narrow it down, and the usual suspects are a short list.
The common causes
- Over-portioning: Cooks plating more than the recipe specifies, especially on proteins and rice.
- Wastage: Spoilage, spills, burnt batches, and trimming losses.
- Receiving errors: Short deliveries recorded as full, or wrong weights.
- Unrecorded sales: Staff meals, comps, and tastings that never hit a bill.
- Theft: Stock leaving without any corresponding sale.
Most owners assume theft first, but in practice over-portioning and wastage explain the majority of everyday variance. Chasing the wrong cause wastes effort and damages trust, so let the item-level numbers point you.
Count consistently or the number lies
Variance is only as good as your stock count. Inconsistent counting creates phantom variance that sends you chasing problems that do not exist.
- Same time, same person: Count at a fixed point in the cycle, ideally the same trained staff member.
- Same units: Count in the units your recipes use, so kilograms match kilograms.
- Count high-value items often: Proteins, cheese, and oil deserve more frequent counts than salt or flour.
Focus on what moves money
You do not need to chase a 50 gram variance on coriander. Rank your items by rupee value of the gap, not by quantity. A small percentage variance on chicken or paneer costs far more than a large one on a cheap staple, so spend your attention where the rupees are.
Turn variance into a weekly habit
Variance is not a monthly autopsy, it is a weekly steering signal. Reviewed often, a rising gap on one item is a small, fixable problem. Left for a month, it becomes a mystery no one can unwind because too much has changed.
- Review weekly: Look at your top twenty items by value every week.
- Investigate outliers only: Chase the two or three worst gaps, not every line.
- Close the loop: Fix the cause, then confirm the variance falls the next week.
If you run several locations, compare variance across them. An outlet with a consistently higher gap on the same dish points to a specific process or person, and central multi-outlet management makes that comparison straightforward. Inventory variance will never reach zero, and it does not need to. A small, steady, understood gap is a sign of a controlled kitchen. A large or growing one is your business telling you, in the clearest terms it has, exactly where to look.
Frequently asked questions
What is a normal level of inventory variance?
There is no universal figure, but a small, steady, and explainable gap is normal and healthy. What matters is the trend: a variance that is stable and understood signals control, while one that is large or growing signals a problem worth investigating.
Is variance always caused by theft?
No. Owners often assume theft first, but over-portioning and wastage explain the majority of everyday variance. Let the item-level numbers guide you, because chasing the wrong cause wastes effort and damages trust with your team.
How do I calculate theoretical usage?
Multiply everything you sold by each dish’s recipe, item by item, to get the quantity of each ingredient your sales should have consumed. This depends on accurate recipes tied to your sales data, which is why recipe-level tracking matters.
How often should I check variance?
Treat it as a weekly steering signal rather than a monthly autopsy. Reviewing your top items by value each week keeps a rising gap small and fixable, whereas a month’s delay makes the cause far harder to trace.
