# How to reduce restaurant no-shows — and when to take a deposit > No-shows aren't bad luck. They're a series of small, fixable gaps between the moment someone books and the moment they're meant to walk in. Here's the order to close them — and the one lever most restaurants reach for too early. _Canonical: https://seatsat.com/guides/reduce-restaurant-no-shows_ --- A no-show is rarely a decision to skip your restaurant. It's a forgotten plan, a double-booking, a party that shrank from six to three, or a guest who couldn't find a way to cancel without an awkward phone call. Treat it as an operations problem, not a character flaw, and it becomes a number you can move. The instinct is to jump straight to deposits. Hold off. Deposits are the strongest tool and the bluntest — used everywhere, they quietly suppress the casual bookings that fill your room midweek. Work through the cheaper levers first; reach for a card only where the risk justifies the friction. > **The short version** > > - Confirm at booking, remind the day before, and make cancelling one tap. > - Turn silent no-shows into early cancellations you can re-sell. > - Reserve deposits and card holds for big parties, peak slots and set menus. > - Measure the rate by slot and party size — don't guess. ## 1. Make the booking real with a confirmation A reservation that lives only in someone's head will be forgotten. The moment a guest books — on your site, by phone, over chat — they should get an immediate confirmation with the date, time, party size and a clear way to change or cancel. This does two things: it anchors the plan in their calendar, and it gives them an exit that doesn't involve a phone call they'll avoid making. If your only record is a paper book or a message thread, confirmations are the first thing to fix. Every booking should generate one automatically, in the guest's language. ## 2. Send one good reminder A single reminder the day before — or the morning of, for evening bookings — recovers more covers than almost anything else. The reminder isn't nagging; it's an invitation to cancel cleanly. A guest whose plans changed will tap "can't make it" at 11am if you let them, and that table goes back on sale. Without the reminder, that same guest simply doesn't appear at 20:00, when it's far too late to re-fill. > A reminder doesn't stop people cancelling. It moves the cancellation early enough that you can sell the table twice. > > _— — THE WHOLE POINT OF REMINDERS_ ## 3. Make cancelling effortless This is the counter-intuitive one. Restaurants sometimes hide the cancel option, hoping friction keeps the booking. It does the opposite: it converts a would-be early cancellation into a no-show. Put a one-tap cancel and modify link in every confirmation and reminder. You want the guest who can't come to tell you as early as possible — the easier you make leaving, the more covers you save. ## 4. Watch the high-risk bookings Not all reservations carry the same risk. The ones that hurt share a pattern: - Large parties — one no-show empties a whole section, not a two-top. - Peak slots — Friday and Saturday prime time, where you turned away walk-ins to hold the table. - Long lead times — a table booked three weeks out is more fragile than one booked this morning. - Set menus and events — where you've bought stock and rostered staff against a headcount. These are exactly the bookings worth protecting with something stronger. Everything else is usually well covered by the first three steps. *** ## When a deposit actually helps A deposit or card hold works when the cost of an empty table is high and the booking is one you can afford to lose if the guest balks at giving a card. That's why it fits large parties, peak weekend slots, tasting menus and ticketed events — and rarely fits an ordinary Tuesday two-top, where the friction of asking for a card costs you more bookings than the occasional no-show ever would. ### Hold vs. charge You have two mechanisms. A **card hold** takes nothing up front but authorises a no-show fee if the guest doesn't arrive or cancels inside your window — low friction, strong signal. A **prepaid deposit** takes money now and nets it off the bill — best for events and set menus where you're committing real cost ahead of service. For most restaurants, a card hold on the riskiest 10–20% of bookings is the sweet spot. > **Set the policy before you need it** > > - State the window plainly: e.g. free cancellation up to 24 hours before. > - Apply holds only above a party-size threshold, or only at peak slots. > - Always confirm the policy in the booking message — no surprises at the door. > - Waive it generously for genuine emergencies. Goodwill outlasts one fee. ## Is a no-show fee even legal? It's the question every operator reaches eventually, and the honest answer is: usually yes, if you do it openly — but the details are set by your local law, not by us, so what follows is general orientation rather than advice. Across most of Europe the same principle recurs. A no-show or late-cancellation charge is generally defensible when three things are true: the amount is **disclosed before the guest books**, the **cancellation window is stated plainly**, and the guest **actively agreed** to those terms. A fee that meets that bar is a term of a contract the guest accepted. A fee that fails it — buried in fine print, sprung at the door, or wildly out of proportion to the real loss — is the kind that gets disputed and, in some jurisdictions, struck down as an unfair term. > **Keep a fee defensible (general guidance, not legal advice)** > > - State the amount and the cancellation window **before** the booking is confirmed. > - Capture clear consent — a checkbox or an explicit step, not a link no one opens. > - Keep the amount **proportionate** to the actual cost of the empty table. > - Apply it **consistently**, and waive it for genuine emergencies. > - Confirm the specifics against your country's consumer law — the rules vary. The tax treatment is a separate question, and a genuinely local one. Depending on the country and on whether the money is a forfeited prepaid deposit or a card-hold penalty, a no-show fee may sit outside VAT (treated as compensation for a loss) or inside it (treated as payment for a supply). That's a question for your accountant, not a universal rule — flag it before you decide whether your stated fee is inclusive or exclusive of tax. None of this should scare you off a policy. It's an argument for a _clear_ one: the same disclosure that keeps a fee lawful is also what keeps it fair to the guest. UK operator? [What restaurants in the UK actually do](/guides/restaurant-no-show-fees-uk) goes further on amounts, the deposit-versus-charge distinction, and the two questions worth putting to your accountant before you publish a figure. ## Measure it, or you're guessing You can't improve a no-show rate you don't track. The useful version isn't one number — it's a breakdown: — typical no-show range for full-service restaurants, by city and cuisine **×2** — a clean early cancellation lets a prime table be sold twice — a sensible default cancellation window for most rooms Break your rate down by slot, by party size and by booking source. You'll usually find the problem is concentrated — large weekend parties booked far ahead — which tells you exactly where a card hold earns its keep and where it would just cost you covers. ## A simple rollout 1. Turn on automatic confirmations for every booking, in the guest's language. 2. Add a day-before reminder with one-tap cancel and modify. 3. Track no-shows by slot and party size for a month — establish your baseline. 4. Add card holds only to large parties and peak slots, with a clear 24-hour window. 5. Review monthly. Loosen where the rate is fine; tighten only where it isn't. Most restaurants find steps one to three solve the majority of the problem before a single deposit is taken. The deposit is the scalpel for what's left — not the first thing you reach for.