DakaarAsk any owner who has run a restaurant for more than a year and they will tell you: the menu is not where you lose money. You lose it in the gap between what the kitchen cooked and what the cash drawer collected. Most leakage is small, daily, and invisible — ₹300 here, a cancelled ticket there — which is exactly why it compounds into lakhs over a year. Here are the seven classic leaks, and the specific evidence trail that catches each one.
1. The KOT that never becomes a bill
Food goes to the table, the guest pays cash, the order is quietly deleted before billing. The kitchen worked, the ingredients are gone, the till shows nothing. The catch: a report listing every KOT that was fired but never attached to a settled bill. If your system can delete an order without leaving a trace, you cannot catch this — which is why an append-only audit trail matters more than any camera.
2. The cancelled bill after payment
Bill printed, guest pays, bill cancelled after they leave, cash pocketed. The catch: bill cancellations should require a manager PIN and a typed reason, and the day-end report should show every cancellation with who authorised it. A pattern of one cashier cancelling 3× more than others answers itself.
3. The quiet discount
A 20% "friends" discount applied to full-price customers, with the difference pocketed. The catch: a discount report grouped by employee. Healthy restaurants show discounts clustered around genuine campaigns; leaks show up as one person's steady drip.
4. Items added after the KOT, never entered
The waiter takes a verbal add-on order — two more drinks — relays it to the kitchen verbally, collects for it in cash. The POS never saw it. The catch: a hard rule that the kitchen cooks only from printed KOTs or a kitchen display ticket. No paper, no plate. This is an operations rule, but the system has to make following it effortless — instant KOT printing and a kitchen display screen remove the excuse.
5. The edited KOT
Four plates fired, two "removed" after cooking, two sold off the record. The catch: KOT edits after firing should print a "what changed" slip in the kitchen and appear in an edits log with reasons. The kitchen crew themselves become your verification layer, because their printed record disagrees with a falsified one.
6. The shared login
When everyone bills as "Cashier", every other report on this list loses its meaning. The catch: individual PINs, a role system that limits who can discount or cancel, and per-cashier sales reports. Accountability starts with attribution.
7. The cash drawer that "almost" matches
₹200 short most days is not bad arithmetic, it is a salary supplement. The catch: a proper shift system — opening float declared, drops recorded, drawer counted at close, variance computed automatically and logged per cashier. People behave differently when the variance has their name on it.
The one habit that ties it together
None of these reports help if nobody reads them. The owners who actually stop leakage spend five minutes every morning on yesterday's exceptions: cancellations, edits, discounts, unbilled KOTs, drawer variance. That is the entire routine. Dakaar POS bundles exactly that into one Leakage report, and you can check it from your phone — the cloud dashboard shows the same numbers wherever you are. Five minutes a day, and the quiet ₹300s stop being quiet.