4 September 2026 · 4 min read
Waitlist vs reservations for small restaurants: you probably need both, in different proportions
Why small restaurants shouldn't choose between a booking system and a walk-in waitlist — and how to decide the right mix for your covers.
This gets framed as an either/or question more than it deserves to be. Most small restaurants that do well with both aren't choosing between reservations and a waitlist — they're deciding what share of tonight's covers should come from each, which is a very different question with a very different answer depending on your size, your neighbourhood, and your night of the week.
What each one is actually for
| Reservations | Walk-in waitlist | |
|---|---|---|
| Best for | Guests planning ahead — a birthday, a date, an out-of-town visit | Guests deciding in the moment — passing by, a group that didn't plan, last-minute plans |
| Table held | In advance, at a fixed time | As soon as one's free, in arrival order |
| Cancellation risk | Real — no-show or late cancellation on a table you turned others away for | Lower stakes — a no-show just means the next walk-in gets called instead |
| Typical tool | OpenTable, Resy, SevenRooms, or a phone book | A QR-code queue app, or (still, in a lot of places) a clipboard |
Why "just take reservations for everything" doesn't work for most small places
- You lose walk-in revenue. A fully-booked reservation system turns away people standing at your door right now — often on your busiest, most profitable nights.
- Small kitchens can't always predict pace weeks out. A restaurant with 12 tables and one seating per slot has much less room to absorb a table running long than a 40-cover venue with a deeper bench.
- Not every neighbourhood books ahead. High-street and passing-trade locations get a large share of covers from people who decided to eat there in the last twenty minutes — reservations don't capture that at all.
Why "just do walk-ins" leaves money on the table too
- You lose planned, high-value bookings — birthdays, anniversaries, business dinners — to competitors who let people book ahead with confidence.
- Your busiest nights become unpredictable — with no reservations at all, a slow Tuesday and a heaving Saturday get no advance warning, which makes staffing and prep guesswork.
- Some guests simply won't risk a walk-in wait for a special occasion and will pick somewhere they can guarantee a table instead.
A practical split
A common pattern for small restaurants: reserve a portion of tables in advance (enough to protect planned, high-value bookings and give the kitchen a predictable floor) and leave the rest — often the majority on a passing-trade high street, or a smaller share in a purely destination venue — for walk-ins on the day. The exact ratio depends on your location far more than any general rule; a destination restaurant that people specifically travel to skews toward reservations, a bar-and-small-plates spot on a busy street skews toward walk-ins.
Running both without it being two systems to manage
The two don't need to compete for the host's attention if they're kept visually and operationally separate: the reservation book (whatever software or paper you already use) tells the host which tables are spoken for at which time, and a lighter walk-in queue tool handles everyone else, filling gaps as they open up. A host working a Friday night needs to glance at both without either one hiding the other.
- 01Block out reserved tables and times in your existing booking system as normal.
- 02Put a QR code at the door for walk-ins — a completely separate flow, no overlap with the booking calendar.
- 03As tables free up outside of a reservation slot, the host works from the walk-in board and calls the next party.
- 04When a reservation's due, that table is simply not offered to the walk-in queue for that window.
Deciding for your own restaurant
If you're mostly booked out days in advance already, a light walk-in queue for no-show tables and last-minute gaps is probably enough. If your door sees steady passing traffic and your reservation book has gaps most nights, weighting toward walk-ins — with reservations reserved for genuinely planned occasions — usually serves guests and the kitchen better than trying to force everyone through a booking calendar.
Where Queued fits
Queued isn't a reservation system — it's built specifically for the walk-in side, so it sits alongside whatever booking tool you already use rather than replacing it. QR code at the door, branded guest page, live board for the host, and an email the moment a table's free.
Add a walk-in queue to what you already run
Set up a queue for the tables you don't take reservations for.
Get started free- Can I use a waitlist app alongside my existing booking software?
- Yes — most restaurants keep their reservation system for advance bookings and run a separate, lighter waitlist tool just for walk-ins.
- What share of tables should I reserve for walk-ins?
- It depends heavily on your location and concept. Tracking your actual covers split for a couple of weeks is a more reliable guide than any general rule of thumb.
- Do walk-in queues cause the same no-show problems as reservations?
- The stakes are lower — a walk-in no-show just means the next party in line gets called, rather than an empty table you turned other guests away for.