Restaurant theft control that shows shrinkage in rupees
Theft rarely looks like theft. It looks like a stockroom that is lighter than the sales say it should be, and the gap has a price.
CountStand catches shrinkage by comparing what you should have used against what you actually did. Every sale deducts ingredients by recipe, so the system knows the theoretical usage; a physical count gives the real number; the difference is variance, shown in rupees against the ingredients where it hurts most. Over-portioning, unrecorded staff meals and bulk-item pilferage stop being a vague monthly feeling and become a named, priced line you can act on this week.
How the gap gets caught
Recipes and counts, turned into a number you can confront.
Theoretical usage from every sale
Because each dish carries a recipe, selling it deducts its ingredients. The system always knows what the day’s sales should have consumed, the baseline theft hides behind.
Variance priced to the ingredient
A physical count meets the theoretical figure and the difference is costed in rupees, ranked so the oil, cheese or chicken that is bleeding shows up first.
Caught before month-end
Variance surfaces continuously, not in a quarterly stock-take, so a leak is a this-week conversation with a named item, not a year-end write-off.
Over-portioning made visible
A cook adding ten grams a plate across three hundred plates is three kilos a day. Recipe-versus-actual is the only lens that makes that pattern legible.
How do you prove pilferage without watching every shift?
You cannot stand over every station, and CCTV tells you a hand moved, not that a kilo of paneer left unpaid. The proof that stands up is arithmetic: recipes multiplied by units sold give the quantity that should have gone out; a count gives what did. When the counted stock is short of the theoretical figure by more than natural wastage, that gap is shrinkage, and it has a rupee value.
CountStand does that arithmetic continuously so the evidence is ready before the loss compounds. You are not accusing anyone on a hunch, you are showing a costed variance on a specific ingredient and asking why.
Is variance always theft?
No, and treating it that way burns trust. Variance is the sum of theft, over-portioning, spoilage, unrecorded staff meals and sloppy counting. The value of putting it in rupees per ingredient is that it points you at the cause: a steady daily gap on cooking oil reads differently from a one-off spike on a festival weekend.
The tool’s job is to make the leak measurable and specific. What you do with it, retrain a station, tighten a recipe, change a supplier, or have a hard conversation, stays a management decision, now backed by a number instead of a suspicion.
Asked by owners like you
How does CountStand detect restaurant theft?
It compares theoretical ingredient usage (recipes times units sold) against a physical count. The shortfall beyond normal wastage is variance, priced in rupees per ingredient, the signature of pilferage or over-portioning.
Does it show the loss in rupees?
Yes. Variance is costed and ranked by ingredient, so the item bleeding the most money appears first, rather than a vague sense that stock is short.
Will I have to wait for a month-end stock-take?
No. Recipe-linked deduction runs on every sale, so variance surfaces continuously and a leak becomes a this-week conversation, not a year-end write-off.
Is anti-theft variance an add-on?
No, it is part of CountStand from ₹999/mo per outlet, with a 30-day free trial and no card.
Put a price on what is going missing
See variance in rupees on your own recipes, start free for 30 days, no card.
30-day free trial · No card · From ₹999/mo per outlet