Restaurant No-Show Cost Calculator 2026

Fourteen percent of restaurant bookings never arrive. That is the Zonal/CGA figure for Europe, and almost every operator I meet nods at it, then explains in the next breath that no-shows are not really a problem in their room. Both are true. That is exactly why nothing gets fixed.

A no-show is never seen as a monthly total. It is seen one table at a time: a Friday, 8 pm, four covers that do not turn up, an average spend of £35. That is £140 out of a single service. Nobody opens a spreadsheet for £140.

Fifty-two weeks of £140 is another conversation.

Why 1 in 7 bookings never arrives

Three causes come back: forgetfulness, double-booking across platforms, plans that change late. None is solved by someone from the floor calling round the day before.

What makes the loss invisible is its shape: fragments, spread over a year, on services that looked full enough. The industry markers, for reference: a 14% average no-show rate (Zonal/CGA Europe), £35 average spend per cover (traditional dining, UK 2025), and a monthly revenue loss put at 10 to 20% by The Fork and Zenchef.

The calculator: your real losses in figures

The formula:

(weekly bookings) × (average party size) × (no-show rate) × (average spend per cover) × 52

Three of the four already sit in your booking software and on your monthly P&L.

The fourth is the one nobody measures. Not 14%: yours. Over the last 30 days, count the bookings marked as arrived and divide by the bookings confirmed. That gap runs higher than the figure quoted from memory: a table cancelled at 6 pm for an 8 pm sitting is filed as a cancellation, not as four empty covers.

Run it twice, once with 14% and once with your own number. The distance is the problem you actually have. Calculate my real loss

Why manual reminders no longer cut it

Calling guests the day before takes 20 minutes an evening, sends 30% of those calls to voicemail and leaves no trace of the rest. One attempt, one channel. The guest forgets anyway.

An automated reminder is a different object, because it is not a single shot. Three windows: an SMS the evening before, a WhatsApp message four hours out, a one-tap confirmation. Read rate, 98%. No-shows divided by five.

Case study, 80-cover bistro in Paris: £1,240 recovered every week

200 bookings a week, average spend £38, no-show rate at 13%. After Heep automation: 2.5% within 6 weeks.

• −81% No-show rate
• +£1,240 Revenue recovered / week
• £64,480 Annual revenue saved

What matters there is the six weeks, not the annual figure: the rate fell once all three windows were running.

The 4 levers that cut your no-shows by 5×

The SMS at D-1 carries the volume: read almost every time, within minutes, with a one-tap "I'm coming" or "I'm cancelling".

The confirmation four hours out is the last useful tipping point: a cover released at 4 pm still finds a buyer.

The card hold from 6 covers is a pre-authorisation, not a deposit. It removes most group no-shows when you set a threshold rather than applying it to everyone.

The waitlist, minutes after a missed booking time, puts the loss back on sale. How much you recover depends on how many people you turned away that same day.

What Heep changes in practice

Each reminder goes out on the channel that works for that guest: SMS, WhatsApp, email, Instagram. Four minutes past a booking time with no arrival, the table is flagged and offered to the waitlist. All of it sits on top of Zenchef, TheFork, SevenRooms or OpenTable, without migration.

The mechanics are detailed in card holds explained and the 2026 cancellation policy template.

One number to take away, and it is not ours: your real no-show rate over 30 days, next to your average spend, multiplied by 52. Whatever you decide next, you will be deciding on a figure that belongs to your room.