
how much do no-shows cost a restaurant | restaurant no-show cost | cost of no-shows restaurant
How Much Do No-Shows Really Cost Your Restaurant? (The Math Most Owners Get Wrong)
March 9, 2026 β Most restaurant owners know no-shows hurt. What they don't know is how much.
Run the actual numbers and most people are surprised. Not a little surprised. The kind of surprised that makes you sit down and stare at the wall for a second.
Here's the math β and why most restaurants are underestimating the damage by 40 to 60%.
The Standard Calculation (And Why It's Wrong)
Ask a restaurateur how much a no-show costs them, and they'll usually say something like: "A table of 2 at β¬40 average spend. So β¬80."
That's the floor. Not the ceiling.
The real cost of a no-show has three layers β and most people only count the first one.
Layer 1: The Direct Revenue Loss
This one's obvious. A table that doesn't show up is a table that doesn't spend.
The formula:
Party size Γ Average spend per cover = Direct loss per no-show
Example: a table of 3 at a restaurant with a β¬65 average ticket = β¬195 lost per no-show.
But that's not the full story.
Layer 2: The Multiplier Effect (The Part People Miss)
Here's where it gets brutal.
A no-show during a full service doesn't just cost you that one table. It costs you the table you could have given to someone who was waiting. In other words: the real cost isn't just the empty table β it's the table you actively turned away.
Direct loss + Opportunity cost = True no-show cost
And in a restaurant running at 80β100% capacity on a Friday or Saturday night, those numbers are identical. You lost β¬195 and you turned away β¬195 worth of other guests.
Real cost per no-show on a full service night: β¬390.
Most restaurant owners never account for this. That's why they underestimate the damage by half.
Layer 3: The Monthly Hit (This Is the One That Stings)
One no-show is annoying. Thirty is a structural problem.
The monthly calculation:
Covers per day Γ No-show rate Γ Average ticket Γ Days open per month = Monthly revenue leak
Let's run a real example for a mid-size London restaurant:
- 120 covers per service
- 10% no-show rate (industry average without deposits or confirmation calls)
- Β£65 average ticket
- 25 service days per month
120 Γ 10% = 12 no-shows per day
12 Γ Β£65 = Β£780 per day
Β£780 Γ 25 = Β£19,500 per month
Nearly Β£20,000 a month in direct revenue loss. Before you count the opportunity cost.
That's not a rounding error. That's a salary. That's a renovation. That's a year's rent payment gone quietly out the door.
"But Our No-Show Rate Is Lower Than 10%"
Maybe. But here's the thing: most restaurants don't actually track their no-show rate with precision. They feel it β they don't measure it.
Industry data consistently puts average no-show rates at 8β15% for restaurants relying on SMS and email reminders alone. Without any active confirmation system, 10% is a conservative estimate, not a pessimistic one.
And that's before you factor in partial no-shows β tables of 6 where 2 people show up, or a group that downgrades from a tasting menu to three courses because "two of us can't make it."
The Deposit Trap
The instinctive response to no-shows is to ask for a credit card deposit. Makes sense in theory.
In practice, deposits reduce your booking volume by 20β30%. The guests who never book in the first place don't show up as a no-show in your data β but the table still sits empty.
You've traded one problem for another. And you've also introduced a layer of friction that pushes potential regulars toward the restaurant down the road that doesn't ask for their card details.
There's a detailed breakdown of this trade-off in our article on credit card deposits vs. voice confirmation β.
What Fixing This Actually Looks Like
The economics are straightforward. If a restaurant spending Β£299/month on Luigi recovers even 5 no-show tables per month at Β£65 average, that's a 30x return on investment before the month is out.
The lever is confirmation. Not deposits. Not stricter policies. Not longer cancellation windows.
When a real voice calls a guest 24 hours before their reservation β not a reminder SMS that gets ignored, not an automated email β the psychological dynamic changes. The guest feels expected. They feel a social commitment. And they either confirm, or they cancel with enough notice to fill the table.
That's the entire mechanism. Hear Luigi in action β
Calculate Your Own Number
Every restaurant is different. The best way to know what no-shows are costing you is to run your own numbers.
Use the Luigi ROI Calculator β
Enter your covers, average ticket, and no-show rate. You'll have your monthly loss in 30 seconds.
Most people do it once and don't close the tab for a while.
The Bottom Line
No-shows aren't a minor inconvenience. For most premium restaurants, they're the single largest preventable revenue leak in the business.
The math isn't complicated. A 10% no-show rate on a 120-cover service is nearly Β£20,000 a month walking out the door β before you count the guests you turned away.
And the fix doesn't require deposits, stricter policies, or operational overhaul. It requires one phone call, made at the right moment, in the right tone.
That's Luigi.
Related reading
INTEGRATIONS
Luigi works with your reservation system
Whether you're on OpenTable, Zenchef, SevenRooms, or another platform β Luigi connects without changing your setup.