Restaurant Void Tracking: Investigate Spikes Without Jumping to Conclusions

A spike in voids is a reason to inspect the records. It is not a diagnosis. Order corrections, menu setup, service problems and misuse can produce similar-looking totals, and a small number of transactions can make a percentage swing sharply.

The goal of restaurant void tracking is to identify the pattern, preserve the evidence and choose an appropriate response.

Define what your POS calls a void

Do not assume every system uses void, refund, discount and comp in the same way. Check whether the event cancelled an item, reversed a payment or reduced a completed check. Decide whether you are measuring void count against order count or void value against a stated sales base, and use that definition consistently.

Lightspeed, for example, documents discounts and corrections separately within its reporting. That illustrates why operators should use their own system's definitions rather than a universal label. Lightspeed report categories.

Establish a location-level baseline

Compare similar dayparts and service formats. Review both count and value. Look for changes by item, reason code, terminal or approval workflow. Do not treat a fixed percentage as the line between harmless corrections and abuse. A low group average can also hide an important local pattern.

Keep sparse data visible. One large correction during a quiet service can look dramatic without representing a recurring issue.

Investigate in a useful order

1. Confirm the report period and that transactions are not duplicated.
2. Read the reason and approval trail for the flagged items.
3. Check for menu-button errors, duplicated orders or known service incidents.
4. Ask the manager for context and supporting records.
5. Where cash is relevant, reconcile the related transaction and cash records.
6. Record the finding and follow-up rather than leaving an accusation in a chat.

A balanced drawer does not rule out misuse. A short drawer does not prove it. Preserve original logs and limit employee-level information to people responsible for review.

Match the action to the cause

A repeated modifier correction may call for POS setup or training. Missing approval records may call for a workflow review. Unexplained transaction activity may require escalation through the business's established investigation process.

Earlier review can help stop repetition, but next-day analysis still matters. It can identify recurring causes, recover documentation and improve controls for future shifts.

Measure the follow-through

After a change, compare equivalent periods and check whether activity moved into another category such as discounts. A lower void total alone is not proof that profit improved.

Define the rate and keep a review log

Two possible definitions are void events ÷ orders × 100 and voided value ÷ stated sales base × 100. They answer different questions; the count rate can be misleading if one order has multiple void events. State whether the value base includes the voided amount and keep the definition stable. These are measurement choices, not acceptable-rate benchmarks.

The source-backed review findings illustrate why transaction context and missing records matter. For the next operating decision, use the location-level profit review approach to connect the issue to an owner and a later check.

Follow the void finding through to a result

Marty is a managed profit-control layer: Find → Assign → Follow up → Verify. The paid Cash Recovery Plan establishes what to watch first, with evidence, owners, actions and a 30-day plan. Delivery is seven business days after required access is complete; read-only access and the flat fee are confirmed first.

Optional Managed Profit Control continues the agreed checks, manager alerts, follow-up, escalation and verification. Start the Cash Recovery Plan.