1What does theft cost a restaurant?
Nobody publishes a reliable figure for Indian restaurants, and any single percentage you read is a guess. Take an example instead: if 2% of a ₹50 lakh year walks out, that is ₹1 lakh, which can be a large share of a small outlet’s profit.
Two things keep it invisible. It is rarely one villain: it is many small mechanisms, each too small to notice on its own, such as a cancelled order here, a light portion there, an inflated invoice once a month. And the person best placed to take is usually the person you rely on most, so suspicion without records poisons the whole team.
So start from the honest point: most staff don’t steal. Controls protect the honest majority as much as they catch anyone, because when ₹40,000 goes missing and there are no records, everyone is a suspect. If you already track food cost and variance, you have half of what this guide needs.
2What are the 11 scams, and how do you catch each one?
Every scam below has the same shape: a gap between what happened and what got recorded.
| Scam | The tell | The control |
|---|---|---|
| Cancelled order, cash kept | Cancellations cluster on one person or shift | A manager’s PIN and a reason for every cancel, reported by name |
| Void after payment | Voids after settlement, or a drawer that always matches | A settled bill can’t be edited |
| The outage bill wipe | Repeated outages on the same shifts, with soft sales | An outage log, and stock counted against sales |
| Reprint resale | High reprint counts for one person | A reason for every reprint, and copies marked as copies |
| Free plates for friends | Ingredients used beyond what sales account for | No order, no food; staff meals recorded |
| Under-ringing and overcharging | Price changes, open items, handwritten bills | A printed, numbered bill for every sale |
| Portion skimming | Plates that weigh light | Recipe cards in grams, portion tools, plates weighed |
| Raw materials walking out | A stock gap in the costliest items | Weekly counts of the top ten items |
| Supplier collusion | Rates above the market, invoices above deliveries | Two quotes, and deliveries checked against the order |
| Bottle swapping at the bar | Bar takings that don’t match the room | Marked bottles, checked at every shift change |
| Discount abuse | Discounts clustering on one person, on cash bills | Approval and a reason for every discount |
Now each one properly.
1. Cancelled order, cash kept
How it works: the order is taken, the kitchen cooks it, the guest pays cash, and then the order is cancelled. The food went out, the money came in, and the record disappeared.
The tell: cancellations by person and by shift. An honest restaurant cancels rarely and at random. This scam cancels often, in a pattern, usually after the kitchen already had the order.
The control: a cancellation after the kitchen has the order needs a manager and a reason, and lands in a daily report with a name on it.
In CountStand: once a line is sent to the kitchen it can’t be edited; changing it means voiding it. A cashier can’t void without a manager’s PIN and a reason, and the void is recorded against the manager whose PIN was used. The Discounts and voids report lists every one.
2. Void after payment
How it works: the bill is settled in cash and later, at a quiet hour or the end of the shift, voided or edited down. The drawer then matches the altered record.
The tell: voids clustered after payment, or a drawer that reconciles too perfectly, night after night.
The control: a settled bill can’t be changed. Anything after payment is a separate record, with a name and a reason.
In CountStand: a settled bill can’t be changed; the till says “This bill is already settled.” Anything after that is a manager’s job and leaves its own record. In every plan, a scan every night at 1:00 am looks for a payment followed by a void on the same order, among other patterns, and raises what it finds for you to review.
3. The outage bill wipe
This one deserves the most attention, because it attacks the record itself.
How it works: someone cuts the internet: the router switched off, a cable pulled, a data pack run dry. The till carries on billing, as it should. Orders go in, food goes out, cash comes in. Then, before the line returns, the bills stored on the device are destroyed: the browser’s data cleared, or the app’s storage wiped. When the connection comes back there is nothing to send. The kitchen worked all evening; the record shows a dead shift, and the outage is its own alibi.
The tell: outages that repeat on the same shifts or under the same people; sales that dip in exactly those windows while preparation and purchases stay normal; and a cash drawer that matches a suspiciously quiet evening.
The control: two habits and one check. Write down every outage: when, how long, and who was on the till. Keep the router somewhere staff can’t reach, with a phone hotspot as the backup. And count your costliest stock every week, because the only trace an unrecorded sale leaves is the stock it used.
In CountStand: while the internet is down the till saves every action on the device and shows how many are waiting, then sends them in order, exactly once, when the line returns. A banner tells staff not to close the till while any are unsent, so an honest outage loses nothing. No till can protect a bill someone deletes before it is sent. What CountStand does is make the deletion show: stock is deducted by recipe when an order reaches the system, so food that left for a wiped bill appears at the next count as stock used that no sale explains.
4. Reprint resale
How it works: one bill is printed twice and handed to two guests who pay cash. One payment reaches the drawer and the other reaches a pocket.
The tell: reprint counts by person. Honest reprints are rare.
The control: every reprint needs a reason, is marked as a copy, and appears in a report.
In CountStand: the first print never asks for anything; every reprint asks for a reason, recorded with who and when, and the reprinted bill is marked as a duplicate.
5. Free plates for friends
How it works: food leaves the kitchen with no order at all, for friends, for family, or under a side arrangement.
The tell: you can’t see it in billing, because it never touched billing. You see it in stock: ingredients used beyond what sales account for.
The control: no order, no food. That includes staff meals, which get recorded too, so that they are visible rather than invisible.
In CountStand: the kitchen display shows what was sent from the till or the captain’s phone, and stock is deducted by recipe for every dish sent to the kitchen. A plate that left with no order shows up at the next count as stock gone without a sale.
6. Under-ringing and overcharging
How it works: two versions. Under-ringing: the guest pays for a biryani, a soft drink is rung up, and the difference is kept. Overcharging: the guest pays more than the menu price on a handwritten or spoken total.
The tell: price changes and open items in the records, and handwritten bills existing at all.
The control: prices set by the owner, a printed and numbered bill for every sale, and no handwritten totals. That is also what GST expects; see the GST guide.
In CountStand: every bill carries a consecutive serial number, and a discount needs a manager’s PIN and a reason.
7. Portion skimming
How it works: the kitchen plates a little light all evening, and the difference goes home or is sold on the side. Guests are short-changed and the stock records look almost normal.
The tell: plates that weigh light on spot checks, and complaints about portion size.
The control: recipe cards in grams, portion tools sized to them, and random plate weighs. Be clear about the limit of stock counts here: if the skimmed food leaves the building, the stock used still matches the recipes, so the count looks clean. The scale and your guests are what catch this one.
8. Raw materials walking out
How it works: the oldest one. Paneer, chicken, ghee, oil and liquor leave in bags.
The tell: a stock gap concentrated in the costliest items, and purchases rising while sales stay flat.
The control: weekly counts of your ten most valuable items, a register for anything that leaves the kitchen other than on a plate, and stock deducted as you sell, so the count has an honest baseline.
In CountStand: recipes deduct stock as orders go to the kitchen, stock counts record what is actually on the shelf, and the gap shows in rupees. In every plan, the evening brief by email lists the day’s gap, item by item.
9. Supplier collusion and inflated invoices
How it works: whoever buys agrees with a supplier on inflated rates, or on invoices for more than was delivered, and they split the difference. It is often the largest single leak, and it never touches the till.
The tell: rates creeping above the market, one supplier quietly winning everything, and invoices that don’t match what the kitchen received.
The control: two quotes for your biggest spend lines, every delivery checked against the order and the invoice, and a rota for who receives deliveries.
In CountStand: a purchase order records the quantity and the rate you ordered, so the supplier’s invoice can be checked against what was agreed.
10. Bottle swapping at the bar
How it works: a bartender brings their own bottle, pours from it as the house spirit, and keeps the takings. Your stock is untouched, so the bottle counts look fine. A variant: a premium bottle refilled with something cheaper.
The tell: bar takings that don’t match a busy room, and guests who notice the drink isn’t what they ordered.
The control: mark every bottle with the outlet’s stamp, check the stamps and seals at every shift change, keep personal bags away from the bar, and use measured pours.
11. Discount abuse
How it works: a real discount is applied to a guest who paid full price. The guest pays ₹500, the bill records a 20% “loyalty” discount, and the difference is kept.
The tell: the share of discounted bills by cashier, and discounts clustering on cash payments near the end of a shift.
The control: discounts need approval and a reason, with a daily report by person.
In CountStand: a cashier can’t discount without a manager’s PIN, every discount carries a reason recorded against the person whose PIN was used, and the Discounts and voids report lists them all. The nightly scan, in every plan, flags people whose discounts cluster.
3Why do cameras alone fail?
Cameras earn their place against walkouts and back-door traffic. But look back at the list: most of the eleven scams look completely normal on camera. A cancelled order is a person tapping a screen. An under-ring is a smiling transaction. A wipe looks like someone restarting a stuck till. Nobody watches twelve hours of footage a day, and staff learn where the cameras can’t see within weeks. Cameras answer “what happened in this incident”. Only records can answer “is something happening”.
4How does the stock method catch what cameras miss?
It is the same loop that controls food cost, pointed at a different question.
- Recipes say what each dish should use, in grams.
- Every order turns into the stock it should have used, automatically.
- A weekly count of your costliest items says what you actually used.
- The gap, per ingredient and in rupees, says where to look.
- A daily list of exceptions: cancels, voids, reprints and discounts, each with a name.
A typical finding reads like this, as an example: “Chicken: 2.3 kg used beyond what sales account for this week, mostly on Friday and Saturday dinner.” It names the ingredient, prices the leak and narrows the window before you have asked anyone a single question. Most scams on the list last exactly as long as nobody looks at that number.
CountStand’s Single plan, at ₹2,999 a month per outlet, runs this loop: recipes deduct stock as orders go to the kitchen, counts record what is on the shelf, and every cancel, void, discount and reprint carries a name and a time. Every person signs in with their own PIN; a PIN two people share is refused, and so is the PIN of someone who has left. It also brings the evening brief with the day’s stock gap and the nightly scan for void and discount patterns. To see what a leak of a few per cent means on your own sales, run your numbers through the food cost calculator.
5How do you build controls without destroying trust?
Anti-theft work can fail by producing a suspicious owner and a demoralised team, which costs more than the theft did. What works:
- Announce the system, openly. Controls installed quietly read as an accusation. Controls announced read as how the restaurant is run: “every bill is numbered, every void has a name, stock is counted every week”, said once, to everyone, on the first day.
- Let the records ask the questions. Never accuse on a hunch. A stock gap is a question (“help me understand Friday”), not a verdict.
- Make the honest path easy. Recorded staff meals. A real process for genuine cancellations. Fair wages, paid on time.
- Say so when a week is clean. A week with no unexplained gap is worth mentioning out loud.
- When you do find someone, act on evidence, calmly. Named records and a priced gap make the conversation short and factual. For anything beyond ending employment, take proper legal advice rather than improvising.
6The weekly 15-minute audit
Run it once a week, on the same day, every week. The regularity is the deterrent.
- Cancels and voids by person: is anything clustering?
- Reprints and discounts by person: the same question.
- Outages: when, how long, and who was on the till? Did sales during them look normal?
- Bill numbers: continuous, with no gaps or restarts?
- The stock gap on your ten costliest ingredients, in rupees.
- At the bar: takings against a busy room, and the bottle stamps.
- Purchase rates for your five biggest spend lines, against last month.
- One plate, chosen at random, weighed against its recipe card.
- The drawer: each night’s close of day, matched, short or over.
Fifteen minutes is enough when the records collect themselves. If any of these takes more than a couple of minutes, that is a tooling problem, and you can see the records in a demo.
7Questions owners ask
Not from instinct, from gaps: stock used beyond what sales account for, cancels and voids clustered on one person or shift, sales that dip during outages, and purchase rates creeping while sales stay flat. Look at those weekly before you suspect anyone.
There is no reliable published figure for Indian restaurants, so treat any single percentage as a guess. Your own number can be measured: the stock you used beyond what sales account for, priced in rupees, every week.
No. Cameras deter walkouts, but most theft happens inside the billing records, through cancels, voids, under-rings and discounts, and it looks normal on video. The combination that works is cameras, named records on the till, and a weekly stock count.
Staff cut the internet, keep billing, take cash, then clear the bills stored on the device before the line returns, so the sales never reach the records. The defence is an outage log, a router out of reach, and a weekly count, because the food sold still left the stock.
Not on suspicion alone. Gather the records first, with dates, names and amounts, then have a calm, factual conversation. For ending employment or recovering money, take proper legal advice for your state.