86 an item so nobody orders it at five past

To 86 an item is kitchen shorthand for taking a dish off the menu because it has run out. The sea bream is gone at eight o'clock, so the kitchen calls "86 the bream", and from that moment nobody should be able to order it. In practice, that moment often stretches. The kitchen knows at eight, the server on section two hears at ten past, the QR menu still shows it at half past, and a guest orders it at five past eight from a table where nobody has been told.

Every order taken for a dish that no longer exists causes the same small crisis. The ticket reaches the kitchen, the kitchen sends it back, the server returns to the table with bad news, and the guest has to choose again, often after their companions have been served. One such moment is an annoyance; several on a busy night undo the work of a good service.

This guide explains how to 86 an item so that it is off every screen, menu and channel at once. It covers how to see a dish running out before it does, who may 86 a dish, how to tell the floor, updating a QR menu and other channels, what guests should see instead, bringing a dish back, and how to learn from the 86s so they happen less often.

The phrase "86" has been used in American restaurants for decades to mean that an item is unavailable, and its origins are disputed; the general entry on 86 as a term covers the competing explanations. In kitchens today it means one thing: this dish cannot be ordered until further notice.

Dishes are 86'd for several reasons. The kitchen has run out of a key ingredient, a batch has been used up, a delivery did not arrive, a dish has failed quality checks, or a piece of equipment it depends on has broken. Sometimes only part of a dish is affected, such as a sauce or a garnish, and the dish can be offered with a substitution instead.

Whatever the reason, the goal is the same: no guest should order the dish after the kitchen knows it is gone. That requires the information to travel from the kitchen to everyone and everything that takes orders, at once.

The gap between the kitchen knowing and the guest knowing is where the damage happens. A dish 86'd at eight o'clock but still orderable at five past creates a disappointed guest, a wasted trip for the server and a ticket the kitchen has to reject. If the guest ordered from their phone and their companions' orders have already gone to the kitchen, the table's meal is now out of step.

The longer the gap, the more orders are affected. A popular dish on a busy night may be ordered several times in ten minutes. Each of those orders needs a conversation, a new choice and a new ticket, and each one makes the table's wait longer.

Closing the gap is mainly a matter of kitchen communication: making sure that one action by one person takes the dish off everywhere at once.

The best 86 is the one the kitchen sees coming. A dish rarely runs out without warning: the last portions are visible in the fridge, the batch is nearly finished, the delivery is short. A kitchen that knows how many portions of each dish it has at the start of service, and watches them during it, can warn the floor before the last portion goes.

Count limited dishes before service. A special with twelve portions, a fish with ten, a slow-cooked dish made in a batch of twenty: note the numbers, and tell the floor at the pre-service briefing. During service, the pass can call out when a dish is getting low: "four bream left".

Warning the floor early lets servers steer guests gently towards other dishes as the last portions go, and avoids recommending a dish that may be gone by the time the order reaches the kitchen.

Decide in advance who has the authority to 86 an item, and make sure everyone knows. Usually it is the head chef or whoever is running the pass, because they know what is in the kitchen. In some venues, the floor manager can 86 a dish too, for example when a dish has been withdrawn after a complaint.

Too many people with the power to 86 dishes leads to mistakes: a dish taken off by someone who misunderstood, or left off after it should have come back. Too few means delays while someone finds the person with authority. One or two named roles per service is usually right.

Whoever does it should do it in one place, with one action, so the change reaches every screen and menu at once. Telling one server and hoping the message spreads is how dishes stay on the menu until five past.

In many venues, a dish lives in several places: the till, the handheld devices, the QR menu, the menu boards, the website, and perhaps delivery apps. To 86 an item properly, it has to come off all of them. When each is a separate system, that means several actions by several people, and something is always missed.

The fix is one source of truth for the menu, with every screen reading from it. Mark the dish sold out once, and it disappears or shows as sold out on every till, every handheld and every guest's phone at the same moment. Our guide to updating the menu in one place, not five covers why every copy of the menu should come from one source.

Where some channels cannot be connected, such as a delivery app managed separately, add them to a short checklist that the person doing the 86 works through immediately.

Updating a QR menu is the most urgent part, because guests ordering from their phones never speak to a server before the order reaches the kitchen. If the dish is still on the QR menu, guests will order it, and nobody will be there to tell them it has gone.

A live digital menu can mark a dish sold out the moment it is 86'd, so guests see it as unavailable or do not see it at all. A PDF menu cannot, which is one of many reasons to replace PDFs with live menus. Our guide to QR ordering covers ordering from the table.

Guests who already have the dish in their basket when it is 86'd need handling too. The best systems tell them when they try to order, and let them choose again before the order is sent, rather than after.

Even when every screen updates automatically, servers need to know. A server recommending the bream to a table, or describing tonight's specials from memory, will create the same disappointment as an out-of-date menu. Kitchen communication with the floor should be immediate and clear.

Many venues use a simple routine: the pass calls the 86 aloud, the floor manager confirms it with each section, and a board or screen at the service station lists what is off. Servers check it before recommending dishes. Some venues send a message to every server's device as well.

Tell servers what to offer instead. "The bream is gone, offer the hake, it is cooked the same way" gives servers something to say, rather than just bad news.

When a dish is 86'd, guests should see clearly that it is unavailable, rather than finding out after they have chosen it. On a digital menu, many venues show the dish as sold out, greyed out, rather than removing it entirely, so guests who came for it understand what has happened. Others remove it, to keep the menu clean.

