How much should a restaurant charge as a reservation deposit per guest?

Start from the cost of an empty seat, not from a round number

The right deposit is tied to what a no-show actually costs you. For most full-service restaurants, the loss from an empty two-top is not the whole check; it is the contribution margin you would have earned on that seating, plus any food prepped specifically for that booking. Estimate your average spend per head, subtract the food and beverage cost you avoid when nobody shows, and you have a rough ceiling. A deposit in that range reimburses the real loss without looking punitive. Going far above it invites arguments and disputes; going far below it turns the deposit into a symbolic gesture that nobody thinks twice about forfeiting. Related: Why No Shows Hurt Restaurants So Much

In practice, most restaurants land on a flat per-guest amount rather than a percentage, because a flat number is easy to say on the phone, easy to print in a confirmation, and easy for a host to explain. Round to something clean. A per-guest figure that sits somewhere between a cocktail and an entree at your price point is a common starting place for a la carte dining, while fixed menus and tasting formats typically move toward a larger share of the menu price or full prepayment. The exact number matters less than whether it is meaningful relative to what a guest expects to spend with you.

Keep reading: Why No Shows Hurt Restaurants So Much, How a Deposit Changes Behavior, Making Deposits Guest Friendly. See how HoldTabl helps you no-show deposit collection for restaurant reservations.

Scale by party size, day, and how hard the table is to resell

One number for the whole book is simple, but it ignores how differently a Tuesday two-top and a Saturday eight-top behave. Large parties are harder to rebook on short notice and they tie up several tables' worth of revenue, so a higher per-guest deposit, or a deposit that only kicks in above a certain party size, is easy to justify. Prime slots on Friday and Saturday evenings carry more risk than a weekday lunch, and many operators only require deposits on those nights. Special events and holidays sit at the top of the scale because the food is bought and prepped in advance. Related: Making Deposits Guest Friendly

A tiered structure works well as long as it stays short enough to fit on one line of your booking page. Two or three tiers is usually the limit before hosts start misquoting it. Something like no deposit for small weekday parties, a modest per-guest deposit for peak nights, and a larger per-guest deposit or full prepayment for parties above a threshold and for ticketed events covers most dining rooms. Write the tiers down, put them where staff can see them, and resist the urge to add exceptions to the policy itself; handle exceptions as decisions, not as more rules. Related: Which Bookings Need a Deposit

Account for processing costs and refund mechanics

Deposits are card-not-present transactions, and the economics of charging and refunding small amounts are worth understanding before you set the figure. Many payment processors keep some or all of the per-transaction fee when you refund, so a policy that charges and refunds a small deposit on every booking can quietly cost you money on the guests who did show up. If most of your deposits will be refunded or credited, a card hold or a card-on-file arrangement may fit better than a captured charge for smaller amounts. Ask your processor exactly what happens to fees on a refund and whether an authorization is a real option for your booking lead times.

The number also interacts with how the deposit is settled at the end of the meal. If it is applied to the final bill, the guest experiences it as a prepayment rather than a fee, and a slightly higher amount becomes acceptable. If it is refunded separately after the visit, guests notice the wait for the money to reappear on their statement, and a smaller amount reduces the number of calls your host stand fields about it. Decide the settlement method first, then set the amount, because they are not independent decisions.

Test one number, watch three signals, then adjust

Treat your first deposit amount as a starting point rather than a final answer. Pick a figure, apply it to a clearly defined slice of the book such as weekend dinner parties of a certain size, and run it for several weeks. Watch three things: whether no-shows and late cancellations on that slice fall, whether the volume of bookings on that slice changes, and how many guests push back at the point of booking. If no-shows barely move, the amount is probably too small to register. If bookings drop noticeably and the pushback is frequent, it may be too large or poorly explained. Related: How a Deposit Changes Behavior

Adjust one variable at a time. Raising the amount and widening the policy to more nights in the same week makes it impossible to tell which change did what. Keep the booking page copy stable while you test the number, and keep the number stable while you test the copy. Most restaurants find their level within a couple of adjustments, and the final figure tends to be less controversial than owners feared, because the guests who object loudest are often the same guests who were never going to show up anyway.