Reservation deposits: when they help, when they hurt

Reservation deposits are the strongest tool a restaurant has against no shows. When a guest has paid something to secure a table, they are far more likely to turn up, and far more likely to cancel properly if they cannot. For a fully booked Saturday, a tasting menu prepared for every guest, or a table for twelve on New Year's Eve, that certainty is worth a great deal.

They also have a cost that is easy to miss. Every deposit request is a moment where a guest hesitates, and some guests decide not to book at all. They are not all the guests who would have failed to turn up. Many of them would have come, eaten, paid and returned. A deposit that removes three no shows but loses five genuine bookings has made the night worse, not better, and because those lost bookings never appear in the diary, nobody notices.

This guide is about getting that trade right. It explains the different forms a deposit can take, when deposits help and when they hurt, how much to ask, how to write the policy, and the cheaper measures that should usually come first. It is written for venues deciding whether, and where, to use deposits at all.

The word deposit is used loosely, but there are four distinct tools, and guests feel them differently.

The order matters because the friction rises with each step. A card hold asks the guest to trust you with their details; a deposit asks them to part with money now; prepayment asks them to commit fully. Each step reduces no shows further, and each step deters more guests.

Deposits work because they change the guest's position. Without one, failing to turn up costs the guest nothing, so a booking can be kept "just in case" alongside two others and abandoned at no cost. With one, the booking has a price, so the guest either comes or takes the trouble to cancel. Even a small amount changes behaviour, because it turns the booking from a free option into a commitment.

They also filter. Guests who book many places speculatively, or who book without much intention of coming, tend to avoid booking where a deposit is asked. That is part of why deposits reduce no shows so sharply: they remove the bookings most likely to fail.

The same filtering effect catches genuine guests. Some people will not give card details to a restaurant they have not visited. Some book on behalf of a group and do not want to take on the risk for others. Some simply find the extra step annoying and book somewhere that does not ask. Each of these is a booking lost before it was made.

This shows up in booking conversion: the share of people who start a booking and finish it. A deposit step adds friction exactly at the point of commitment, and booking flows that ask for payment often see more guests abandon before completing. Our guide to booking conversion covers how to measure that drop.

There is a quieter cost too. A deposit changes the tone of the relationship. A guest who has been asked to secure their table with money arrives as a customer who has prepaid, not a guest who has been welcomed. For many venues, that matters.

Deposits pay where the cost of a no show is high and demand is strong enough to absorb a few lost bookings. That usually means:

In each of these cases, the guests booking are usually motivated enough to accept a deposit, and the cost of a no show is high enough to justify the friction.

Deposits tend to do more harm than good where:

For an ordinary weekday service in a neighbourhood restaurant, a deposit is usually a solution to a problem that a good reminder would have fixed.

Before introducing deposits anywhere, make sure the gentle measures are in place, because they fix most no shows without any friction at all.

These turn many silent no shows into cancellations you can resell, which is often all a venue needs. Our guide on how to reduce no shows without annoying guests sets out the full sequence. Measure your no show rate after the gentle measures have been running for a month, and only then decide where deposits are still needed.

If you do need stronger protection, a credit card hold is usually the better first step. It asks less of the guest, because nothing is taken unless they fail to arrive or cancel late, and it still changes behaviour, because the guest knows a fee may apply.

A paid deposit is stronger, and suits services where food is committed in advance or where the cost of a no show is very high. Prepaid bookings suit tasting menus, ticketed events and dates where the whole room is sold in advance.

Whichever you use, take card details only through a properly secured payment provider, never written down or stored in a spreadsheet. Card data security has its own standards, set by the PCI Security Standards Council, and a venue that collects card details itself takes on obligations it is usually better to leave to a payment provider.

The amount should be large enough to change behaviour and small enough not to deter. A common approach is a fixed amount per guest, scaled to the venue's average spend, rather than a large share of the expected bill. For a set or tasting menu, prepaying the menu itself is often accepted, because guests understand that the food is prepared for them.

Keep the amount the same for similar bookings, so guests are not confused, and state it clearly at the start of the booking flow rather than at the last step. A deposit that appears as a surprise on the final screen is the most likely to cause abandonment.

The policy matters as much as the deposit. A clear, fair policy, shown before the guest commits, is accepted by most guests. A vague or hidden one causes arguments, bad reviews and chargebacks.

A good policy states:

Show the policy on the booking page, in the confirmation and in the reminder. Use plain language: "If you need to cancel, let us know by midday the day before and your deposit will be refunded in full" is clearer than any amount of legal phrasing.

A no show fee, charged to a card on file, is the part of a deposit policy that most often goes wrong. Charge it only when the policy was clear, the guest agreed to it, and there is no obvious reason to waive it. Give the team authority to waive it in reasonable cases, such as a genuine emergency, because a fee charged unfairly creates an angry former guest and sometimes a disputed charge.

Record every fee charged and every one waived, with a reason. The pattern tells you whether the policy is working and whether it is being applied fairly.

Here is an illustrative comparison for a restaurant with a weekend problem. The figures show the method rather than typical results.

