How to reduce no-shows at your restaurant
You cut no-shows by stacking four layers: confirm the booking the moment it comes in, remind 24 hours before, keep a clear and visible policy, and ask for a deposit only on large parties and peak slots. No single measure fixes it; the full system does. In Spain the average rate was around 3.3% in 2025 (TheFork), and SMS reconfirmation plus card deposits can bring it down meaningfully. This guide explains the why behind each tactic and how to set it up without scaring away bookings.
What a no-show is and why it hurts so much
A no-show is a booking that never turns up and never warns you. It is not a cancellation —that, at least, gives you room to reseat the table—: it is an empty chair you discover too late, with the kitchen already firing, the produce bought and, very often, real guests you turned away because you were full.
It hurts for three reasons that pile up. First, margin: in hospitality profit lives in a handful of points, and one empty table on a full service eats the profitability of the whole night. Second, sunk cost: you bought fresh product and staffed the floor for covers that never arrive. Third, and quietest of all, opportunity cost: every ghost table is almost always another booking you declined. On a Friday at 9pm, that is gone for good.
That is why a no-show is not measured only by the ticket you missed, but by everything it drags with it. Seen this way, the question changes: it is not "how do I punish the one who didn't show?" but "how do I get most of my bookings to actually turn up?".
What a no-show really costs
A no-show costs, on average in Spain, around €78 per table that fails to show. That figure comes from crossing two TheFork data points for 2025: an average spend of €27 per diner and an average party size of 2.9 people, which works out to roughly €78.30 of potential revenue lost per ghost table.
It sounds small until you multiply it. With an average no-show rate of 3.3% (TheFork, 2025, down from 3.6% in 2024), a restaurant handling 500 bookings a month loses around €1,292 a month: more than €15,500 a year. And not every table weighs the same: a party of 6 that vanishes is about €162, and one of 10 climbs to €270, using that same average spend as the benchmark.
Two honesty notes. One: these are sector averages, not your specific case —if your average ticket is €45 or €90, the maths changes entirely. Two: these figures measure lost revenue, not profit; the real damage depends on your margin. To see it with your own numbers, use Qomanda's no-show calculator.
Why people don't show up (and it's rarely bad faith)
Most no-shows are not sabotage: they are forgetfulness and friction. According to a 2025 TheFork survey, 55% of those who didn't show simply forgot the booking, 38% had a last-minute problem and 7% admitted they were embarrassed to cancel. That profile is good news, because forgetting and embarrassment are solved with product, not punishment.
On top of that sit two very modern habits. The first is multi-booking: people who hold a table in three places "just in case" and decide on the fly. The second is friction to cancel: if calling by phone during service is the only way to cancel, many people simply won't, and just don't turn up. When cancelling takes a single click, a share of those no-shows becomes timely cancellations —and a cancellation with notice is a table you can sell again.
The operational takeaway is clear: before tightening policies, remove friction and refresh the guest's memory. That is where most of the recoverable ground lies.
The tactics that actually work
There is no silver bullet; there is a layered system, ordered from least to most demanding on the guest. The first layers (confirmation, reminder, easy cancellation) recover forgetful guests with very little effort and bother no one. The last ones (deposits, prepayment) are heavy artillery: they slash no-shows, but use them with judgement so you don't scare off legitimate bookings.
The data backs this order. In a CoverManager analysis of 9,500 Spanish restaurants (Father's Day 2025), bookings with no protection had a 1.92% no-show rate; with an automatic SMS reconfirmation it dropped to 1.52% (around 21% lower), and when a card or prepayment was requested it fell to 0.66% (nearly 66% lower). In short: the reminder is the simple, universal fix; the deposit is the powerful, selective one.
The eight steps below are that system, in order of rollout. You don't need to switch them all on at once: start with reminders and policy, measure, and move up a layer only where the numbers demand it (large parties, peak hours, key dates).
How Qomanda solves it (and what it doesn't do)
Qomanda brings all those layers into a single tool: automatic confirmations, SMS reminders, one-click cancellation straight from the email, a waitlist to reseat tables instantly, a CRM with history to flag repeat offenders, card deposits and holds —via Stripe, charged onto the restaurant's own account— and analytics that tell you how many no-shows you have by source and by service. Instead of five separate tools, one panel you already know from the pass.
Let's be honest about what Qomanda is not: it is your own booking engine, embedded in your website, not a portal or a marketplace. A marketplace like TheFork can bring you brand-new diners from its portal; Qomanda does not do that. In exchange, it charges no commission per diner or per booking: it is €49 a month per restaurant, with 30 days free and no card required, and no lock-in. If you run volume, that gap between a flat fee and a per-head commission adds up fast by month's end.
And there is no call centre behind it: Qomanda is built by Alture, a team in Granada that works with local restaurants. When you write, the people who make the product are the ones who reply.
Ways to cut no-shows, in order.
- 01
Confirm the booking the moment it comes in
As soon as the booking lands, send an email or SMS confirmation with the details spelled out (date, time, party size, restaurant name) and a button to cancel or modify in one click. The confirmation is not a formality: it cements the commitment and gives the guest an easy way to warn you if plans change.
- 02
Send a reminder 24 hours before
Forgetting is the number-one cause of no-shows, so target memory. An SMS the day before with an option to reconfirm or cancel recovers a good share of the absent-minded. In the CoverManager study, SMS reconfirmation cut no-shows from 1.92% to 1.52%. It is the best effort-to-result measure there is.
- 03
Publish a clear, visible policy (and enforce it)
State inside the booking engine itself what happens if guests don't show: grace period, cancellation deadline and whether a deposit applies. A policy visible at the moment of booking reduces the sense of anonymity and curbs the "I'll book just in case" habit. What matters is not that it be harsh, but that it be clear and always applied.
- 04
Turn on the waitlist to reseat instantly
A late cancellation or a no-show spotted in time need not be a lost table if you have someone to call. Keep a waitlist per service and notify automatically when a slot frees up. Turning ghost tables into filled tables is half the battle.
- 05
Ask for a deposit on large parties and peak slots
Don't ask for a card on every booking: save that artillery for where no-shows hurt most —parties of 6 or more, Friday and Saturday nights, key dates. In the CoverManager study, requiring a card or prepayment cut no-shows to 0.66% (nearly 66% lower). With Qomanda the deposit is charged via Stripe onto the restaurant's own account.
- 06
Flag repeat offenders in the CRM
A guest who has already stood you up twice does not deserve the same treatment as a new one. With a CRM that stores history you can tag repeat offenders and apply different conditions: a confirmation call, a mandatory deposit, or simply more caution before handing them a prime table at peak time.
- 07
Use controlled overbooking, only with data
If your data shows a recurring, predictable no-show rate on certain services, you can overbook slightly to offset it, just as airlines do. It is a precision tool, not a free pass: do it only on reliable historicals and with a plan for when everyone shows up. Miscalibrated, it breeds waits and bad reviews.
- 08
Measure and adjust every month
You can't improve what you don't measure. Review your no-show rate by booking source and by service, and check which layer is moving the needle. Reminders may be enough midweek while you only need deposits at weekends. Analytics turn this system into continuous tuning, not a rigid rule.
Before you make the move.
What restaurants thinking about switching usually ask us. No fine print.
The national average was around 3.3% in 2025, according to TheFork (down from 3.6% in 2024). It's a useful benchmark, but your real rate depends heavily on your type of venue, your area and your peak hours: a group-and-weekend-night spot usually suffers more no-shows than a weekday set-menu lunch. What matters is not comparing yourself to the average, but measuring your own rate by service and watching it fall month over month.
Fill your room.
We handle the rest.
We migrate your restaurant with you and stay through the launch. You run the service; the software is on us.
€49/mo · no fees · 30 days free · cancel anytime