Updating a QR menu in the middle of service

At eight o'clock on a busy Friday, the kitchen sells its last portion of lamb. On a paper menu, that is a problem servers solve one table at a time: "I'm sorry, the lamb has just finished." On a QR menu that guests order from directly, it is a different problem. Unless someone takes the lamb off the digital menu straight away, the next guest to scan can order it, and the kitchen receives an order it cannot cook.

Updating a QR menu in the middle of service is one of the digital menu's great strengths, and one of its great risks. Done quickly and by the right people, it keeps the menu true minute by minute in a way paper never could. Done slowly, or by nobody in particular, it sends guests dishes that do not exist. This guide covers how to 86 an item at once, how to add daily specials, how to change prices safely, and who in the team should be allowed to change the digital menu. Every figure in it is an example.

On a paper menu, the menu itself never changes during service. Servers carry the changes in their heads: what has run out, what the specials are, what has a substitute tonight. Guests ask, and the server tells them.

On a QR menu, especially one guests order from, the menu is the conversation. Guests read it, choose from it and send orders without a server in between. Anything the menu says is taken as true. A dish shown as available is a dish the guest expects to receive.

That makes the digital menu's accuracy during service a matter of guest experience and kitchen workload. An order for a dish that has run out means a declined order, an apology, a disappointed guest and a server who has to go to the table anyway.

To 86 an item is kitchen language for taking it off because it has run out, and Wikipedia's article on 86 as a term traces where the expression came from. On a QR menu, the 86 must happen in the digital menu, at the moment the kitchen knows, not when someone remembers to do it later.

The fastest approach is to 86 an item from the same screen the team already uses during service: the point of sale. When the kitchen calls that the lamb is finished, the person at the point of sale marks it as sold out, and the dish disappears from ordering on every guest menu, the point of sale and any boards at once.

Our guide to 86 an item so nobody orders it at five past covers the kitchen side of the routine: how to see the run-out coming, and how to tell the floor.

The best 86 is the one made a few minutes before the last portion goes, not after. A kitchen that knows it has four portions of lamb left can warn the floor, slow down recommendations and 86 the dish when the last one is ordered, rather than discovering it is gone when an order arrives.

Build a simple habit: the kitchen keeps a count of limited dishes during service, especially specials and dishes made in batches, and calls a warning when the count gets low. The person who updates the menu then knows to be ready.

Some venues show a limited dish as "only a few left" on the menu when portions run low. That can help guests decide quickly, but it must be accurate; a dish that stays "almost gone" all evening loses credibility.

An 86 is not always permanent. A delivery arrives late, a fresh batch is ready, the kitchen finds a few more portions. The dish should go back on the menu as quickly as it came off, from the same screen.

Make putting a dish back on as easy as taking it off, and make sure it is someone's job. A dish 86'd at eight and never put back on is missing from tomorrow's lunch menu too, until someone notices.

At the end of each service, check what is 86'd, and decide what should come back on for the next service and what should stay off. A short line in the closing routine avoids the next morning's surprise.

Daily specials are one of the reasons guests return, and on a QR menu they can be presented beautifully: a section at the top, a photograph, a short description and a price. But specials change often, sometimes daily, and every change needs to happen before guests start ordering.

Add specials before service, not during it. The person responsible should add each special with its description, price, options and allergen information, check it on a phone as guests will see it, and tell the team. A special added in a rush during service is the one most likely to have a wrong price or missing allergens.

When a special runs out, 86 it like any other dish. When the special changes the next day, remove the old one rather than leaving it hidden, so the menu does not slowly fill with yesterday's dishes.

Every new dish, special or substitution needs accurate allergen information before it appears on the digital menu. Guests filter by allergens and rely on what the menu tells them, so a special with missing allergen information is a real risk.

Make allergens part of adding a dish, not an afterthought. The person adding a special should record its allergens from the recipe as it is made today, and check them with the kitchen. If a substitute ingredient changes a dish's allergens during service, because the usual product ran out, the menu must change too, or the dish must come off until it can.

When in doubt, take the dish off. A dish missing from the menu for an hour is far less serious than a dish with wrong allergen information.

Sometimes a dish does not run out, but part of it does. The kitchen runs out of the usual side, a garnish or a sauce, and substitutes something else. With a paper menu, the server mentions it at the table. On a QR menu, the guest reads the description, orders the dish and expects exactly what it says.

A substitution that changes what the guest receives should change the menu too. If the change is small, such as a different salad leaf, a word from the server may be enough. If it changes the dish's character, its price or its allergens, update the description and the allergen information before the next order, or 86 the dish until the change is made.

Agree in advance which substitutions the kitchen can make without a menu change, so nobody has to decide in a hurry with a full board.

Changing prices in the middle of service is usually a mistake. Guests who have looked at the menu, or ordered once, expect the price to stay the same through their meal, and a price that changes between their first and second round looks like a trick.

Change prices before service or after it, not during. Plan price changes for a quiet moment, such as the start of a day or the start of a new menu, and make sure every version of the menu changes together.

The exception is a genuine error: a price entered wrongly that guests are being charged for. Fix it as soon as it is noticed, and make sure the guests already charged the wrong price are treated fairly.

Deciding who can update the menu during service matters as much as how. If anyone can change anything, mistakes happen: a server changes a price by accident, a dish is removed by the wrong person, a special appears with a typing error. If only one manager can change anything, updates wait until that manager is free.

Separate the kinds of change. Most venues let anyone on duty at the point of sale 86 a dish and put it back on, because those changes must happen at once and are easy to undo. Adding dishes, changing descriptions and changing prices are usually kept to managers or the head chef, because those changes need checking.

