
hidden costs restaurant no-shows | restaurant no-show food waste | true cost of no-shows restaurant
The Hidden Costs of Restaurant No-Shows Most Owners Never Count
February 24, 2026 — Most restaurant owners know no-shows are a problem. Very few know the actual number.
Not the vague "it's costing us money" feeling. The precise, monthly, pounds-and-euros figure that's walking out your door every week in the form of empty chairs.
We've talked to dozens of restaurant operators over the past few months. When we ask them to guess their monthly no-show cost, they're almost always off. Not by a little. By 40-60%.
Here's why: they count the empty table. They don't count everything around it.
The visible cost (what you already know)
This part is straightforward. Take your no-show rate, multiply by your covers, multiply by your average ticket.
A 70-seat restaurant doing 80% online bookings with a £52 average spend and 12% no-shows loses about 8 covers a night. That's £416 per night. £2,500 per week. Over £10,000 per month.
That number alone should make you uncomfortable. But it's actually the small part.
The invisible costs (what you're not counting)
Wasted prep. Your kitchen preps based on expected covers. Every no-show means food that was portioned, prepped, sometimes partially cooked, and never served. On perishables with tight margins, that's real money. Most restaurants estimate 3-5% food waste directly attributable to no-shows.
Overstaffing. You scheduled based on a full book. Three no-show tables means you've got a server covering a section that's generating half the revenue you planned for. You're paying the same labour cost for fewer covers. Over a month, this adds up to hundreds in unnecessary wage costs.
Turned-away guests. This is the big one that nobody tracks. When your book looked full at 6pm, you told walk-ins and late callers there was no space. Then two tables didn't show at 7:30pm and those chairs sat empty all night. You'll never know how many paying customers you turned away for people who never came.
Morale. Harder to quantify but real. A server who gets a section of no-shows makes less in tips. A kitchen that preps for 80 and serves 65 feels deflated. Over time this affects retention. And replacing a server costs a lot more than a few empty tables.
The deposit "solution" has its own hidden cost
Some restaurants look at these numbers and immediately reach for card deposits. And yes, no-shows drop to 2-3%.
But the cost shifts somewhere else.
We've seen it consistently across markets: requiring a card at booking drops reservation volume by 20-30%. The people who bounce aren't your no-show risks. They're legitimate diners who don't want to enter payment details for a casual dinner.
So now you're doing the maths on a different problem. If deposits cost you 25% of bookings on a £52 average ticket across 56 online covers per night (80% of 70 seats), that's 14 bookings lost per night. £728. Per night.
The no-shows were costing you £416. The "solution" is costing you £728.
This is the trap most restaurants don't see until they've been running deposits for a few months and wonder why revenue hasn't actually improved.
How to calculate your real number
You need three figures:
Your monthly covers from online bookings. Not total covers, just the ones that come through your booking platform. That's where no-shows live.
Your average ticket. Be honest. Use your actual data, not the aspirational number.
Your no-show rate. If you don't track this precisely, use 12%. That's the industry average for restaurants without deposits. If you use deposits, you need to also estimate how many bookings you're losing to friction (compare your booking volume before and after you introduced them).
Multiply those three together and you've got your baseline visible cost. Then add 15-20% for the invisible costs (prep waste, labour, turned-away guests).
We built a calculator that does this in 30 seconds if you don't want to do it manually.
Luigi No-Show Cost Calculator →
The number will probably surprise you. It surprised us when we first ran it for our own operations.
What changes when you know the number
Once you see the actual figure, the conversation shifts. It's no longer "no-shows are annoying" but "I'm losing £11,000 a month and I need to decide how to recover it."
The options are limited:
Do nothing. Accept the loss. Some restaurants genuinely decide this is the cost of doing business. Fair enough, but at least make it a conscious decision with the real number in front of you.
Card deposits. Reduces no-shows but creates a bigger revenue hole through lost bookings. The maths rarely works out unless you're a Michelin-starred restaurant where demand far exceeds supply.
Manual confirmation calls. The most effective method. Restaurants that call every reservation see no-show rates of 3-5%. The problem: it takes 1-2 hours daily and requires a dedicated person or eats into management time that should be spent elsewhere.
Automated confirmation calls. Same psychology as manual calls (verbal commitment, human-feeling interaction) but without the daily time investment. This is what Luigi does. No-shows drop to 4-6% with zero change to the booking experience. No card form, no friction, no lost reservations.
The real ROI question
The question isn't "can I afford a no-show solution." It's "can I afford not to have one."
If your no-shows cost £10,000 per month and a solution recovers 60-70% of that, you're looking at £6,000-7,000 in recovered revenue monthly. Against a tool that costs a fraction of that.
But don't take our word for it. Run your numbers. See what comes out. Then decide.
INTEGRATIONS
Luigi works with your reservation system
Whether you're on OpenTable, Zenchef, SevenRooms, or another platform — Luigi connects without changing your setup.