Restaurant Booking Deposits: How Much to Charge and How to Collect Them

Why restaurants are starting to charge for bookings

A no-show table is not an empty chair — it is lost revenue that cannot be resold. A table of six that never arrives on a Saturday night costs a restaurant real money: blocked inventory, prep work, and staff allocated to a cover that never lands. As bookings moved from phone calls to WhatsApp and Instagram DMs, the cost of flaking dropped to zero for the customer — and the bill landed on the restaurant.

Deposits flip that incentive. When a guest pays €10–20 to hold the table, attendance rates jump and the no-show's cost is covered when they don't. That is why more restaurants now ask for one — and why guests increasingly expect it for premium slots.

What a deposit legally is (Spain)

Key distinction first: a deposit is an advance, not a supplement. Spain's consumer authorities are explicit on both halves: the Dirección General de Consumo de la Junta de Andalucía (via Consumo Responde) states that booking a table cannot carry an extra cost on top of the final bill — but the restaurant can require an advance, and that advance must be deducted from the total. In practice:

• State the policy before confirming the reservation: amount, what it covers, cancellation deadline.
• Deduct it from the final bill — never keep it as an extra.
• If the guest no-shows without cancelling within your stated window, the deposit is compensation for the blocked table.
• Keep written proof the guest accepted the policy (a confirmation message works).

A real-world check: the Comunidad de Madrid's consumer FAQ answers the exact scenario — a guest gives card details at booking, no-shows, and gets charged. Verdict: legal, provided the total price including cancellation and no-show charges is clearly known to the consumer beforehand. This is the same mechanism hotels use as preauthorization: holding an amount on the card at booking instead of charging it — useful for restaurants that don't want to charge upfront, with the same disclosure duty.

This is general information, not legal advice — for edge cases (large events, fixed menus with suppliers), check with your asociación de hostelería.

How much to charge

There is no legal cap — the market norm is enough to make flaking hurt, not enough to scare the booking away:

Two rules of thumb: scale the deposit with the cost of the empty table, not with the group's politeness; and announce it as policy ("reservations are confirmed with a €15 deposit per person") rather than as a negotiation.

Collecting deposits by WhatsApp

The moment of friction decides whether deposits work. If collecting one means a bank transfer with proof-of-payment screenshots, guests abandon the booking. The flow that works:

1. Guest books (WhatsApp, phone, or your booking link).
2. You reply confirming availability and send a payment link for the deposit — same chat, seconds later.
3. Guest pays by card (or Bizum where available) from their phone.
4. The reservation locks in automatically once paid; the amount registers against the booking and is deducted from the final bill.
5. Automatic reminder the day before — with the cancellation window stated.

WhatsApp is where your guests already are — meeting them with the payment link inside the same conversation removes the friction that kills deposits. Platforms like Mesabot build this in: deposit request, payment confirmation, and reminder flow attached to the booking itself, instead of juggling a POS, a bank app and a chat.

What booking software charges for deposits

If you collect deposits inside reservation software instead of a payment link in the chat, check which plan actually includes the feature — on every major platform in Spain it sits behind the higher tiers or a paid add-on. Verified on each vendor's own pricing page in September 2026:

• Restoo — deposit collection ("cobra anticipos en 15 segundos") and no-show elimination start at Premium, €149/month. The cheaper Mini (€39) and Pro (€79) plans don't include them.
• Resmio — "pedir depósito para reservas" is a paid add-on at €19.90/month on top of the plan (Premium €69.90 / Ultimate €129.90), so real deposit capability starts near €90/month.
• CoverManager — preauthorization and deposits ("preautorización & depósitos") are reserved for Premium at €189/month; Essential (€89) manages the booking but not the deposit.

The pattern: the feature that protects your revenue is the one used to push you up a tier — budget for it when comparing a €39 entry price against a chat-native flow where the deposit link costs nothing extra.

One more data point: nowEat includes anti-no-show deposits in its single plan at €50/month (€40/month billed annually) — but adds a €1.50 fee on every booking that carries a deposit, with 100 SMS included. The feature is included, yet each protected reservation still costs extra: at 100 deposit bookings a month that's €150 on top of the plan. Compare structures, not just the headline price.

Weighing pros and cons before you start

For:

• Attendance on protected slots: OpenTable reports deposits cut no-show rates by 57% on average (and make guests 72% less likely to cancel at the last minute), against the 10-20% no-show share restaurants assume without a policy; CoverManager cites a -35% no-show reduction once a deposit is required.
• Cash-flow and prep certainty: locked tables mean real purchase decisions on staff and stock for peak nights.
• Filters unserious bookings automatically — the policy does the screening, not your phone.

Against:

• Friction at the exact moment of booking: every extra step loses part of the parties, mostly casual ones.
• It reads poorly if applied everywhere: deposits on midweek tables signal distrust and push those bookings to competitors.
• It adds work when charged outside the booking flow: transfers, proofs of payment, manual tracking — and refund handling when plans change.

The market answer to "against" is structural: deposits only where the risk justifies them, auto-collected inside the conversation the booking already happens in.

Putting it in place: a 5-step checklist

1. Pick the threshold: which bookings carry a deposit — market practice is groups from 8 up, weekend prime time, holidays and fixed menus (a reservation software guide recommends the 8-cover mark).
2. Set the amount from the table above: €10-20 per person, or 30-50% on fixed menus — enough to hurt a no-show, not the booking.
3. Write the policy in one sentence and publish it on the booking channel itself: amount, deduction from the bill, cancellation deadline.
4. Choose the collection route: payment link inside the WhatsApp booking chat (no extra tooling) or a software plan that includes the feature — checking the add-on and per-booking fees first.
5. Automate the day-before reminder with the cancellation window stated, and decide in advance the refund rule for resold tables.

What happens to the no-show's deposit

With the policy stated in advance, keeping the deposit when a guest no-shows inside the cancellation window is the compensation for the blocked table — that is the whole point of the mechanism. Two practices that keep it fair and defensible:

• Publish the cancellation deadline (24-48h for standard bookings) and honour it: if they cancel in time, refund in full.
• Refund no-questions when you resell the table — goodwill costs less than a bad review.

Do deposits scare customers away?

Handled well, no: a clear, small, deductible deposit reads as professionalism, not distrust. Completion rates stay high when the payment is one tap inside the booking conversation. What does scare guests away: surprise charges on the bill, deposits on a Tuesday lunch, and refund policies buried in fine print.

In short

Charge deposits where the risk justifies them — groups, weekends, holidays, fixed menus — at €10-20 per person, state the policy before confirming, deduct from the bill, and collect with a payment link in the same WhatsApp conversation where the booking happened. The restaurants losing money to no-shows in 2026 are not the ones charging deposits; they are the ones still taking bookings with nothing attached. And the deposit is one piece of a larger system: the guide to reducing no-shows explains how reminders, confirmations and a waitlist fit around the deposit. And if you are weighing which platform should run those deposits, Mesabot vs CoverManager compares the two where it matters: who answers the booking, and where the deposit sits in each plan.