The gain is small, and a waitlist could have filled some of those 12 empty covers anyway. Now apply the card hold only to parties of six or more, who account for half the no shows but a much smaller share of bookings. Bookings barely fall, no shows drop by about half, and seated covers rise more. Targeting is usually what makes deposits pay.

The bookings a deposit loses are invisible unless you look for them, because they never reach the diary. To see them, measure booking conversion on your booking page: how many people start a booking and how many complete it. Compare the services that ask for a deposit with the ones that do not, or compare the same service before and after the deposit was introduced.

If the share of people completing a booking falls sharply when the deposit appears, the deposit is turning guests away. Some of those would have been no shows, but many would not. Weigh the drop against the no shows saved, using your own average spend, and you have an honest picture of whether the deposit is paying for itself.

Where the drop is large, try moving the deposit notice earlier in the booking flow, so guests know before they invest time in choosing a date and a table. Guests who decide early not to continue are less irritated than guests who reach the final step and find a payment screen they did not expect.

Venues with a large share of walk-in trade should be especially careful with deposits. If most of your guests arrive without a booking, the few who book are often your most committed guests: regulars, celebrations, groups planning ahead. Asking them for a deposit can feel like punishing the guests who did the right thing.

For these venues, a better approach is usually to keep bookings free and to hold a sensible share of the room for the door, so a no show is absorbed by walk-ins rather than leaving the room short. Deposits can still make sense for large groups or special dates, where the commitment on both sides is bigger.

If you decide to introduce deposits on a service that has never had them, how you do it shapes how guests react. A sudden change, discovered at the last step of a booking, feels like a new charge. A change explained in advance feels like a sensible policy.

Announce it first to the guests most affected: your regulars and anyone with a future booking on the service in question. Explain the reason in a sentence, such as tables left empty on busy nights, and explain how the deposit works, including that it comes off the bill and is refunded with reasonable notice. Update the booking page so the deposit is mentioned at the start of the flow. Brief the team who take phone bookings so they can explain it the same way. Then watch bookings and seated covers closely for the first month, ready to adjust the amount or the services it applies to.

Groups and private dining are where deposits are most accepted and most useful. A table for twelve or a private room is a large commitment for the venue: it may mean turning away other bookings, ordering extra stock and adding staff. Guests booking these understand that.

For groups, a common approach is a deposit per guest at the time of booking, with final numbers confirmed a set number of days before the date and the balance settled on the night. For private rooms, a minimum spend with a deposit against it is usual. Put the terms in writing, confirm them by email, and keep a record of the organiser's agreement. Most disputes over group bookings come from terms that were agreed verbally and remembered differently.

Measure four things before and after introducing deposits on a service: the no show rate, the number of bookings, booking conversion on your booking page, and the number of covers actually seated. Deposits are working when seated covers rise. If no shows fall but seated covers stay flat or fall, the deposit is costing as many bookings as it saves, and a gentler measure would serve the service better.

servearound's reservations module concentrates on the measures that reduce no shows without friction. Guests verify their email with a six-digit code before a booking is confirmed, a reminder goes out as many hours before the booking as you choose, and every confirmation carries a link to change or cancel, so changed plans arrive as cancellations rather than empty tables. A booking can be postponed to another date without starting again, and when a time is full, the booking page offers the waitlist.

Celebration packages and set menus can be offered on the booking itself, priced per guest or at one price, and join the bill when the party is seated. The reservations report in Analytics shows no show, cancellation and seated rates by meal period, source and party size, so you can see which services still need stronger measures. See the reservations module, or our pricing, which is per venue with no fees per cover.

Most do for peak nights, large parties, set menus and special dates, especially when the policy is clear and fair. Fewer accept them for ordinary weekday bookings.

Usually not. Regulars rarely no show and are the guests most likely to resent being asked. Many venues exempt known guests or apply deposits only to bookings above a certain size.

It is stronger, but asks more of the guest. Start with a card hold where protection is needed, and use deposits or prepayment where food is committed in advance.

Show them the policy they agreed to and the record of their booking. If the policy was clear and visible, most disputes are resolved. If it was not, it is usually better to refund and fix the policy.

Refundable with reasonable notice is the fairest and most widely accepted approach. Non-refundable deposits suit prepaid events and dates where a late cancellation genuinely cannot be resold.

Rarely for ordinary bookings. In a venue that relies on walk-ins, keep bookings free, hold part of the room for the door, and reserve deposits for large groups and special dates.

Briefly and warmly: what is taken, that it comes off the bill, and how much notice gets it refunded. A consistent, friendly explanation prevents most of the arguments deposits can cause.

Usually, and guests appreciate it. Deducting the deposit from the final bill makes it feel like part of the meal rather than a penalty.

Reservation deposits reduce no shows and reduce bookings. Use the gentle measures first: verified contact details, clear confirmations, well-timed reminders, easy cancellation and a live waitlist. Then, where no shows are still expensive, use a credit card hold, a deposit or prepaid bookings, targeted at peak services, large parties, set menus and special dates.

Show the policy before the guest commits, keep it fair, waive fees with discretion, and measure seated covers rather than no shows alone. A deposit is working only when more guests end up sitting at your tables.