Restaurant no-show cost calculator: how much you actually lose every week
How much do no-shows really cost you? Calculate your yearly loss in three numbers. And see how Heep recovers 80% — live in a few days, no migration.
An operator knows the occupancy rate down to the cover. Ask what no-shows cost last year and the number isn't there. It's a question of scale: a no-show is witnessed table by table, and paid for over twelve months.
Across Europe, one reservation in seven never shows up: 14%, according to the Zonal/CGA study. On a 60-cover service, that's 8 empty seats every evening.
Why 1 in 7 reservations never shows up
Three reasons keep coming back, and none is bad faith: forgetfulness, double-booking across platforms, last-minute disruption. A manual call the day before handles none of them properly.
The tab adds up fast. A Friday at 8 pm, losing 4 covers at £35 each is £140 gone in a single service. Spread that over 52 weeks and the annual hit gets heavy.
- 14% Average no-show rate (Zonal/CGA Europe study)
- £35 Average ticket (Traditional dining, France 2025)
- −10 to −20% Monthly revenue loss (Sources: The Fork, Zenchef)
Want your own number, not the industry average? Run my real loss
The calculator: your loss in real numbers
Here is the formula. Weekly reservations × average party size × no-show rate × average ticket: that gives you one week. Multiply by 52 and you have the year.
Two precautions: use your own rate rather than the sector's 14%, and the average ticket of the service concerned. A Saturday no-show does not cost the price of a midweek lunch.
It's a conservative floor, drinks not included.
Why your manual reminders no longer work
The host calling guests the day before? That's 20 minutes a day, 30% of calls hitting voicemail, and no follow-up after. The guest forgets anyway.
What changes is not the wording. It is the number of windows: an SMS at D-1, a WhatsApp four hours before, a one-tap confirmation. 98% read rate, no-shows cut by 5x.
80-cover bistro in Paris: £1,240 recovered every single week
The starting volume: 200 reservations a week, average ticket £38, no-show rate at 13%. Six weeks after automation, it is down to 2.5%.
- −81% No-show rate
- +£1,240 Revenue saved / week
- £64,480 Annual revenue saved
The 4 levers that cut no-shows by 5x
Automated SMS reminder at D-1
The most-read channel, 98% within 5 minutes. Personal, never robotic, with a one-tap "I'm coming" or "Cancel" button.
One-tap confirmation 4 hours before
The last useful switching window. The guest confirms or cancels in a second, and the freed cover goes back on sale.
Card hold above 6 covers
Not a deposit, a pre-authorisation taken through your booking system. The threshold matters more than the principle: regulars accept it without friction.
Waitlist called back the same evening
Once the slot passes with no arrival, the table should go back out by SMS to your waitlist. Average recovery observed: 73%.
What Heep actually changes
- Native multi-channel. SMS, WhatsApp, email, Instagram. Each reminder picks the most effective channel for that specific guest.
- Unfinished requests get followed up. A booking started and never completed goes back out as a message a few minutes later.
- Card hold inside the booking flow. The link is pulled from your reservation software and sent on the slots you consider at risk.
- Syncs with your current stack. Zenchef, TheFork, SevenRooms, OpenTable: Heep aligns with your reservation calendar without migration.
Don't chase a rate of zero, chase your own. Over four weeks, log the covers booked that never turned up, then project over twelve months. It's the one number nobody can hand you.
Go deeper: the card-hold playbook · the 2026 cancellation policy template · SMS automation that moves the needle.
Frequently asked questions
What is the average restaurant no-show rate?
Around 14% of reservations according to the Zonal/CGA study, with spikes above 20% on Friday and Saturday evenings. Tourist areas and premium venues often run higher than the European average.
How do I calculate my no-show cost?
Simple formula: (weekly reservations) × (average party size) × (no-show rate) × (average spend). Run it on your own four numbers, then multiply by 52 for the annual figure.
Does a card hold scare off guests?
Not if it's applied at the right threshold (from 6 covers, or for peak services). It's a pre-authorisation, not a charge. Regulars accept it without friction.
Does Heep integrate with my current reservation system?
Yes. Heep syncs with Zenchef, TheFork, SevenRooms and OpenTable. No migration required. Live in a few days.
