Restaurant booking deposits explained: how they work and when to use them.
It's 7pm on a Saturday. The kitchen team is prepped, the floor is fully staffed, and the table for six by the window is still empty. No call, no email. Just a gap on your busiest night that no walk-in is going to fill.
If that sounds familiar, you're not alone. Research from Zonal estimates the cost of no-shows to UK hospitality at around £17.6 billion a year in lost sales, and found that no-show rates rose from 12% to 14% over 2024.
That's the reason more restaurants are asking customers to pay a deposit upfront when they book. So how do restaurant deposits work, and when is it worth or right to ask for one? Let’s take a look at the why, the how and the when, plus the details you need to get right so deposits protect your business without putting customers off.
Why do restaurants take deposits on bookings?
A free booking costs customers nothing to make and nothing to forget. A deposit changes this outlook. Once someone has paid out of pocket upfront, the booking feels like a commitment, and they're far more likely to turn up or let you know if their plans have changed.
A small customer financial commitment does a few jobs at once:
- Reduce no-shows. Customers who have paid upfront are more likely to show. It’s a no-show prevention tool.
- Reduces late cancellations. People are more likely to amend or cancel in advance, which gives you a real chance to rebook the table.
- It filters out "just in case" bookings. Some customers are known to book three places and decide on the night. A deposit leaves you with customers who plan to turn up.
- Protecting revenue. When a table doesn't show, the overheads don't disappear. A deposit helps secure your revenue and covers some of those costs so that empty table doesn't wipe out the margin on a whole service.
Worried a deposit could turn away a customer or one of your regulars? Most guests understand why a restaurant would ask for one on a Saturday night or for a group of eight. Customers today, are now more open to this than you might anticipate. In Zonal and CGA's survey of 5,000 consumers, over half support paying deposits for restaurant bookings.
How do restaurant deposits work?
The process is easier than many restaurant owners expect, especially when a restaurant booking system handles this step for you. Here's how typical booking deposits work from booking to service.
- Customers pay the deposit when they book.
To confirm the booking, the customer is asked for a deposit in the booking process, either per person or per booking. Some restaurants charge a fixed amount per cover, say £/€/$10.00 per head. Others take the full price upfront, which works well on set menus or special events where the food cost is fixed. - A payment gateway securely captures the deposit.
The card details go straight to a payment gateway provider (such as Stripe), not handled by your team. The gateway processes and holds the payment, so no one in the restaurant ever sees or stores the full card number. Your staff and customer card details are safeguarded. - Customer cancels or amends booking within the policy.
If a customer cancels or modifies covers within the policy, the restaurant can refund the deposit amount. - At the end of the night, the deposit comes off the final bill.
On the night, the deposit is deducted from the final bill, and the customer pays the remaining balance. - If the customer doesn’t follow the booking policy, the restaurant keeps the deposit. If the customer no-shows or cancels outside the cancellation period set out in your booking policy, the restaurant keeps the deposit. It won't always cover the full loss, but it takes the sting out of an empty table.
For customers, it's one extra step in the booking process, and for the restaurant, it's a reliable restaurant booking system and a step closer to eliminating no-shows.
When should restaurants take deposits?
Deposits are not necessary on every booking. The right time to ask for one is when an empty table would hit your revenue hardest, especially when you've little chance of filling it from walk-ins or a waitlist. For most restaurants, that comes down to these three situations.
Peak times
Friday and Saturday evenings are the obvious ones, the popular times customers want to book. These are the slots where you could be turning away a walk-in, so a no-show costs you twice: the lost spend from the booking and the lost spend from the people you said no to. Many restaurants only take deposits on weekends or evening time slots and leave the rest of the week free to book.
Special events and occasions
Valentine's Day, New Year's Eve and the festive season are high demand, high stakes nights. These services normally involve a special menu, buying in extra stock and having more staff on the floor, so every seat counts. Customers expect it too. In the same Zonal and CGA research, 65% of consumers said they approve of deposits for special occasions like Valentine's Day.
The same goes for your own events, such as tasting menus, supper clubs or private dining. If you're prepping a menu for a fixed number of guests, taking the full amount upfront is often the fairest way to keep costs covered.
Large group bookings
A table of ten that doesn't turn up is a much bigger problem than a table of two. You've rostered staff, blocked out a section and possibly prepped food for them. Setting deposits for bookings above a minimum party size, for example six or more, protects you against the extra staffing and prep a big group needs. Guests tend to accept this: the research found 59% support for deposits on groups of six or more.
What to get right when taking restaurant booking deposits.
Deposits work best when customers feel the process is fair and secure. The following points can make a big difference in customer assurance.
Keep customer card details safe
Never take card numbers over the phone, write them down, or store them in a spreadsheet. Use a PCI-compliant payment method, where card details are captured and stored by the payment gateway securely, rather than by your team. This protects customer data and staff, who never have to handle sensitive information.
Deduct the deposit and show it on the final bill
When a customer pays on the night, take the deposit off the final bill and record the deduction clearly on the receipt. This avoids awkward moments with customers at the end of a good experience, and it keeps figures accurate.
Send a customer receipt for the deposit
Customers should get a receipt for the deposit as soon as they pay it, ideally emailed along with the booking confirmation. This gives a record of what they've paid and reassures them the booking is secured, and payment was successful.
Be upfront about your booking policy
Inform customers clearly of the deposit amount and your cancellation policy at the time of booking. Include in the booking policy how much notice they need to give for a refund and what happens if they don't turn up or cancel too late. Clear terms result in fewer disputes and disappointed customers.
Set up booking reminders
Send automated reminders by email or text a day or two before the booking, and include a short line highlighting again your cancellation and no-show policy. This gives customers enough time to cancel or change their plans, so you can rebook the table. Reminders work on their own too: Zonal and CGA found 36% of consumers are more likely to attend when they get one.
When used at the right times and clearly outlined to customers, deposits protect restaurants during their busiest services and are a valuable no-show preventation tool. The only cost to customers is nothing more than a little extra commitment.
simpleERB is a booking system that lets restaurants handle deposits securely during peak times or for special menus with Stripe. Trial simpleERB today, with no card required and no lock-in.