Use the permissions in your systems to enforce this, and make sure the team knows who can do what. A server who knows they can 86 a dish, but must ask a manager to change a price, acts quickly where speed matters and carefully where accuracy does.

A simple routine keeps the digital menu true through a service:

Write it down, train the team on it and keep it short. A routine that fits on a card at the pass gets followed.

A digital menu rarely lives alone. The same dishes may appear on the point of sale, on menu boards in the room, on the venue's website and on a printed menu. A dish 86'd on the QR menu but still showing on the board above the bar sends guests to ask for it in person.

The safest arrangement is one source for the menu, from which every version reads, so a change made once appears everywhere. Our guide to updating the menu in one place, not five covers why that matters and how to set it up.

Printed menus cannot change during service, so servers still need to know what has run out. A short note at the pass, or a word in the pre-service briefing, keeps the team in step with the digital menu.

When a dish is 86'd, guests should see it clearly. Many digital menus show a sold-out dish as unavailable, greyed out or marked "sold out", rather than removing it entirely. That helps guests who saw it earlier understand what happened, and it tells guests the dish exists for another visit.

Either approach can work, as long as the dish cannot be ordered. What must never happen is a dish that looks available, can be added to the basket and is then declined after the guest has sent the order.

If a guest has already ordered a dish that has just run out, tell them quickly, in person if possible, and offer an alternative. The digital menu prevents most of these moments; a server handles the few that slip through.

Mid-service updates are about keeping tonight's menu true. Updating the menu for the next service is a different job: changes to dishes, descriptions, photographs and prices that should be planned, checked and made when the venue is quiet.

Keep the two apart. During service, only 86s and essential corrections. Before or after service, the planned changes, made carefully, checked on a phone and briefed to the team. Our guide to changing the menu: a calendar, not a crisis covers the larger, seasonal changes.

A team that knows which changes belong in which moment makes fewer mistakes and keeps the menu accurate without disrupting service.

Mistakes happen: the wrong dish 86'd, a special added with the wrong price, an allergen missed. When they do, fix them quickly and look after any guest affected. A guest charged the wrong price should be refunded the difference without fuss; a guest who received a dish with an allergen they told you about needs immediate attention and a proper record.

Afterwards, look at why it happened. Was the person rushed? Did they have the right information? Was the change made by someone who should not have been making it? Adjust the routine or the permissions so the same mistake is less likely.

Keep a record of changes where your system allows it, so you can see who changed what and when. That is not about blame; it is about understanding.

Running out is not the only reason to change the menu in the middle of service. When the kitchen falls badly behind, some dishes make it worse: a slow dish that ties up the grill, or a dish that needs a station that is already overloaded.

Some venues take one or two of the slowest dishes off the digital menu for half an hour when the kitchen is stretched, and put them back on when it recovers. Guests ordering from their phones then choose from dishes the kitchen can deliver in reasonable time, rather than waiting forty minutes for one it cannot.

Use this sparingly, and make it the head chef's call. A menu that changes every few minutes confuses guests and the team, but one or two planned moves on the hardest nights can protect the whole room.

An invented bistro takes orders by QR code. On busy nights, dishes run out and stay on the digital menu for twenty minutes or more, because only the manager can change the menu and the manager is usually on the floor. Guests order dishes that have gone, orders are declined and servers spend the evening apologising.

The bistro changes its routine. Anyone at the point of sale can now 86 a dish and put it back on, while price and description changes stay with the manager and the head chef. The kitchen calls a warning when a limited dish reaches three portions. Specials are added before service, with their allergens checked by the head chef, and removed the next morning.

Declined orders for sold-out dishes almost stop, servers spend less time apologising, and guests begin to trust that what they see on the menu is what they can have.

In servearound, a dish can be 86'd from the point of sale during service, with a confirmation, and put back on from the same screen; once 86'd, it shows as sold out on every guest menu at once, and digital menu boards pick up menu changes within seconds. Staff sign in on the point of sale with their own name and PIN, the team is notified when a dish is 86'd or put back on, and team members' roles and permissions decide who can change the menu itself.

Dishes, specials and prices are edited once and appear on the menu guests open from a table's QR code, the venue's menu page and print designs, which say when a dish has been added, removed, renamed or repriced since they were printed. Allergen and dietary tags sit on each dish, and a menu or a dish can also be scheduled, so a lunch special appears only at lunch. See the menus module and Order Fulfillment.

The moment the kitchen knows it has gone, ideally before the last portion is ordered, so no guest can order it.

To take a dish off because it has run out. On a QR menu, the 86 must happen in the digital menu at once, not just in the kitchen.

Usually anyone on duty at the point of sale, because it must happen quickly and is easy to undo.

Managers or the head chef, because those changes need checking, and usually before or after service rather than during it.

Before service, with prices, options and allergen information checked, and removed when they finish.

Either works, as long as it cannot be ordered. Showing it as sold out helps guests who saw it earlier understand what happened.

Usually not. Guests expect prices to stay the same through their meal. Fix genuine errors at once, and plan other changes for quiet times.

Feed every version from one source where possible, and keep the team informed about anything the printed menu cannot show.

Tell them quickly, in person if possible, and offer an alternative.

Updating a QR menu in the middle of service keeps the menu true minute by minute, but only if it is quick and done by the right people. 86 an item from the point of sale the moment the kitchen says it is gone, warn the floor before limited dishes run out, and put dishes back on as soon as they return. Add daily specials before service, with allergens checked, and remove them when they finish.

Keep mid-service changes to 86s and genuine corrections, and plan price and description changes for quiet times. Let anyone on duty 86 a dish while keeping other changes with managers and the head chef, feed every version of the menu from one source, and follow a short routine before, during and after every service.