Key takeaways
- Write the policy as a decision ladder: fix the dish first, replace second, refund or comp last.
- Give every role a clear comp limit in writing, and require a reason code for every adjustment.
- Log remakes and comps in the POS, then review them weekly by server, dish and reason.
- Treat takeout and delivery complaints with their own rules, because you cannot see the plate.
Why a refund policy needs to be written down
Most restaurants already have a refund policy. It just lives in the head of whoever is managing the floor that night, which means a cold steak gets remade on Tuesday, comped on Friday and argued over on Sunday. Guests notice the inconsistency, staff learn to avoid the conversation, and nobody can tell whether adjustments are rising.
The money is not trivial. Food and labor each take roughly 33 cents of every sales dollar[1], so a remade entrée costs you the plate twice and a full refund also gives away the labor that went into it. With 42% of operators saying their restaurant was not profitable in 2025[2], and 33% saying the same for the first half of 2026[3], loose comping is a margin leak you can measure.
Source: National Restaurant Association, 2026[3]
Show the data
| Item | Value |
|---|---|
| Full year 2025 | 42% |
| First half of 2026 | 33% |
The other side of the ledger is reputation. A one-star increase in a Yelp rating has been linked to a 5 to 9% rise in revenue for independent restaurants[4], and a complaint handled well at the table rarely turns into a one-star review. The goal of a written policy is not to say no more often. It is to say yes the same way every time, quickly, and with a record.
The decision ladder: fix, replace, refund, comp
Put the options in a fixed order so staff do not jump straight to taking items off the check. The first question is always whether the dish can be put right; the last is whether money changes hands.
| Situation | First response | If the guest declines | Who approves |
|---|---|---|---|
| Dish undercooked or cold | Remake to spec and fire it on priority | Replace with another dish | Server, with expo told |
| Wrong dish or missing modifier | Remake correctly, keep the wrong plate off the check | Remove the item | Server |
| Guest simply does not like it | Offer one alternative dish | Remove the item once per visit | Manager on duty |
| Foreign object or allergen concern | Remove plate, inform manager and kitchen, never remake from the same prep | Remove item and any related items | Manager on duty, logged as an incident |
| Long ticket time, food fine | Apologize with a time update | Small comp such as dessert or a drink | Manager on duty |
| Service failure across the visit | Manager visits the table | Partial or full check adjustment | General manager or owner |
Allergen complaints sit outside the normal ladder. The eight major allergens accounted for 90% of US food allergies when federal labeling law passed[5], so a guest who says they reacted to something is a safety event first and a refund question second. Remove the plate, do not argue, and write it up.
Comp authority: who can give what
A comp limit only works if everyone knows it and it is small enough that people do not need to ask for routine fixes. Set limits by role and by reason, and put them in the staff handbook next to the steps of service.
| Role | Can approve without asking | Must call a manager for | Reason code required |
|---|---|---|---|
| Server or bartender | Remakes of their own tables' dishes; one dessert or soft drink per table | Removing any entrée from the check | Yes |
| Shift lead | Removing one item per check | Adjustments above one item, any refund to a card | Yes |
| Manager on duty | Item removals and partial check adjustments up to an Example cap of one entrée per guest | Full-check comps, gift card offers | Yes, plus a short note |
| General manager or owner | Any adjustment, gift cards, follow-up offers | Nothing | Yes |
Example: a fictional bistro sets its server limit at one dessert per table, its manager cap at one entrée per guest, and requires the general manager for anything that touches a full check. In the first month the bistro finds that most adjustments come from two dishes and one closing shift, which tells it where to fix the kitchen rather than where to tighten the rules.
Scripts that keep the conversation short
Speed matters as much as the remedy. 94% of off-premises customers call speed critical and over 9 in 10 put customer service at the top of their priorities[6], and dine-in guests are no more patient when a plate is wrong. Give staff a few lines they can say without improvising.
- At the table: "I'm sorry that's not right. I can have the kitchen remake it now, or bring you something else. Which would you prefer?"
- When the guest wants it off the check: "Of course, I'll take that off. Can I bring you anything in its place while your friends finish?"
- When it is above their limit: "I want to get this right for you. My manager will be over in a moment to sort it out."
- On the phone after the visit: "Thank you for telling us. Can you give me the date, the time and what you ordered so I can look at the check while we talk?"
Avoid asking guests to prove the problem at the table. If the policy says a dislike earns one alternative per visit, that is the remedy, without a debate about whether the sauce was really too salty.
Logging every adjustment so the policy is not abused
Comps without records become a quiet discount program for friends of the staff. The fix is boring and effective: every adjustment goes through the POS with a reason code and a name, even a free coffee.
Create reason codes
Set up a short list such as cooking error, wrong order, guest dislike, long wait, foreign object, allergen concern, service recovery and promotional. Avoid an "other" code or require a note when it is used.
Require a name on every void and comp
Each adjustment records who requested it and who approved it, so you can see patterns by person as well as by dish.
Keep remade plates on the record
Ring remakes as a zero-price item with a reason code so the kitchen's waste is visible, not just the check change.
Review weekly
Pull adjustments by reason, dish, server and daypart every week. Compare the total with sales so you see adjustments as a share, not just a dollar figure.
Act on patterns, not single events
Two or three repeats of the same dish and reason point to a recipe, station or training problem. One server with far more comps than peers needs a private conversation.
Watch also for adjustments that are tied to reviews. Offering refunds or freebies only to guests who promise a positive review crosses a line under federal rules on review incentives[7], and review platforms already filter a meaningful share of restaurant reviews as suspicious; one study found roughly 16% of Yelp restaurant reviews were filtered[8]. Fix the problem because it was a problem, never in exchange for a rating.
Takeout and delivery complaints need their own rules
You cannot see a delivery plate, and the guest cannot hand it back. Write a separate section of the policy for off-premises orders so phone staff are not making it up.
- Ask for the order number, the item and what was wrong, then check the packing record or photo if you keep one.
- For missing items on direct orders, offer a refund of that item or a credit on the next order, and log it with the same reason codes.
- For marketplace orders, direct the guest to the platform's own help flow, then record the complaint internally so you can dispute charges you believe are wrong. See how to dispute delivery app refunds for the evidence to keep.
- Never promise a remake by delivery unless your driver or partner can actually do it within the guest's window.
If a phone line is busy when an unhappy guest calls back, the complaint usually moves to a review site. Some restaurants use an SI Employee such as Ava to take the details and a callback number at any hour and pass the complaint to a manager, who can respond the next morning with the check in front of them.
Costing the policy before you roll it out
Before you announce new limits, run last month's adjustments through them. Pull every void, comp and remake, tag each with the reason code it would have received, and see which ones the new ladder would have handled differently. This shows whether your limits are realistic or whether managers will be called to tables all night.
Example: a fictional 90-seat restaurant finds that cooking errors and long waits make up most of its adjustments, while "guest dislike" removals are rare but large because they tend to be entrées. It keeps the server limit low, adds a one-alternative rule for dislikes, and sets a weekly target for remakes by station rather than a target for comps, so the kitchen owns the fix.
Making the policy visible to guests
Guests do not need your comp ladder, but they do need to know how you handle problems. Put two or three plain sentences on your website's policy page and in your online ordering confirmation, for example that you will remake any dish that is not right and that delivery issues are handled through the app used to order. Keep it consistent with your reservation policy page and your house rules so a guest never reads two versions.
Train the policy at pre-shift for a week after any change, and update it when the weekly review shows a new pattern. A refund policy that changes with evidence is far easier to defend than one that changes with whoever is on shift.
Frequently asked questions
Should restaurants give refunds or remakes?
Start with a remake or a replacement dish, because it fixes the meal the guest came for. Remove the item from the check when the guest declines a fix, and keep full refunds for serious failures approved by a manager.
Who should be allowed to comp food?
Give servers small, routine fixes such as remakes and a dessert, give the manager on duty item removals within a set cap, and reserve full-check comps and gift card offers for the general manager or owner. Every comp should carry a reason code and a name.
How do I stop staff from abusing comps?
Ring every adjustment through the POS with a reason code and approver, review the report weekly by server, dish and shift, and talk privately with anyone whose comps run well above peers.
Can I offer a refund in exchange for removing a bad review?
No. Make the guest whole because the meal was wrong, not in return for changing a review. Federal rules prohibit incentives conditioned on review sentiment, so keep refunds and reviews separate.
References
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) ↑
National Restaurant Association (2026). Restaurants remain resilient despite challenging business conditions (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) ↑
US Food and Drug Administration (2004). Food Allergies (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) ↑
Legal Information Institute (Cornell Law School), eCFR text of FTC rule (2024). 16 CFR § 465.4 - Buying positive or negative consumer reviews (opens in a new tab) ↑
Harvard Business School (2015). Fake It Till You Make It: Reputation, Competition, and Yelp Review Fraud (Luca and Zervas) (opens in a new tab) ↑