QR ordering: the table orders, the kitchen cooks

QR ordering lets guests order from their table using their own phones. They scan a code on the table, the menu opens already knowing where they are sitting, and they choose dishes, add options and send the order straight to the kitchen. No waiting to catch a server's eye, no order pad, no order rewritten at a till. The table orders; the kitchen cooks.

For some venues, it has transformed service. Bars, cafés, beer gardens and busy casual restaurants use it to take orders faster, especially for second rounds, and to free their teams from the routine of writing down drinks. For others, it has been a poor fit, felt as a cost-cutting measure that removed the warmth from the meal. The difference is rarely the technology. It is whether the venue decided what the server's job becomes when the table can order for itself.

This guide explains how QR ordering works, how it changes the server's role, who still takes the order, what it does to order accuracy and average spend, and the two kinds of table where scan to order quietly fails. It ends with how to introduce it, what to measure and the mistakes that make guests wish for a pen and pad.

QR ordering is a form of ordering at the table where guests use a QR code menu on their own phone to place orders. The code is usually printed on a card or sticker on each table, so the menu knows which table the guest is at. Guests browse, choose dishes and drinks, select options such as cooking preferences or sizes, add notes, and send the order.

The order goes to the kitchen or bar as a ticket, often at the station that prepares each item, and it joins the table's check, so the bill reflects everything the table ordered. Guests can usually order again later in the meal, for a second round or dessert, without waiting for a server.

The code itself is an ordinary QR code, a square barcode that any modern phone camera can read, which is why guests need nothing beyond the phone in their pocket. It is different from a QR code menu that only shows the menu. Many venues use the same code for both: a menu to read, and, where the venue chooses, a way to order. Our pillar guide to the QR code menu five years on covers what has worked for the menu itself.

A typical scan to order flow has a few steps. The guest scans the table's code with their phone camera, and the menu opens in the browser, with no app to download. They browse the sections, tap a dish to see its description, photograph and allergens, choose any options, and add it to their order. When they are ready, they review the order and send it.

Behind the scenes, the order reaches the kitchen and bar as tickets, with the table number, every option and any notes. The guest can usually see that the order has been received and how it is progressing. The server can see it too, on the table's check.

Each step should be quick and obvious. A guest who has to hunt for the order button, guess what an option means or wonder whether the order went through will stop using it and wave for a server instead.

The most important change is not technical. When tables can order for themselves, servers spend less time writing down orders and walking them to the till, and more time on everything else. That can be very good for guests, or very bad, depending on what the venue does with the time.

In venues where it works well, servers use the time to welcome every table, explain how the menu works, recommend dishes, check on tables after food arrives, clear promptly and spot problems early. Guests get faster ordering and more attention. In venues where it works badly, the time is simply removed: fewer servers, longer sections and tables left alone with their phones.

Decide in advance what the server's job will be. Write it down, train it and check it. QR ordering removes a task; it should not remove hospitality.

Even with QR ordering, servers still take many orders, and should. Some guests prefer to order with a person. Some have questions the menu cannot answer, or want a recommendation. Some do not have their phones, or their phones are out of battery. Some tables are complicated, such as a large group with dietary needs, where a server can manage the order better.

The best venues offer both. Guests can order from their phones if they want, or ask a server, and both orders end up on the same check. A middle option also works well: guests build a selection on their phone and show it to the server, who confirms it and sends it. That keeps the conversation while removing the writing.

Make it clear that guests can always ask. A line on the table card, such as "Order here, or ask us, we are happy to help", sets the tone.

One clear benefit of QR ordering is order accuracy. The order reaches the kitchen exactly as the guest chose it, with every option and note, without being misheard, misremembered or rewritten. Mistakes in transcription, such as a missed modifier or the wrong table number, largely disappear.

New kinds of mistake can appear instead. Guests may choose the wrong option, misunderstand a dish or order the same dish twice from two phones at the same table. Design the menu to prevent these: clear option names, required choices where needed, a review screen before sending, and a visible list of what the table has already ordered.

