Reducing restaurant wait times

"We have a wait problem" is rarely one problem. Guests wait in three different places: in line to order, for their food after they have ordered, and for a table before they can sit. Each wait has its own causes and its own fixes, and the fixes interact. A faster line sends orders to the kitchen faster, so a restaurant that fixes the line without checking the kitchen often just moves the wait from the queue to the pickup counter.

This guide is about choosing the right lever. The detail of each lever lives in the deeper guides linked along the way.

Which wait do you have? Measure it first

Time each of the three waits separately, at your busiest hour, on more than one day, before you change anything. The wait guests complain about is not always the longest one, and a fix aimed at the wrong wait costs money and changes nothing.

• ✓The line to order: from joining the queue to finishing paying. A phone timer and a note of when the line reaches the door is enough.
• ✓The wait for food: from paying to food in hand, or from ordering to the plate landing at a table. A kitchen screen times every ticket; paper tickets leave you guessing.
• ✓The wait for a table: from giving a name to sitting down, written next to the time the host quoted.

Then watch where guests are standing when they get frustrated. Frustration in the queue, at the pickup counter and at the host stand point to three different fixes. Look at the slowest waits at the peak, not the average across the day; the average hides the moments guests remember.

Waiting in line to order: more lanes, fewer orders at the till

The line moves at the speed of the slowest order at the register, so the levers are more places to order, fewer orders that need the register at all, and a menu that is faster to decide from. Pick by what you have: counter space, staff, or guests with phones.

A second register for the peak

Opening a second register at the rush is the oldest fix and still works if you have the counter space and the person. It doubles the places orders are taken without changing how guests order. Its limit is labour: the second cashier is needed only for the peak, which is exactly when nobody is free.

A self-order kiosk as an extra lane

A kiosk is an ordering lane that does not need a person standing at it. Guests who know what they want go to the kiosk; guests with questions go to the cashier, and the two lines move in parallel. The indecisive guest also does less damage at a kiosk, because browsing there does not hold up the people behind them. How many to install is a question about your peak, which the guide on how many self-order kiosks you need works through.

Two things decide whether a kiosk actually shortens the wait: payment at the kiosk has to be quick, and the kitchen has to absorb orders arriving faster than before. Check both before the first busy Saturday.

QR and online ordering to take orders off the line

Every order placed from a phone is one fewer person in the queue. Online ordering for pickup moves planned, regular orders out of the line entirely, and QR ordering lets seated guests order without walking back to the counter. The catch is that phone orders reach the kitchen with no visible queue in front of them, so you need an honest prep time shown to guests and a way to pause online orders when the kitchen is buried.

A simpler menu for the rush

Decision time is part of the line. A long menu with many build-your-own steps produces slow orders and questions at the till. For the peak window, lead with items you can make quickly, put combos where guests see them first, and hide low-sellers that need explaining. This is a menu decision rather than a staffing one, and it often shortens the line more than anything else here.

Waiting for food: fix how orders reach the kitchen

Food waits are usually caused by how orders arrive and are routed, not by cooks moving slowly. The levers are routing each item to the station that makes it, keeping ticket age visible, prepping for the peak you know is coming, and handing food over the moment it is ready.

• ✓Route by station, so each cook sees only what they make instead of reading a whole ticket to find their part.
• ✓Make ticket age visible to the kitchen and the pass. Attention follows what is on the screen.
• ✓Prep for the rush you can predict. Batch the components that sell at the peak before it starts.
• ✓Treat the handoff as a station. Food that is ready but not handed over is still a wait for the guest, so call names or numbers clearly and keep the pickup area clear.
• ✓Quote a realistic ready time at the counter and online. A guest told the truth waits more patiently than one told something hopeful.

Where the minutes hide inside a ticket, from bursts of arriving orders to sequencing across stations, is covered in the guide to reducing kitchen ticket times. For a counter cafe, the guide to the coffee shop morning rush covers the drink build and the handoff in detail.

Waiting for a table: quote honestly, turn tables

You cannot make a full room bigger, so the two levers are a quote guests can trust and less dead time between one party leaving and the next sitting down. Neither involves rushing anyone through a meal.

Quote honestly

A guest told a short wait who then waits longer is angrier than a guest told a longer wait who sits early. Base quotes on what the tables are actually doing, keep true arrival order, and tell a party early when the quote is slipping. The guide to restaurant waitlist management covers quoting and the waiting experience.

Recover dead time around the meal

Most recoverable time is outside the meal itself: a slow first greeting, waiting for the bill, and a paid table that nobody has reset. The guide to improving table turn times breaks a turn into its parts and shows where the minutes go.

What not to do

Most failed attempts to cut waits make one of the same few mistakes: pushing people harder, adding capacity at one stage only, or making promises the room cannot keep.

• ✓Do not tell the kitchen to go faster. It is the least effective intervention available and the one that produces mistakes and remakes.
• ✓Do not add an ordering lane without checking the kitchen can take the extra orders. You will move the wait, not remove it.
• ✓Do not under-quote table waits to stop guests leaving. They leave later, and angrier.
• ✓Do not cut the menu at random. Cut what slows the order and the line, and keep what sells.
• ✓Do not judge success on the daily average. Judge it on the worst waits at your peak.
• ✓Do not shorten waits by hurrying seated guests. Take the time from the dead spots around the meal instead.

Where Opero helps and where it does not

Opero helps most with the line and with getting orders to the right station quickly. It cannot add kitchen capacity or seats, and the table-wait tools are on the Full-Service plan only.

• ✓A self-order kiosk is included on every plan, with no per-kiosk fee and no limit on kiosks per location. It runs in English and Spanish, and it is pay-first: an order reaches the kitchen only after the card clears, so an abandoned order never fires a ticket.
• ✓The kiosk takes cards only, and each kiosk needs its own card reader, bought from Opero and paired to that kiosk on the Devices page. Two kiosks set to one reader would send guests to the same terminal, and Opero warns you about it. Guests who want to pay cash still go to the register.
• ✓Online pickup ordering and QR ordering are included on every plan and read the same menu as the register. Guests pick ASAP or a pickup time later today, each location sets its own prep time, and you can pause online orders for 15, 30 or 60 minutes or until you turn them back on.
• ✓QR table orders are paid from the guest's phone at order time and reach the kitchen tagged with the table. They do not join a server's running check.
• ✓You can hide an item from the kiosk while keeping it on the register, which is one way to run a shorter menu at the kiosk.
• ✓Every channel lands on one kitchen display per location. Each item routes to its station, ticket timers change colour as an order ages, a chime repeats until someone acknowledges a new order, and a batch view groups the same item across tickets for prep.
• ✓On Opero Full-Service ($249 per location per month), the waitlist records each party's quoted wait, shows how long they have waited and flags anyone past their quote, and the live floor shows how long each table has been seated. The $149 Opero plan does not include them.

The honest limits: Opero does not text guests when their order or table is ready, so the host or the counter still calls them. Online ordering is pickup only and same-day. Menus do not switch by time of day, so a rush menu is something you set by hiding or 86ing items by hand. Opero has no offline mode, so every screen needs a working internet connection, and it runs on Android tablets only.