Voids and comps
Voids cancel an order before payment; comps remove a paid item, usually as a goodwill gesture. Both are leakage points if uncontrolled — every void/comp should require a reason code and manager approval, and aggregate trends should be reviewed weekly.
Voids and comps in day-to-day operations
Operators meet voids and comps at three moments: when a system is first configured, when a second outlet opens, and when margin is reviewed. At each point the practical question is not the definition but who owns it, where the data lives, and how quickly a discrepancy surfaces.
If voids and comps lives only in a spreadsheet or in a manager's head, it drifts. When it sits in the operating system alongside tickets, recipes, payments and delivery commission, a discrepancy shows up the next morning instead of at month end — and that gap is where the money is.
LOOP handles voids and comps inside the same POS, KDS and inventory platform, running on devices you already own rather than dedicated hardware. Browse the full F&B glossary or see LOOP pricing.
What is Voids and comps used for in F&B operations?
In multi-outlet restaurant and F&B operations, voids and comps is an essential component — directly affecting service speed, order accuracy and margin. See the related terms below to understand where it fits in the broader stack.
How does LOOP support Voids and comps?
LOOP supports voids and comps natively in its POS + KDS + inventory platform for Vietnamese F&B chains — no plugin or third-party integration required. It's one reason multi-outlet operators pick LOOP as their primary operations system.