Restaurant No-Shows: Should You Take a Deposit?

Quick answer

Deposits cut restaurant no-shows sharply, but they also cost you bookings, so the question is which slots deserve one rather than whether to have a policy.

A no-show costs you the whole table, not the meal. The seats sat empty through your best hour, you staffed for them, and you turned away a walk-in who would have paid. Deposits do reduce no-shows, sharply and reliably. They also reduce bookings, which is the part nobody selling you a deposit tool mentions. So the useful question is not whether to have a policy. It is which slots are worth protecting and which ones you should leave alone.

Key takeaways

What a no-show actually costs

Run the arithmetic once and the urgency makes sense.

A four-top at an average of ₹500 a head is ₹2,000 of revenue. Lose two of those on a Saturday and you are down ₹4,000 on the night that carries your week. Across a year at even a modest rate, this is real money, and none of it shows up as a line item anywhere in your accounts. It is simply revenue that never arrived.

The costs stack in a specific order. You lose the covers. You lose the prep, if the booking was for a set menu. You keep the staffing, because you rostered for a full room. And you may have turned away a walk-in party at 8:30pm who would have taken the table and paid.

That last one is why no-shows hurt most exactly when you can least afford them. On a quiet Tuesday a no-show costs you a table you would not have filled anyway. On a Saturday it costs you a table someone else wanted.

What the data says

Published figures cluster in a wide but consistent band. Industry reporting puts the average no-show rate between 5 and 20 percent depending on format, price point, and whether deposits are taken, citing research that puts fine dining without a deposit policy as high as 25 to 30 percent, and prepaid prix fixe formats down at 5 to 8 percent. The same source cites TheFork finding that requiring card details to hold a booking cuts no-shows by up to 65 percent.

Two caveats before you act on any of that. These are UK and global figures, not Indian ones, and no reliable Indian no-show benchmark is published that we could find. And they come from companies that sell reservation software, so read the direction of the effect rather than the precise number.

The direction is not in dispute, though. Asking for a commitment reduces the number of people who fail to honour it. That has never really been the interesting question.

India already has the answer, and you control it

Here is the thing most Indian owners do not act on: the deposit mechanism already exists in the market you sell in, and it is yours to set.

A cover charge on Zomato Dining, now shown inside the District app, is a redeemable deposit. The guest pays it at booking, and it is adjusted into their final bill when they turn up and settle through the app. If they do not turn up, it is typically forfeited. That is a no-show deposit in everything but name, and the restaurant sets the amount and keeps the bulk of it. We break down exactly how it works in what a cover charge on Zomato is and, for the newer app, cover charge in the District app.

Most owners treat it as a platform feature that happens to them. It is a lever. The amount is a decision, the slots it applies to are a decision, and whether you use it at all is a decision.

Which matters, because the alternative for a direct phone booking is asking a guest for a UPI transfer to hold a table, and that conversation goes badly far more often than a cover charge shown at checkout in an app the guest already trusts.

The cost nobody mentions

Every deposit policy filters two groups at once. It filters the people who would have ghosted you. It also filters people who would have come, but who were not going to hand over money to a restaurant they have not eaten at yet.

For a booked-out Saturday, that trade is obviously good. You have more demand than tables, so losing a few tentative bookings costs you nothing and the no-shows you prevent are pure recovery.

For a Wednesday at 7pm with fifteen empty tables, the same policy is a straightforward loss. You have deterred a booking you would have been delighted to have, in order to protect a table nobody else wanted.

This is why a blanket deposit policy is usually the wrong answer, and why the restaurants with the best no-show numbers are often not the ones with the strictest rules. They are the ones who apply friction only where the table is genuinely scarce.

Do the free things first

Before charging anyone anything, there is a set of levers that cost nothing and recover most of the loss.