When a QR order cannot be made, for example because a dish has just run out, the team needs a way to decline it with a reason and let the guest choose again. A guest who is told politely and quickly is far happier than one who waits and then hears the bad news from a server.

QR ordering changes the rhythm of orders reaching the kitchen. Without a server batching orders, tables send them whenever they are ready, which can spread orders more evenly through the evening, or bunch them when many tables sit down at once. Watch how the kitchen copes, especially in the first weeks.

Courses need thought. A guest who orders starters and mains together from their phone may expect them to arrive in sequence, while the kitchen sees them all at once. Decide how courses will be handled: whether guests order course by course, whether mains are held until the server fires them, or whether the venue serves dishes as they are ready and says so on the menu.

Each item should reach the station that makes it. Drinks to the bar, starters to the cold section, mains to the grill. When tickets arrive at the right station with every detail, nobody needs to shout across the kitchen to ask what a table meant.

QR ordering can raise average spend, but it is not automatic. It tends to help where ordering again is the bottleneck: second rounds of drinks, desserts and coffees that guests would have ordered if a server had passed at the right moment. When guests can order the moment they want something, more of those orders happen.

A well-designed menu helps too. Photographs, clear options for extras and sides, and suggestions such as "pairs well with" can encourage guests to add items they might not have asked a server about. Some guests also feel freer to order more when nobody is watching.

It can lower spend as well. Servers who recommend a better wine, suggest a starter to share or describe the specials sell things a menu cannot. If QR ordering removes those conversations entirely, spend may fall. Measure average check before and after, by service and day, and keep the servers' recommendations in the mix.

QR ordering quietly fails at two kinds of table. The first is the occasion table: a birthday, an anniversary, a business dinner or a large celebration. These guests want to be looked after. They want someone to take their order, explain the dishes, suggest the wine and make the evening feel special. Handing them a QR code tells them they are on their own.

The second is the table that needs help: guests who are unfamiliar with the cuisine, unsure about allergens, without smartphones, or simply uncomfortable ordering on a screen. For them, the QR menu is a barrier. They need a person to explain, reassure and take the order.

The answer is not to abandon QR ordering, but to recognise these tables and serve them differently. A host who knows a table is celebrating can tell the server. A server who sees a table hesitating over the code can step in. The best QR ordering venues use technology for the tables that want speed, and people for the tables that want care.

Ordering from the table must not weaken allergy safety. Guests with allergies should see each dish's allergens before they order, be able to filter the menu to avoid the allergens they need to, and confirm that they have read the allergen information before sending the order. The order should carry any allergy clearly on the kitchen ticket.

Keep the human check. Encourage guests with allergies to speak to a member of staff, and make sure servers know to confirm with the kitchen. A QR menu supports the conversation; it does not replace it. Our guide to building an allergen matrix that stays correct covers the record behind the menu.

The allergen information on the QR menu must be correct for every dish, every day. It should come from the same record the kitchen uses, and change when a recipe changes.

QR ordering often comes with a way for guests to ask for help from the table: call a server, ask for water, request the bill. These requests reach the team at once, rather than waiting for someone to notice a raised hand, and the nearest free member of staff can respond.

Handle them promptly. A request that goes unanswered is worse than no button at all, because the guest knows it was sent. Make sure requests arrive somewhere the team will see them, such as a live queue on a tablet or screen, and that each one is marked as it is dealt with.

Requests for the bill are especially valuable on busy nights, because they free the table sooner. Our guide to pay at table covers the end of the meal.

A good ordering flow is fast, clear and forgiving. The menu should load quickly, show sections at the top, and let guests add a dish in one or two taps. Options should be named in plain words, with required choices marked and sensible defaults. The basket should show the running total and let guests change or remove items easily.

Before sending, show a clear summary of the order, the table number and the total. After sending, confirm that the order has been received and show its progress. If something goes wrong, such as a dish being unavailable, tell the guest clearly and let them choose again.

