How to Reduce Restaurant No-Shows: A Guide for Fine Dining Venues in Asia (2026)

No-shows run around 8% of bookings in mature markets, 10% in Singapore. Deposits cut them by 57%, SMS reminders by 27%. Build a policy that actually works.
Table of contents
Editor's note
This article is published by Revasi and the author is a co-founder. We work with reservation policy decisions every week with restaurants in Bali, Singapore, Bangkok and Jakarta, and the recommendations below reflect what actually works for 30–60 seat fine dining venues in this region. Where the right answer is "use a deposit policy" or "switch off your default reminder flow", we say so even when the conclusion isn't flattering to a particular product feature.
If you run a 40-seat restaurant in Ubud or Singapore and you lose two covers tonight to a no-show, you don't need a study to tell you the impact. At a tasting menu restaurant doing IDR 1,950,000 per cover, two no-shows is roughly USD 240 in lost revenue on a single table, and the kitchen has already prepped for them.
The aggregate data tells the same story. No-shows now run around 8% of all bookings in mature markets (ResDiary, 2024) and roughly 10% in Singapore (Chope, 2024). For a 50-seat restaurant doing two services a night, that's around 70 no-show covers a month, enough to hire a full-time runner if you got even half of them back.
The good news: this is one of the most measurable problems a restaurant has, and it's also one of the most solvable. The interventions that work are well-documented, the trade-offs are well-understood, and almost none of them require a bigger system than you already have.
Key Takeaways
- No-shows in mature markets run around 8% of bookings; Singapore runs higher at roughly 10% based on operator data (ResDiary, 2024; Chope, 2024)
- Requiring a deposit reduces no-shows by an average of 57% and makes guests 72% less likely to cancel last-minute (OpenTable, 2024)
- SMS reminders reduce no-shows by an average of 27%, and 36% of guests who missed a booking said they would have shown up if they'd received a reminder (resOS, 2024)
- 82% of diners are willing to put down a deposit for special occasions or large group bookings, so selective deposits convert better than blanket policies (OpenTable, 2023)
- Acquiring a new fine dining customer costs around 5–7x more than retaining an existing one, so the goal of any policy is to reduce no-shows without scaring repeat guests away
Table of Contents
- What's a Normal No-Show Rate?
- Why Is Asia Different?
- The Three Levers That Actually Move No-Show Rates
- What Doesn't Work (And Why People Keep Trying It)
- Building a Policy That Fits Your Restaurant
- How Revasi Handles This Automatically
- Frequently Asked Questions
What's a Normal No-Show Rate?
If you don't know your current no-show rate, that's the first thing to fix. You can't move a number you can't see. Most operators we talk to either don't track it at all or track it inside a spreadsheet that gets updated weekly when nobody has time to do anything about it.
The benchmark numbers worth knowing: 8% of all UK and Irish restaurant bookings resulted in no-shows in 2023, up from 5% in 2022 (ResDiary, 2024). 76% of venues in that survey said they were materially affected, with average annual revenue loss of £3,621 per venue. Roll that up across the sector and the UK hospitality industry estimates around £17.6 billion in lost annual sales from no-shows (Falstaff, 2024).
Singapore runs noticeably higher. A 10% no-show rate is the working benchmark for Singapore restaurants based on Chope's operator data (Chope, 2024). For a tasting menu restaurant with a group of 8–10 booked at S$300 per cover, a single no-show table is S$3,000 in lost revenue on the night. That isn't a marginal number. It's the difference between a strong service and a thin one.
Fine dining specifically runs higher than the cross-segment average for two structural reasons. Reservations are made further ahead, sometimes 4–6 weeks, which means guests have more time to forget, change plans, or get a better offer. And parties are smaller (usually 2–4), which means each no-show is more visible on the night's covers than a no-show at a 200-seat casual restaurant.
What this means in practice: if you don't have a way to measure your no-show rate today, build that first before you change any policy. We've watched restaurants invest in deposit systems to "fix no-shows" without ever measuring whether their actual rate was 4% or 14%. Those are very different problems and they justify very different policies.
From operator calls we've sat in on
We've spoken with operators who genuinely thought their no-show rate was around 5% and discovered, once their reservation system started tagging it properly, that the real number was closer to 12%. The gap matters: a 12% rate justifies a deposit policy that a 5% rate does not, and most operators learn this the first time they actually measure.
Citation capsule: Restaurant no-shows averaged 8% of all bookings across UK and Irish venues surveyed by ResDiary in 2023, up from 5% the previous year, costing the average venue £3,621 annually (ResDiary, 2024). Singapore restaurants run higher at roughly 10% per Chope operator data, with single group-booking no-shows costing fine dining venues S$3,000+ in a night (Chope, 2024).
Why Is Asia Different?
The published research on no-show rates is mostly UK, US, and EU. The Asia picture is different in three ways that matter for policy design.
The booking mix is different. A meaningful share of fine dining bookings in Bali, Singapore and Bangkok come from international travellers booking weeks ahead of arrival. That booking pattern produces a higher structural no-show rate than a market like London where most diners are local and booking 1–2 weeks out. Travellers cancel trips, miss flights, or simply forget that they booked a tasting menu in a country they're now leaving in five days.
Phone numbers and contactability are messier. A guest from Australia booking a Bali restaurant six weeks before arrival often doesn't have a working SIM in country yet. A reminder SMS sent the day before goes to a phone that's about to be replaced. Email gets used more in Asian fine dining than in UK or US fine dining for exactly this reason, but email open rates are lower than SMS open rates, so the trade-off is real.
Deposit collection is harder. Asian markets are more card-fragmented than the UK or US. A restaurant in Bali can easily be presented with a Singaporean Visa, an Indonesian local debit card, an Australian Mastercard, and a Chinese UnionPay in a single service. Card-hold flows that work cleanly on a US-centric platform sometimes break on regional networks. This is one of the most common operational reasons we hear restaurants in this region cite for not implementing a deposit policy: they tried, the technology didn't quite work, they gave up.
Cancellation policy has tightened recently. Singapore's fine dining sector moved industry-wide from 24-hour to 72-hour cancellation windows during 2024 as a direct no-show countermeasure (Asia News Network, 2024). This is now the working norm in Singapore tasting menu restaurants, and is starting to spread to high-end venues in Bangkok and Bali.
The implication: the framework that works for a Mayfair restaurant doesn't translate cleanly to a 40-seat tasting menu restaurant in Ubud. The mechanics need to be tuned for the actual booking patterns of the region, not retrofitted from a US-centric default.
The Three Levers That Actually Move No-Show Rates
Three interventions consistently move the no-show number. Everything else is noise.
Lever 1: Deposits and Prepayment
This is the single most effective lever and also the one most operators are most reluctant to use. The data is unambiguous: requiring a deposit reduces no-shows by an average of 57% and makes guests 72% less likely to cancel last-minute (OpenTable, 2024). A credit-card hold without an actual charge still produces a 16% reduction, plus a 15% reduction in late cancellations.
The reluctance comes from a real concern: a deposit is friction, and friction reduces conversion. A guest who would have booked your restaurant on a Tuesday whim might not bother if the booking flow asks for a card. That trade-off is real for casual restaurants. For fine dining at a 30–60 seat venue, the math runs the other way: a slightly lower booking volume of guests who are 57% less likely to no-show is more profitable than a higher booking volume with a normal no-show rate.
Where deposits land best:
- Tasting menu restaurants, where every cover is high-revenue and the kitchen prep cost of a no-show is significant
- Group bookings (6+ people), where a single no-show becomes catastrophic. 82% of OpenTable-surveyed diners said they are more likely to put down a deposit for large group bookings or special occasions (OpenTable, 2023)
- Special occasion services like Christmas Eve, Valentine's, NYE, and similar prime dates where demand exceeds capacity
- Weekend prime-time, the Friday and Saturday dinner services at venues that operate at capacity
Where deposits don't fit as cleanly:
- Weekday off-peak services at venues that aren't running near capacity, where the friction costs more than the no-show reduction is worth
- Walk-in-heavy concepts like bars, casual restaurants, neighbourhood venues
- Newly opened restaurants, where the brand isn't yet established enough to absorb the conversion friction
The right framing is selective rather than blanket: 85% of OpenTable-interviewed restaurants said they would use deposits for large parties or specific shifts, but not for all bookings (OpenTable, 2023). That matches what we see with restaurants in Bali, Singapore and Bangkok: a deposit policy that applies to tasting menus, weekends and large groups, but not to a Tuesday two-top, is the configuration that converts well and reduces no-shows materially.
On amount: 30–50% of the menu price, fully redeemable against the bill. Below 20% and the friction-to-impact ratio gets worse. Above 60% and conversion drops sharply for first-time guests. 50% on tasting menus is the most common setting we see in this region.
Citation capsule: OpenTable's 2024 data shows that requiring a deposit reduces restaurant no-shows by an average of 57% and makes guests 72% less likely to cancel last-minute, while a credit-card hold without an actual charge produces a 16% no-show reduction (OpenTable, 2024). 82% of surveyed diners are willing to put down deposits for special occasions or large groups (OpenTable, 2023).
For a closer look at how Revasi specifically implements deposit collection across regional payment networks, see our no-show reduction feature page.
Lever 2: SMS and Email Reminder Sequences
The second lever is simpler, less controversial, and almost universally underused.
SMS reminders reduce no-shows by an average of 27% (resOS, 2024) and 36% of guests who missed a booking said they would have shown up if they'd received a reminder (resOS, 2024). One Chope client restaurant in Singapore reported a 67% reduction in no-shows after activating automated SMS reminders (Chope, 2024). That's an outlier number, but the direction of effect matches the broader research consistently.
The mechanism is unglamorous. Most no-shows aren't malicious. They are guests who genuinely forgot, double-booked, or had something come up and decided not to bother cancelling because they didn't think the restaurant would notice. A reminder 24–48 hours ahead converts a meaningful share of those into either a confirmed attendance or a polite cancellation that gives you time to rebook the table.
The working sequence we recommend for fine dining restaurants in Asia:
- Booking confirmation: immediate, email + SMS, with the date, time, party size, deposit details, and a clear "reply CANCEL" path
- 48-hour reminder: SMS-first, with reconfirmation link. This is the highest-impact touchpoint
- Same-day reminder (4 hours before): SMS-only, short, single-line confirmation
- Post-meal review request: separate from the no-show flow but useful for retention
Two design notes that matter more than people expect:
Make replying easy. A reminder that asks for a button-tap or a one-word reply (CONFIRM / CANCEL) gets significantly higher response than one that asks the guest to call or open a portal. Most no-shows would have been cancellations if cancelling had taken less effort than no-showing.
Use SMS for the time-critical messages. Email open rates run lower than SMS in every market we operate in. Email is fine for booking confirmations and post-meal follow-ups; SMS is the right channel for the 48-hour and same-day reminders, where you actually need the guest to read the message in time to act on it. The Chope-reported 67% reduction came specifically from activating SMS, not from improving email content.
Citation capsule: SMS reminder sequences reduce no-shows by an average of 27% across restaurants using resOS (resOS, 2024), and 36% of guests who missed a reservation said a reminder would have made them attend. A Chope client in Singapore reported a 67% no-show reduction after activating automated SMS confirmations (Chope, 2024).
Lever 3: Cancellation Windows and Policy Design
The third lever is structural rather than transactional: how long before the booking can a guest cancel without penalty?
The Singapore fine dining sector moved industry-wide from 24-hour to 72-hour cancellation windows during 2024 (Asia News Network, 2024). This wasn't a coordinated decision. It was a wave of individual restaurants tightening their policies in roughly the same window because the underlying logic is the same: tasting menu kitchens prep specific portions for specific bookings, and a 24-hour cancellation isn't enough notice to recover the cost of that prep.
The working norm for fine dining restaurants in Bali, Singapore and Bangkok in 2026 is now:
- 48–72 hours: full refund of any deposit
- 24–48 hours: 50% deposit forfeit
- Inside 24 hours: full deposit forfeit
- No-show: full deposit forfeit + a documented internal flag against the guest's record
Two things to note about the structural design.
Match your cancellation window to your prep window. A restaurant whose kitchen starts ingredient prep 48 hours ahead can't honestly claim a 72-hour cancellation deadline. Guests will reject it as unreasonable. A restaurant whose chef does foraging 4 days before service has a defensible case for 96 hours. Tie the policy to the actual operating reality, not to the most aggressive number you think you can get away with.
Communicate the policy at the point of booking. A guest who reads the cancellation policy when they book and accepts it has consented. A guest who is told about it for the first time on the day they try to cancel will leave you a one-star review. Most reservation systems make this easy; very few restaurants take advantage of the placement.
Apply policies consistently. This is the lever where most restaurants break themselves. A deposit policy that gets enforced for an Australian tourist but waived for a regular local guest produces unfair outcomes and damages trust. The right answer is a written policy, applied consistently, with explicit operator discretion only for genuine emergencies (medical, weather, family bereavement) and not for "I just don't feel like going."
What Doesn't Work (And Why People Keep Trying It)
A short list of interventions that don't materially move no-show rates, but that we still see operators reaching for first.
Calling guests to "verify" reservations. This was standard 15 years ago. Today, a phone call from a restaurant the day before a booking reads as suspicious to most international guests, and the call-to-conversion rate is much worse than an SMS or email reminder. The labour cost is also disproportionate.
Posting "no-show shame lists" publicly. A cluster of restaurants experimented with this in 2018–2020 across Singapore, Bangkok and parts of Europe. Outcomes were uniformly negative: media backlash, guest complaints, no measurable change in actual no-show rates. The restaurants who tried this most visibly walked it back.
Dropping reservations entirely and going walk-in only. This works for some venue types like bars and certain casual concepts. For a 40-seat tasting menu restaurant where every cover is booked 4–6 weeks ahead and the kitchen needs to prep specific dietary accommodations, walk-in-only is not a viable model. Some restaurants have tried hybrid versions (most tables bookable, a few held back for walk-ins) and that does work, but it's not a no-show solution. It's a slightly different operating model.
Overbooking by 10–15%. This works in airline operations because cancellations are predictable across thousands of bookings. At a 40-seat restaurant doing 60 covers a night, the variance is too high for overbooking to be statistically clean. You will get nights where everyone shows and you have to apologise to a table you double-booked. The reputational cost of that situation outweighs the recovered revenue from absorbed no-shows.
Charging full menu price for no-shows. Legally available in most jurisdictions if disclosed clearly. Operationally, the chase cost of trying to charge a guest IDR 1,950,000 after they no-showed (the chargeback risk, the dispute time, the customer-service damage) usually exceeds the revenue recovered. A 50% deposit forfeit is the practical maximum for most independent restaurants.
The pattern: the interventions that don't work are mostly ones that try to punish no-show behaviour after the fact, rather than prevent it before the fact. Prevention is structurally cheaper.
Building a Policy That Fits Your Restaurant
A policy that works for Locavore NXT in Lodtunduh doesn't necessarily work for a 12-seat omakase counter in Bangkok or a 200-seat casual restaurant in Jakarta. Here is the shape of the question we would walk a venue through.
Start with the actual no-show rate. Pull six months of bookings from your reservation system. Tag the no-shows. Calculate the rate by service (lunch, dinner) and by day of week. If the rate is below 5% across the board, you don't need a deposit policy. You need better reminders. If it's above 12%, deposits are likely justified. Between 5% and 12%, the picture is more nuanced.
Identify which slices are causing the problem. It's rarely uniform. Most restaurants we work with find that no-shows are concentrated in 2–3 specific slices: for example, Friday and Saturday 7–8pm bookings made more than 4 weeks ahead, or large group bookings (6+) made by international guests. The right deposit policy targets those slices and leaves the rest of the booking flow friction-free.
Match the deposit to the prep cost. The deposit's purpose is to cover the kitchen's actual exposure to a no-show. For a tasting menu restaurant where the kitchen has bought specific ingredients, made specific stocks, and reserved specific kitchen time, 50% of the menu price is reasonable. For an à la carte concept where the prep cost is much lower, a smaller deposit (or just a card hold) is more proportionate.
Audit the reminder flow before you add deposits. If your venue has a 12% no-show rate and no SMS reminders, install reminders first. The 27% reduction from reminders alone may bring you to 8–9%, which is closer to industry-normal and may not justify the conversion friction of deposits. Cheaper interventions go first.
Communicate the change carefully. A restaurant that adds deposits and tightens cancellation windows in the same week without explaining why will absorb a wave of negative reviews. The same change, communicated in a single clear note ("from May 1 we are introducing a 50% deposit on tasting menu bookings, fully redeemable against your bill, to protect the kitchen against last-minute cancellations") usually lands without a problem.
Measure six weeks after launch. Most policies move the no-show rate within 4–8 weeks. If it hasn't moved by week six, the policy isn't working as designed and probably needs revisiting, most often because the cancellation window or the deposit amount is mismatched to the actual booking pattern.
The framework we use most often with Revasi clients is:
| Booking type | Deposit | Reminder cadence | Cancellation window |
|---|---|---|---|
| Weekday off-peak, 2-top | None | Email + 24h SMS | 24h, no penalty |
| Weekend prime-time, 2–4 top | Card hold | Email + 48h SMS + 4h SMS | 48h, full refund |
| Tasting menu, any night | 50% deposit | Email + 48h SMS + 4h SMS | 72h, full refund |
| Group booking 6+ | 50% deposit | Email + 48h SMS + 24h SMS | 72h, full refund |
| Special occasion / NYE / V-Day | 100% prepayment | Email + 1 week + 48h + 24h | 7 days, full refund |
This is a default. Adjust it to your specific venue, but having an explicit table like this (written down, approved by leadership, communicated to staff) is more valuable than any specific row in it.
For a deeper view of how a reservation platform should support this configuration without needing a separate payment processor, see our guide to what to look for in a restaurant reservation system and the regional comparison of SevenRooms alternatives in Asia.
How Revasi Handles This Automatically
The reason we have strong opinions on no-show prevention is that we built the platform around it. Revasi handles deposits, prepayment, reminder sequences and cancellation windows natively rather than as add-ons. A few specifics worth knowing.
Deposits are configurable per booking type. A restaurant can set a different deposit policy for weekend prime-time, tasting menus, group bookings and special occasions without managing four parallel systems. Cards are charged automatically at the right point in the flow, with regional payment networks supported (we deliberately built around Indonesian, Singaporean and Thai card networks because these were the gaps in incumbent platforms).
Reminders are SMS-first by default. The 48-hour and same-day reminders go via SMS unless the guest has opted out, with email as the secondary channel for booking confirmations and post-meal follow-ups. The Chope-reported 67% reduction is the kind of result we see when restaurants flip from email-only to SMS-led reminders.
Cancellation windows are tied to deposit refund logic. A 72-hour cancellation window means automatic refund inside 72 hours, automatic forfeit outside it, without operator intervention. This matters more than it sounds: most restaurants who try to enforce policies manually end up not enforcing them, because the conflict with the guest is uncomfortable and the policy gets quietly abandoned within six months.
No-show flagging is automatic. Guests who no-show twice get an internal flag against their record, visible to the operator the next time they try to book. This isn't a public "shame list." It's an operational signal that lets the host decide whether to require a higher deposit, or in extreme cases decline the booking. We have not seen this misused at any of the venues we work with; it's a quiet, internal tool.
For restaurants thinking about reservation platform changes specifically, the regional reservation system comparison covers how Revasi sits relative to SevenRooms, Chope, TableCheck, OpenTable and Resy, and where each platform's no-show handling differs.
A Closing Thought
The fastest restaurants we have ever seen reduce a 12% no-show rate to 4% did three things in sequence: they installed SMS reminders, they introduced a selective deposit policy on weekends and tasting menus, and they tightened their cancellation window from 24 to 72 hours. The total operational work was around two weeks. The annualised revenue impact for a 50-seat restaurant doing two services a night was in the tens of thousands of US dollars.
The reason this problem still exists at most restaurants is not that the solutions are unknown. It is that the operational lift to implement them feels larger than it is, and the conversation with guests about deposits feels harder than it turns out to be. Most guests, when the policy is explained reasonably, accept it without complaint. The ones who don't accept it are usually not the guests you want anyway.
If you would like to walk through your specific no-show data, or just talk through whether deposits make sense for your venue, most of our team has worked through this conversation with restaurants in Bali, Singapore, Bangkok and Jakarta in the last twelve months. We are happy to help you think it through, even if Revasi isn't the right platform for your venue.
Talk to Revasi about no-show reduction →
Frequently Asked Questions
What is a normal no-show rate for a fine dining restaurant in Asia?
Around 8% globally based on ResDiary's 2024 UK and Ireland industry report, and roughly 10% for Singapore based on Chope's operator data. Fine dining specifically runs higher than the cross-segment average because reservations are typically further ahead and parties are smaller, so each no-show is more visible on the night's revenue.
Do deposits actually reduce no-shows?
Yes, materially. OpenTable's 2024 data shows requiring a deposit reduces no-shows by an average of 57% and makes guests 72% less likely to cancel last-minute. A credit-card hold without a charge still reduces no-shows by 16%. The friction is real but the impact is consistent across markets and segments.
What is the right deposit amount for a fine dining restaurant?
Most operators in Asia land at 30–50% of the menu price as a deposit, fully redeemable against the bill. Below 20% and the friction-to-impact ratio gets worse: the deposit hurts conversion without meaningfully reducing no-shows. Above 60% and conversion drops sharply for guests who haven't dined with you before. 50% on tasting menus and group bookings is the most common setting.
Will guests accept a deposit policy?
For special occasions and group bookings, yes. 82% of OpenTable-surveyed diners said they're more likely to put down a deposit for a special occasion or large group. For walk-in-friendly Tuesday dinners, deposits will reduce conversion. The right answer is usually selective: deposits on weekend prime-time, tasting menus, large parties and special occasions; no deposit on weekday off-peak.
How effective are SMS reminders compared to email?
SMS materially outperforms email for reservation reminders. resOS reports a 27% average reduction in no-shows with SMS confirmations, and 36% of guests who missed a booking said they would have shown up if they'd received a reminder. One Chope client in Singapore reported a 67% reduction in no-shows after activating automated SMS reminders alongside their existing email flow.
How long should the cancellation window be?
Singapore's fine dining sector moved industry-wide from 24-hour to 72-hour cancellation windows during 2024 as a no-show countermeasure. 48–72 hours is now the working standard for tasting menu restaurants in Bali, Singapore and Bangkok. Anything tighter than 24 hours is hard to defend operationally because the kitchen has already started prep.

Lucas
Co-founder, Revasi
Passionate about the intersection of hospitality and technology. Helping restaurants discover digital tools to transform their dining room experiences and turn first-time guests into regulars.