Confirm, then remind. A confirmation at booking and a reminder a few hours before, with a one-tap way to cancel, converts a chunk of silent no-shows into cancellations you can refill. A cancellation at 4pm is a table you sell. A no-show at 8pm is not.

Make cancelling easy on purpose. It feels backwards. It is not. You want the guest who has changed their mind to tell you while the table is still sellable, and any friction in cancelling produces silence instead.

Call back the large tables. A party of eight is worth a personal confirmation call on the day. It is also the booking that hurts most when it evaporates.

Keep a walk-in list. If a booking has not appeared fifteen minutes in, the table should go to someone waiting, with a clear and consistently applied hold time.

Overbook the slots you know slip, carefully, once you have enough history to know your own rate. Airlines have done this for decades. Get it wrong and you have angry guests standing in your doorway, so this is the last lever, not the first.

Where a deposit earns its place

Reserve the friction for tables that are genuinely scarce.

Everywhere else, take the booking and use the free levers.

If you do set a cover charge, keep it small and clearly redeemable. The point is a credible commitment, not revenue. A few hundred rupees a head that comes straight off the bill does the job, and it reads as fair. A large non-redeemable fee reads as a penalty and costs you the booking and the goodwill.

The other half of the problem

One closing thought, and it is the one that applies whether or not you ever take a deposit.

A no-show costs you a table's worth of revenue. So does a table that turns up, orders conservatively, and leaves. The first is dramatic and feels like theft. The second happens every single service and nobody notices, and across a month it costs most restaurants considerably more than their no-shows do.

We do not sell a reservations system, so we have no dog in the deposit fight. What we would say is that the covers you do get are the cheaper problem to fix. Raising what a seated table spends is entirely within your control, needs no policy, and annoys nobody: that is the whole argument for working on average order value, and for bars specifically, on selling the next round before the table goes quiet.

Protect the scarce slots with a deposit. Then go and look at what the tables that did show up actually spent.

FAQ

What is a normal no-show rate for a restaurant?

Published figures put the industry range at roughly 5 to 20 percent, with fine dining without deposits reported as high as 25 to 30 percent and prepaid formats below 8 percent. These are UK and global figures rather than Indian ones, and no reliable Indian benchmark is published, so track your own rate before comparing yourself to anyone.

Do deposits reduce restaurant no-shows?

Yes, substantially. Reservation platforms report large reductions when card details or a deposit are required, and prepaid set menus see the lowest rates of all. The trade-off is that a deposit also deters some genuine bookings, which makes it worthwhile on scarce slots and counterproductive on quiet ones.

Can an Indian restaurant charge a booking deposit?

Yes, and the common mechanism is the redeemable cover charge shown at booking on Zomato Dining or the District app. The restaurant sets the amount and keeps the bulk of it, and it is adjusted into the guest's bill when they arrive and pay through the app. For direct phone bookings, asking for an advance transfer is possible but far more awkward in practice.

Should I charge a no-show fee?

Prefer a small redeemable deposit over a punitive fee. A cover charge that comes off the final bill reads as fair and still creates commitment, whereas a large non-redeemable charge tends to cost you the booking and the relationship. Keep any policy clearly stated at the time of booking.

How do I reduce no-shows without charging anything?

Confirm at booking, remind a few hours before, and make cancelling genuinely easy so changes of mind arrive while the table is still sellable. Call back parties of six or more on the day, hold late tables for a fixed and consistent window, and keep a walk-in list to refill. These recover most of the loss at no cost.

What to do next

Work out your own no-show rate for the last month, split between weekend prime time and everything else. Almost every restaurant finds the problem is concentrated in a few slots rather than spread across the week, which means a blanket policy would be trading away quiet-night bookings for nothing. Put a small redeemable cover charge on the scarce slots only, turn on confirmations and reminders everywhere, and leave the rest alone.

See it on a real table

A 15-minute demo: watch dineomAI take an order, speak five Indian languages, and upsell the right pairing. No hard pitch.

Book a 15-minute demo →