Restaurant No-Show Fees and Deposits: Policies Guests Accept

Why no-shows hurt more than an empty table

When a booked party does not arrive, you do not just lose one table’s revenue for one turn. You turned other guests away for that slot, perhaps texted a walk-in that you were full, and staffed and prepped for covers that never came. On a Friday night the empty table is the least of it; the guests you said no to are the real cost, and some of them will not try again.

The purpose of a no-show policy is not to collect fees. It is to make the reservation feel like a commitment, so guests who cannot come tell you in time for someone else to have the table. A policy that changes behaviour and is almost never charged is a success. A policy that collects a steady stream of fees is a sign that guests do not understand it or that your reminders are not reaching them.

The three mechanisms

How to size the fee

Set the fee per cover, not per booking, so a table of eight who vanish is treated differently from a couple who do. Anchor it to what a typical guest actually spends at your venue rather than to a number you saw another restaurant use. A fee that is a fraction of an average cover reads as a reasonable commitment; a fee close to the price of the meal reads as a penalty and will stop people booking at all.

Match the mechanism to the night. A modest hold with a small no-show fee is enough for ordinary service. A deposit that covers a meaningful share of the expected spend makes sense for a fixed-price menu or a holiday where you buy ingredients against confirmed numbers. Whatever you choose, you should be able to say the amount and the reason out loud to a guest at the door without feeling awkward. If you cannot, it is too high.

When to waive it

A policy that is enforced without judgement will lose you regulars, and the whole point was to keep them. Waive the fee when weather or a transit failure kept people away, when a guest calls ahead even if it is after the window, and on a first offence from someone who has dined with you before. Make waiving easy for your team: a single tap from the reservation, not a call to the owner.

Be consistent about it. Write down the situations where the fee is waived and share them with everyone who answers the phone or manages the book. Guests compare notes, and a fee waived for one person and charged to another for the same reason does more damage than either decision on its own.

How to word the policy on the booking page

Guests accept policies they understand before they commit. Put the policy on the booking page itself, in plain words, before the card field, not in a linked terms page. One or two sentences is enough: what you will do, when, and how much per person. Say what happens if they cancel in time, what happens if they cancel late, and what happens if they do not arrive. Repeat the essentials in the confirmation and the reminder.

Be honest about the difference between a hold and a charge, because guests often confuse them. A hold is not a charge: it reserves an amount on the card, no money moves, and it drops off automatically when the guest arrives or cancels inside the window. A deposit is a charge: money moves at booking and comes back as a credit against the bill or a refund. Use the right word for what you actually do. A guest who sees an unexpected "charge" that was really a hold will call their bank before they call you.

Reminders do most of the work

Most no-shows are not malicious; they are forgotten. A reminder the day before, with the time, the party size and a one-tap way to cancel or change, turns a forgotten booking into a freed table you can give to someone else. A second reminder a few hours ahead helps for larger parties and peak nights. Every reminder should restate the policy briefly so the guest is never surprised by a fee.

Make cancelling easier than not cancelling. If a guest has to call during service to release a table, they will not bother. A link in the reminder that cancels or reschedules in a couple of taps, and a text that tells them the hold has been released, is what makes the policy feel like a courtesy rather than a trap.

How Sopoints implements it, and what to check locally

Sopoints reservations support all three mechanisms through Stripe. For a card hold, the guest’s card is authorized at booking and the hold is released automatically when the guest is seated or cancels inside the window, so a guest who turns up never sees a charge. If the party does not show, the no-show fee you set is charged and is capped at the hold, never more. Charge-at-booking deposits and tiered cancellation policies with a refund window are configured per venue, reminders go out by text, and payouts land in the restaurant’s own Stripe account. Guests get a one-tap cancel link, and STOP replies are honoured automatically.

None of that replaces a check on the rules where you operate. Deposit and cancellation-fee practices are covered by consumer protection law in many places, some jurisdictions restrict what a business may keep on a cancellation, and card network rules apply to how fees are disclosed and charged. Ask a local advisor before you publish a policy, and update it when the rules change. Other reservation systems offer similar tools; whichever you use, the honesty of the wording matters more than the software.