In short: A restaurant cancellation policy works when it is part of the booking workflow: visible before confirmation, repeated in reminders, easy to act on, and backed by clear internal rules for staff. Choose between a credit card hold, deposit, or no-show fee based on your concept, party size, demand, and what you know about the guest. The goal is not to punish guests - it is to make the commitment clear enough that they cancel early instead of disappearing.
Most operators know the feeling. You prepped for a party of six on a Friday night. You staffed for it. You turned away walk-ins to hold the table. Then 7:15 rolls around and nobody comes - not even a text.
A clear cancellation policy doesn't fix every no-show, but it changes the math. It shifts some of the risk back to the guest and gives you a real option when someone doesn't honor a booking.
The mistake is treating a cancellation policy as copywriting. It is not just a paragraph on your reservations page. It is a workflow: what the guest sees before booking, what they receive after confirmation, how reminders are timed, how staff explain the rule by phone, how cancellations are logged, and how exceptions are handled.
Here's how to build one that holds up.
What a Restaurant Cancellation Policy Should Include
A restaurant cancellation policy is a guest-facing rule that explains when a reservation can be canceled, what happens after the cancellation window closes, and whether the restaurant will charge a fee, hold a card, or collect a deposit.
A good policy has four parts:
- The cancellation window - how many hours or days notice is required
- The charge or deposit - what happens financially if a guest no-shows or cancels late
- The cancellation method - how a guest actually cancels (link, phone, text)
- The conditions for exceptions - what qualifies as a legitimate reason to waive the charge
You need two versions: a short guest-facing version that guests read before booking, and an internal version for staff that covers exceptions, waiver authority, and how to document what happened.
The best policy is not the strictest one. It is the one guests see before booking, staff can explain consistently, and the restaurant can enforce with documentation.
Choose the Right Tool: Card Hold, Deposit, or No-Show Fee
The right approach depends on your price point, party sizes, service demand, prep cost, and what you know about the guest.
Credit card hold - the lightest touch. You collect card details at booking and charge only if the guest no-shows or cancels within your window. No upfront cost to the guest, lower friction at booking, but the charge may still fail or be disputed after the fact. Works well for casual-to-mid-range restaurants that want some protection without adding friction for new guests.
Deposit - collected at the time of booking and applied to the final bill. The guest is financially committed before they walk in. OpenTable reports that deposits on its platform reduce no-show rates by an average of 57% and make guests 72% less likely to cancel at the last minute (OpenTable, 2026). More friction at booking, but significantly stronger commitment. The right fit for larger parties, tasting menus, holiday reservations, or any night where a no-show does real operational and financial damage.
No-show fee - charged after the fact, either flat per person or tied to a minimum spend. More common at fine dining, tasting menus, private dining, and high-demand services where per-cover revenue justifies the enforcement overhead.
The honest question to ask: What am I actually losing when someone doesn't show? If it's one cover on a Tuesday, a credit card hold may be enough. If it's a reserved private area on New Year's Eve, a deposit is the only policy that makes sense.
Set the Cancellation Window and Late Arrival Rule
Vague policies create disputes. "Reasonable notice" means nothing. Your policy needs a hard number.
Common windows:
- 24 hours - a common starting point for casual and mid-range restaurants
- 48 hours - often used by busier, more formal spots, and for larger parties
- 72 hours or more - often used for tasting menus, prix fixe, or private dining
Also decide what happens with late arrivals. Many restaurants hold a table for 15-20 minutes before releasing it. If you do this, say so in the policy. "We hold reservations for 15 minutes" is a complete sentence that saves a difficult conversation later.
Restaurant Cancellation Policy Template
Here are three versions matched to common restaurant types. Treat these as starting points, not universal rules. Adapt the amounts, cancellation windows, and payment language to your concept, market, booking platform, payment processor, and local rules.
Credit card hold (casual / mid-range):
We require a credit card to hold all reservations. Cancellations made at least 24 hours before your reservation time will not be charged. Cancellations within 24 hours or no-shows will be charged $15 per person. To cancel, click the link in your confirmation email or call us at [number]. We hold reserved tables for 15 minutes.
Deposit (large party / high-demand):
Reservations of 6 or more require a $20 per person deposit, collected at booking and applied to your final bill. Cancellations made at least 48 hours in advance will receive a full refund. Cancellations within 48 hours are non-refundable. To cancel, use the link in your confirmation email.
No-show fee (fine dining / tasting menu):
A credit card is required to secure all reservations. Cancellations must be made at least 72 hours in advance. Cancellations within 72 hours or no-shows will be charged $50 per person. To cancel, reply to your confirmation email or call [number] during business hours.
Three things make each version work: the commitment mechanism, the cancellation window, and a clear exit. Guests know exactly where they stand.
A guest-facing policy full of exceptions and qualifications is hard to understand and harder to enforce.
Show the Policy Before the Guest Books
The most common reason cancellation policies don't hold up is that guests say they never saw it. Sometimes they're right.
Put your policy in:
- The booking widget, before the reservation is confirmed
- The confirmation email, clearly labeled - not buried at the bottom
- Every reminder message
- Your website's reservations page
The policy often breaks on the phone, not online. A guest calls during service, the host is busy, the card requirement feels awkward, and the policy gets softened into "just let us know if anything changes." That is how a written policy becomes optional before the reservation is even confirmed.
If you're taking reservations by phone, give staff the exact sentence to use: "We do ask for a card to hold the reservation, and cancellations within 24 hours are subject to a $15-per-person charge - is that okay?" That takes 15 seconds and removes ambiguity. A policy your host can't say out loud isn't really a policy.
The dispute usually starts with one sentence: "I didn't know I would be charged." Your best defense is not a harsher policy. It is proof that the guest saw it before booking, saw it again in confirmation, and had an easy way to cancel. Without that documentation, a disputed charge becomes much harder to defend.
Make Canceling as Easy as Booking
If a guest can book online in two minutes but has to call during service hours to cancel, you've created friction that turns a cancellation into a no-show.
Every confirmation should have a cancellation link or a clear process. Every reminder should repeat it. Toast reported in its Q3 2025 full-service restaurant trends data that cancellations rose 7% while no-shows declined 1% year over year (Toast, 2025). That does not prove why guests changed behavior, but it supports the operational point: an advance cancellation is easier to recover from than a silent no-show.
Easy cancellation is not generosity - it is good operations.
Enforce It Consistently - But Define Exceptions Before Service Gets Busy
Consistency does not mean charging every guest no matter what. It means deciding in advance what counts as a valid exception, so the decision does not depend on which manager happens to be on shift.
The awkward part is usually not the rule. It is the moment at the host stand or on the phone when someone asks for an exception and the team has to decide quickly. If the rule only exists in the owner's head, every shift will apply it differently.
Your staff needs to know: who can waive the fee, what qualifies as an emergency, how to document the decision, and what note goes into the guest record. A regular who has shown up every Friday for six months should not feel treated like a stranger. But a guest who has canceled late twice needs a different conversation. Neither judgment call should land on a host mid-service without prior guidance.
The best cancellation policies do not read like a threat. They read like a mutual commitment: we will hold the table for you; in return, we ask you to cancel early enough for us to offer it to someone else.
Track Cancellations and No-Shows by Guest
A cancellation policy handles the immediate loss. Guest history handles the longer picture.
When you know that a guest has canceled late twice, you can decide whether to require a deposit for their next reservation. When you see a regular who has never missed a dinner, you treat the conversation differently if life gets in the way.
That kind of awareness doesn't require a complicated system. It requires keeping records - names, visit history, notes on behavior - that give you context the next time that phone rings or that booking comes through.
ToBeOut is built to help independent restaurants keep reservation history, guest notes, and visit patterns in one place — the context you need to make cancellation policies fairer and easier for staff to apply consistently. See how it works →
Cancellation Policy Checklist
- Choose the right mechanism for your restaurant: card hold, deposit, or no-show fee
- Set a specific cancellation window (24, 48, or 72+ hours based on party size and concept)
- Write a short guest-facing policy in plain language - no legal hedging
- Write an internal version for staff: exceptions, waiver authority, documentation process
- Display the policy at every booking touchpoint: widget, confirmation, reminder
- Include a clear cancellation method in every guest communication
- Give staff the exact language to use when taking phone reservations
- Log cancellations and no-shows in guest records so patterns are visible over time
FAQ
What should a restaurant cancellation policy include? At minimum: the cancellation window (how many hours' notice is required), what happens if a guest no-shows, the payment mechanism (credit card hold, deposit, or fee), and how to cancel. The guest-facing version should be short and readable. A separate internal version for staff should cover exceptions, waiver authority, and documentation.
Should I require a deposit or just a credit card hold? For many casual-to-mid-range independents that need more protection than reminders alone, a credit card hold is a reasonable starting point. Deposits make more sense for large parties, tasting menus, or high-demand periods where a no-show creates real operational and financial exposure.
How much should a restaurant no-show fee be? Many casual-to-mid-range restaurants use modest per-person fees, while fine dining and ticketed experiences may set higher amounts. The right fee should reflect your actual loss - food prepped, staff scheduled, the table held - and should match the guest expectations for your concept. It is not meant to be punitive; it is meant to make the commitment real.
Can I charge a no-show fee if the guest booked by phone? You can, but your case for keeping the charge is much stronger when the guest acknowledged the terms in writing - via a confirmation email or booking confirmation. Phone reservations are harder to document. For higher-value bookings taken by phone, follow up with a confirmation text or email that restates the policy.
Should regular guests follow the same cancellation policy? The written policy applies to everyone, but how you handle exceptions is up to you - and should be decided in advance, not in the moment. A guest with a long, reliable booking history is a different conversation than a first-timer who no-showed. That distinction is easier to make consistently if you have the history in front of you.
How far in advance should restaurants send cancellation reminders? A practical starting point is one reminder 24-48 hours before the reservation. For higher-risk bookings - larger parties, special events, holiday services - a same-day reminder can reduce forgetfulness, but the earlier reminder is what gives you a better chance to refill the table.