Either way, offer an alternative where you can. A note such as "sold out tonight, try the hake" turns a disappointment into a suggestion. On printed menus, servers should mention 86'd dishes when they hand over the menu or take the order, before guests set their hearts on them.

For a guest who has already ordered the dish when it runs out, be quick and honest. Apologise, explain, suggest an alternative and, where appropriate, offer something to make up for the disappointment.

Sometimes only part of a dish runs out: the sauce, the garnish, a side. The dish can still be served, but not as described. These partial 86s are where order accuracy most often slips, because the change is easy to forget.

Decide what to do in each case. Either substitute something similar and tell the floor, so servers can tell guests, or 86 the whole dish if the substitution changes it too much. Never substitute silently, especially where allergens could change. A different sauce may contain an allergen the original did not.

Record substitutions on the ticket, so the cook and the pass know what is going on the plate, and so the server can tell the guest before the dish arrives.

On a busy night, a clear routine stops an 86 from becoming a scramble. Many kitchens use something like this:

It takes less than a minute, and it can be practised. A routine everyone knows is far quicker than an improvised one in the middle of a rush.

The bar has its own 86s: a wine that has sold its last bottle, a beer whose keg needs changing, a cocktail whose garnish has run out. They cause the same disappointment, and they are often handled less carefully, because bar stock is rarely counted during service.

Treat drinks the same way as food. Count limited wines and specials before service, mark them sold out everywhere when they go, and tell servers what to offer instead. A guest who chose a particular wine for a celebration deserves a good suggestion, not just an apology.

A dish that comes back, such as when a delivery arrives or a new batch is ready, needs the same care in reverse. It should come back on every screen and menu at once, and the floor should be told. A dish left off by mistake for the rest of the night is lost revenue, and a guest who asked for it may have been turned away for nothing.

Decide when 86'd dishes return by default. Many venues bring dishes back automatically at the start of the next day's service, so nothing stays off by accident. Others keep them off until someone deliberately brings them back, which suits dishes that depend on an irregular delivery. Whichever you choose, make sure someone checks at the start of each service.

Tell the floor when a dish comes back, especially if it was a popular dish that guests asked for earlier.

An 86 that is handled badly damages order accuracy in several ways. Orders for the dish have to be rejected and re-entered. Substitutions made in a hurry are entered wrongly or not at all. Tables whose orders are disrupted end up with courses out of step. Each of these produces the kind of mistake that guests remember.

Handled well, an 86 causes almost no disruption. The dish disappears from every menu at once, servers know what to offer instead, and the kitchen receives no orders it cannot fill. Our guide to kitchen tickets that never need a shout covers how clear tickets keep the kitchen and the floor in step.

Every 86 is information. A dish that runs out often is telling you something: the kitchen is preparing too little, demand has grown, a supplier is unreliable, or the dish is more popular than expected. A dish that never runs out may be over-prepared, which means waste.

Keep a simple log: which dish, at what time, on which day, and why. Review it weekly. Patterns appear quickly: the special that always runs out by eight on Fridays, the fish that is short every Tuesday because of the delivery schedule, the dessert that sells out whenever it rains.

Use the log to adjust preparation and ordering. Our guide to the prep list covers how to plan how much of each dish to prepare. Running out of a dish occasionally is a sign of good stock control; running out of the same dish every week is a sign that the plan needs changing.

When a dish is 86'd early, its sales for the night are lower than its true demand. If you read the menu mix without knowing about the 86, you may conclude that the dish is less popular than it is. Equally, the dishes guests chose instead will look more popular than usual.

Keep the 86 log alongside the menu mix, and allow for it when judging dishes. A dish that sells out regularly is a strong performer, not a weak one. Our guide to menu mix covers how sold-out dishes distort the numbers.

Here is an illustrative Friday, before and after a venue changed how it handles 86s. The details are examples.

The change cost nothing in food. It saved five disappointed tables, several remade orders and a good deal of the kitchen's attention at the busiest moment of the night.

In servearound, taking a dish off is one action for the whole venue. Mark it sold out from the point of sale or from the item in the menu editor, and it is off every terminal and every guest's menu at the same moment, including tables that are mid-scan, so guests cannot order it. It comes back by itself tomorrow, or stays off until you turn it back on.

An order from the table for a dish the kitchen cannot make can be declined with its reason, and the guest's dishes go back to their cart so they can choose again. Each dish names the station that cooks it, so the kitchen display, the point of sale and the QR code menu all read the same dishes. See fulfillment and the menus module.

Either works. Showing it as sold out tells guests who came for it what happened; removing it keeps the menu clean. Be consistent.

Usually the head chef or whoever runs the pass, and perhaps the floor manager. Keep it to one or two named roles per service.

Tell them quickly and honestly, suggest an alternative and, where appropriate, offer something to make up for it.

Many venues bring them back at the start of the next service, so nothing stays off by mistake. Check at every service either way.

Substitute only with the floor told and the ticket updated, and never where allergens could change without the guest knowing.

Keep a log of 86s, review it weekly, and adjust preparation and ordering.

Yes, if the dish is on them. Add each app to the 86 checklist, because an order from an app for a dish you cannot make is a refund and a poor rating.

To 86 an item properly, take it off everywhere at once: every till, every handheld, every guest's phone and every channel. The gap between the kitchen knowing and the guest knowing is where orders for dishes that no longer exist are taken, so close it with one source for the menu and one action by one named person.

See it coming by counting limited dishes, tell the floor immediately and give servers an alternative to offer, handle updating a QR menu as the most urgent step, show guests clearly what is unavailable and bring dishes back deliberately. Keep a log of every 86, and use it to plan better, because running out of a dish should be the exception, not the routine.