Key takeaways
- Comps, voids and discounts are normal tools of hospitality, but without rules and reports they become the easiest way for margin to leak.
- Use reason codes and approval levels in the POS, and review totals daily and by employee weekly.
- The strongest warning signs are voids after an item was sent, discounts on cash payments and one person far above the team average.
- Track loyalty and promotional discounts separately; rewards influence the choices of 61% of delivery customers[1].
Why small adjustments add up
A comp for a slow entree, a void for a mistaken order, a discount for a regular: each one is small and most are justified. Added together over a month they can rival the profit line. Food and labor each take roughly 33 cents of every sales dollar[2], and 42% of operators reported that their restaurant was not profitable in 2025[3]. In that environment, leakage that goes unmeasured is leakage that goes unmanaged.
The goal is not to stop staff from taking care of guests. It is to make every adjustment visible, give it a reason and make sure the right person approved it.
Know which is which
- Comp: an item given free after it was made and served, such as a dessert for a birthday or a dish taken off the bill after a complaint.
- Void: an item removed before payment. A void before the item is sent to the kitchen is usually an ordering correction; a void after it is sent means food was made and not paid for.
- Discount: a reduction in price, by percentage or amount, such as a staff discount, a loyalty reward or a promotion.
- Refund: money returned after payment, often for a takeout or delivery order.
- Employee meal: food given to staff under your meal policy, rung in so it is counted.
Each has a different cause and a different control, so your POS should record them separately.
Set a policy
| Adjustment | Who can apply it | Approval needed | Reason code required |
|---|---|---|---|
| Void before send | Server or bartender | None | Yes |
| Void after send | Manager only | Manager login | Yes, plus note |
| Comp up to one item | Server | Manager login | Yes |
| Comp of a full check | General manager or owner | Owner review next day | Yes, plus note |
| Staff discount | Manager | Manager login | Staff name |
| Promotional discount | Server, from preset buttons only | None | Promotion code |
| Refund | Manager only | Manager login | Yes, plus original check |
In this Example, the rules are tight where the risk is high, such as voids after send and refunds, and simple where the risk is low. Adapt them to your team size: in a small restaurant the owner may be the only approver.
Reason codes that tell you something
Keep the list short so staff use it properly: wrong item ordered, kitchen error, quality complaint, long wait, guest changed mind, birthday or celebration, manager hospitality, staff meal, training, promotion. Avoid a catch-all such as "other" without a required note, or that code will soon hold most of your comps.
Configure the POS
- Give every employee a unique login and never share manager cards or codes.
- Require a manager login for voids after send, comps, refunds and open-price items.
- Remove the ability to delete items from a closed check.
- Use preset discount buttons for promotions instead of manual percentage entry.
- Turn on the comp, void and discount report by employee and by reason, and schedule it to email daily.
Review daily and weekly
Daily, on the flash report
Check total comps, voids and discounts in dollars and as a share of sales, with a note for any single large adjustment.
Weekly, by employee
Compare each person's adjustments with their sales and with the team average over the same shifts.
Weekly, by reason
Look for reasons that are growing, such as kitchen errors or long waits, which point to operational problems.
Monthly, by manager
Review who approved what. A manager who approves far more than peers may be under pressure or may be the problem.
Follow up
Talk to the person, fix the process, and note the outcome so you can see whether it changed.
Worked Example: reading a weekly void report
| Server | Shifts | Net sales | Voids after send | Comps | Discounts | Total as share of sales |
|---|---|---|---|---|---|---|
| Server A | 5 | $8,900 | $48 | $62 | $70 | 2.0% |
| Server B | 5 | $9,400 | $35 | $55 | $64 | 1.6% |
| Server C | 4 | $7,200 | $212 | $40 | $180 | 6.0% |
| Server D | 5 | $8,600 | $52 | $96 | $58 | 2.4% |
In this Example, Server C stands out with high voids after send and high discounts on fewer shifts. That is a reason to look closer, not proof of wrongdoing. The manager pulls the individual checks and finds most voids on closing shifts, several on checks later paid in cash, and discounts applied after the guest left. Those patterns justify a direct conversation and tighter approval on closing shifts. Server D's higher comps turn out to come from one table with a genuine complaint, which needs no action.
Red flags
- Voids after an item was sent, especially on checks later paid in cash.
- Discounts or comps applied after payment or after the guest left.
- The same reason code used repeatedly by one person.
- Many small voids rather than a few large ones, which can stay below a review threshold.
- High adjustments on shifts with no manager on site.
- Comps with no matching guest complaint or remake in the kitchen.
- A server whose sales per guest are much lower than peers in the same section.
Refunds on takeout and delivery
Off-premises orders bring their own leakage. Delivery platforms issue refunds for missing or wrong items and may charge them back to you, and takeout guests call to report problems after they get home. Record every refund with the order number, the item and the reason, and compare platform refund reports with your own records each week. A run of missing-item refunds usually points to a packing problem: no checklist at the pickup shelf, sauces packed separately and forgotten, or a rushed handoff to drivers. A simple packing check before each bag is sealed often removes most of these refunds.
Comps that pay for themselves
Not every comp is a loss. A well-timed dessert after a long wait can save a guest relationship and a review. Reputation is worth protecting: a one-star increase in a restaurant's Yelp rating has been linked to a 5-9% increase in revenue in Washington State data[4]. Give managers a hospitality budget, track it as its own reason code, and review whether it is being used for the guests who need it. The point is to spend it on purpose, not by accident.
Track discounts and loyalty separately
Promotions and loyalty rewards are planned costs and should be measured against the traffic they bring. Over 80% of consumers use deals such as BOGO offers, combo meals or real-time specials[5], and rewards programs influence where many guests order.
Report promotional and loyalty discounts apart from service comps, and calculate the cost of each promotion per redemption and per new or returning guest. A promotion that mostly discounts guests who would have come anyway is a price cut, not marketing.
Kitchen errors and remakes
Many comps begin in the kitchen: a steak cooked past temperature, a missing modifier or a dish that sat too long in the window. Track remakes by reason in the same way as comps, and review them with the chef weekly. A cluster of remakes on one dish points to a recipe, a station or a training problem. A cluster at one time of night points to a ticket flow problem, often linked to pacing at peak. Fixing those causes reduces comps without asking servers to say no to unhappy guests, which is the better outcome for everyone.
Train every new hire on the policy
New staff should learn the rules on their first shift, not after their first mistake. Show them how to void before sending, when to call a manager, which reason codes to use and why the restaurant reviews adjustments. Make it clear that reviews apply to everyone, including managers and the owner, so nobody feels singled out. When honest staff understand that the reports protect them as well as the business, they are more likely to raise problems early.
Talk to staff with facts, not suspicion
Script: "I review everyone's adjustments every week. Yours were higher than the team's this week, mostly voids after send on Thursday and Friday close. Walk me through what happened on these checks." Listen first; many spikes have simple explanations, such as a broken printer or a new menu item that confused guests.
If the explanation does not hold, follow your written policy and get advice before taking disciplinary action. For broader controls see our guide to restaurant theft prevention.
Frequently asked questions
What is the difference between a comp and a void?
A comp gives away an item after it was made and served. A void removes an item before payment; a void after the item was sent to the kitchen means food was made and not paid for.
What percentage of sales should comps and voids be?
It depends on concept and policy. Set your own baseline from eight weeks of data, track it daily and investigate any person or shift far above the team average.
How do I stop void abuse at my restaurant?
Require manager approval for voids after send, use unique logins, block deletions from closed checks, review voids by employee weekly and look for voids on checks paid in cash.
Should loyalty discounts count as comps?
No. Track them separately as a marketing cost and measure them against the visits they bring.
References
National Restaurant Association (2025). Restaurant Industry Poised for Growth in 2025 (2025 State of the Restaurant Industry press release) (opens in a new tab) ↑
National Restaurant Association (2026). Restaurants remain resilient despite challenging business conditions (opens in a new tab) ↑
National Restaurant Association (2025). Persistent Cost Increases and Enduring Demand Will Shape the Restaurant Industry in 2026 (opens in a new tab) ↑
Harvard Business School (Michael Luca) (2016). Reviews, Reputation, and Revenue: The Case of Yelp.com (HBS Working Paper 12-016) (opens in a new tab) ↑
National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