Staff Theft & Voided Orders: The Restaurant Audit Trail

How do restaurants lose money to voided orders and staff theft?

Restaurants lose money when food leaves the kitchen without revenue attached to it — most commonly through voided items that were actually served, discounts applied without authority, cash sales that never reach the drawer, and stock that walks out the back door. The common thread is that each one is invisible unless the system records who did what, when, and why.

None of this is solved by suspicion. It is solved by making the ordinary path easy to record and the unusual path leave a mark.

Why are voids the classic problem?

Because a void is the one action that makes revenue disappear legitimately.

The mechanics are simple. An order is punched, the kitchen cooks it, the food is served, the guest pays cash — and then the item is voided before the bill closes. The dish left the kitchen. The money left the guest's hand. The system shows nothing was sold, so nothing is missing from the till.

Stock will eventually reveal it, because the ingredients are gone. But if nobody is reconciling stock against sales, that signal arrives months late and looks like general wastage.

What makes voids detectable is not banning them — they are necessary. It is recording them with enough structure that patterns become visible.

What should a void record capture?

Four things: what was voided, who voided it, when, and why.

The "why" is what most systems skip, and it is the one that turns a number into information. A void with a reason attached — item unavailable, guest changed mind, punched in error — can be sorted and counted. A bare void count tells you nothing.

POSFORRETAIL records voids and returns as documented events with reasons, and a return references the original transaction rather than floating as a standalone negative entry. The Enterprise plan adds a full audit trail across the system.

The management insight is always in the pattern. One void is nothing. Twenty voids a week, all by the same person, all on cash sales, all after 10pm, is a conversation. You cannot see that pattern unless every void carries a name and a timestamp.

What about discounts?

Discounts are voids wearing better clothes.

A 50% discount applied to a friend's bill costs exactly half the revenue, and unlike a void it does not even look unusual — discounting is a normal commercial activity. Restaurants that carefully monitor voids while leaving discount authority open to every user have locked one door.

The control is permissions. Not every staff member needs the ability to discount, and those who do should be doing it under their own login. POSFORRETAIL has staff roles and permissions on every plan, including Starter, so discount authority can be restricted to the people who should have it.

That single configuration change — discounts limited to supervisors — closes a large share of the exposure in most restaurants.

Does everyone logging in separately actually matter?

It is the foundation. Nothing else works without it.

A shared login means every action belongs to "the terminal", and no record can ever point at a person. Voids, discounts, refunds and price overrides all become anonymous. The audit trail exists but says nothing.

Individual logins are unglamorous and mildly annoying at a busy counter, and they are the single highest-value control in the list. Every action carries a name, and staff know it does, which changes behaviour before any investigation happens.

Every POSFORRETAIL plan includes staff users with roles and permissions — 3 users on Starter, 10 on Professional, unlimited on Enterprise.

How does stock reconciliation catch what the till misses?

Because food that left the building has to be explained by something.

If your system says you should have forty kilos of chicken and you have twenty-eight, twelve kilos went somewhere. Sales account for some. Wastage accounts for some. Whatever remains unexplained is the number worth looking at.

This only works if stock movement is recorded properly at both ends — purchases received against suppliers with documents, and adjustments recorded as documents with reasons rather than someone quietly editing a quantity. POSFORRETAIL handles purchase orders, goods receipts and stock adjustments as documented events, so a discrepancy has a trail rather than a shrug.

An honest limitation worth stating: POSFORRETAIL does not currently do recipe-level ingredient costing, so it will not automatically deplete 200g of chicken when a karahi is sold. Stock tracking is at product level. For ingredient-level control you would reconcile purchased stock against dishes sold manually, which is more work but still far better than nothing.

What about cash that never reaches the drawer?

The defence is that every sale is recorded at the moment it happens, and the drawer is counted against what the system says it should hold.

That requires accurate tender recording. A bill settled part cash, part card has to be recorded as exactly that — otherwise the drawer is legitimately wrong and a real shortage hides inside a recording error. POSFORRETAIL records payment by method against each transaction, so a mixed settlement reconciles cleanly.

Counting the drawer against an expected figure is only meaningful when the expected figure is trustworthy. Most restaurants that "cannot get the drawer to balance" have a recording problem, not a theft problem — and until the recording is fixed, actual theft is undetectable.

The controls that actually work

In rough order of value:

1. Individual logins. Every action has a name.
2. Restricted discount and void permissions. Not everyone needs them.
3. Reasons on voids and returns. Patterns need structure to be visible.
4. Accurate tender recording. A trustworthy expected drawer figure.
5. Regular stock reconciliation. Catches what the till cannot.
6. Audit trail. Available on Enterprise, for when you need the full history.

Notice that the first four are configuration, not spending. Most restaurants running a decent POS already have the capability and have not turned it on.

The management posture

The goal is not catching people. It is removing the conditions where losses go unnoticed — because most restaurant loss is not organised theft, it is sloppiness that nobody could see.

Staff who know that every void carries their name and a reason behave differently, without anyone being accused of anything.

Roles and permissions are on every plan; the full audit trail is on Enterprise at PKR 11,999 per month, alongside double-entry accounting and payroll. See pricing for the comparison — 14-day free trial, no card required. For how orders and settlement flow through the system, our restaurant workflow guide covers it end to end.