Test the flow on several phones, in the venue, on its own connection. Ask people who have never used it to order a drink and a dish, and watch where they hesitate.

QR ordering often works best where table service is hardest. On a large terrace, in a garden or in a busy bar, servers cover long distances and guests can wait a long time to be noticed. Letting guests order a round from their table, and having runners bring it out, removes the longest waits in the venue.

Plan the delivery side carefully. Orders from distant tables need someone to run them, and drinks orders from the terrace need to reach the bar quickly. Make sure the table numbers on the terrace are clear, so runners can find each table, and that the network reaches every corner.

At the bar itself, QR ordering can take pressure off the counter on busy nights, letting guests at tables order without queuing. Keep the counter open for guests who prefer to order in person.

Guests need to know QR ordering exists and how to use it. Put a clear card on each table with the code, a short instruction and a reassurance that they can also order with a server. Ask servers to explain it when they welcome each table, especially in the first weeks.

Introduce it gradually. Many venues start with drinks only, or with second rounds, where the benefit is clearest and the risk lowest. Once guests and staff are comfortable, extend it to food.

Listen to feedback. Guests will tell you, directly or by their behaviour, what works and what does not. A table that scans the code and then waves for a server is telling you something about the menu or the flow.

QR ordering is often presented as a way to reduce staff. In practice, venues that cut too deeply find that service suffers: tables wait for food to be delivered, plates are not cleared, requests go unanswered and the occasion tables feel neglected. Ordering is only one part of service.

Plan staffing around the work that remains: welcoming, running food, clearing, checking on tables, handling requests and looking after the tables that need help. You may be able to cover more tables per server, or redeploy time to runners and the host stand, but measure the effect on guests before making cuts permanent.

Involve the team in the change. Servers who see QR ordering as a tool that removes the dullest part of their job tend to support it; servers who see it as a threat tend not to.

Measure whether QR ordering is working. Useful measures include the share of orders placed from the table, the time from seating to first order, the share of tables ordering a second round or dessert, average check, the number of declined or corrected orders, and the time from request to response for service requests.

Compare these with the period before QR ordering, and compare services: QR ordering may work well at lunch and less well at dinner, or the other way round. Listen to guest feedback and online reviews for mentions of the ordering experience.

Watch the kitchen's ticket times too. If they rise because orders arrive in bursts, adjust how courses are fired or how many tables are seated at once.

Here is an illustrative case of a casual venue introducing QR ordering. The details are examples.

In servearound, each table's QR code opens the menu already knowing where the guest is sitting and who is serving them. A menu can let guests order from the table, build a selection to show their server, or browse only, venue by venue. Options can require a least and a most to choose, any dish can carry a note, guests confirm they have read the allergen information before ordering, and they can follow the order's progress with an estimate.

With Order Fulfillment, an order from the table arrives as a ticket at the station that cooks it and joins the check the server is working on. An order can be declined with its reason, and the guest's dishes go back to their cart. Guests can call a server at any time and request the bill once they have ordered, and both requests land in a live queue for the team. See the menus module and fulfillment.

Sometimes a little fewer, often the same number doing different work. Measure the effect on guests before changing staffing.

Many will, and some will not. Always offer the option of ordering with a server.

Decide how courses will be handled, and say so. Many venues hold mains until the server fires them.

It often helps second rounds and desserts. Measure it in your own venue, and keep servers' recommendations in the mix.

Decline the order with a clear reason and let the guest choose again, quickly.

Usually not for ordering, though a QR menu can be useful for information such as allergens and wine notes.

QR ordering lets the table order and the kitchen cook, with orders reaching the right station exactly as guests chose them. It improves order accuracy and speeds up second rounds, but it changes the server's job rather than removing it. Decide what servers will do with the time, and keep the option of ordering with a person.

Design a fast, clear scan to order flow, handle courses deliberately, keep allergen safety and service requests sharp, and recognise the two tables where it fails: the occasion table and the table that needs help. Introduce it gradually, measure QR ordering average spend and guest feedback, and staff for the service that remains.