What does 86 mean in a kitchen, and why

At half past eight, the chef calls across the pass: "Eighty-six the lamb." The kitchen hears it, the sous chef crosses it off the board and the servers nearby nod. But the server at the far end of the room, taking an order from a table of six, does not hear it, and two lamb mains go through on the next ticket. Ten minutes later, she has to go back to the table and explain that the dish they chose is no longer available.

What does 86 mean? In a restaurant kitchen, to 86 a dish is to take it off the menu because it has run out, or can no longer be served, for the rest of the service. It is one of the oldest and most useful words in kitchen slang. It is also one of the easiest to get wrong, because the word itself only works if everyone who takes orders hears it at once.

This guide covers what the term means, where it may come from, how it is used today, why it matters to guests and the team, and what should happen on every screen, board and menu the moment a dish is 86ed. Every venue and figure in it is an example.

To 86 something, in restaurant language, is to declare it unavailable. "Eighty-six the salmon" means there is no more salmon tonight. "We're 86 on the tart" means the tart has sold out. The word can be a verb, to 86 a dish, or an adjective, the dish is 86.

The same word is used, more rarely, for refusing to serve a guest, or asking one to leave: a guest who has been "86ed" is no longer welcome. In most kitchens today, though, it simply means a dish has run out.

Nobody knows for certain where 86 comes from. It was recorded in American soda-fountain slang by the early 1930s, when a newspaper column listed it as code for "all out of it", and it has been used in restaurants and bars ever since. Its origin has attracted dozens of theories.

One of the most often repeated is that it began as rhyming slang for "nix", meaning to refuse or cancel. Others link it to a New York bar's street address or to codes used at lunch counters. None is proven, and the word's history matters far less than what it does in a kitchen tonight.

Today, 86 is called whenever a dish can no longer be served: the last portion has gone, an ingredient has run out, a batch did not come out right or a piece of equipment has failed. It can apply to a whole dish, a component, such as a side or a sauce, or a single option, such as a particular cut.

The call is usually made by the chef or the person running the pass, and it should be the only voice that makes it. A kitchen where several people 86 dishes in different directions soon has servers selling dishes that are gone and avoiding dishes that are still available.

When you 86 an item, three things should happen at once. Every person who takes orders should know, so no more are sold. Every menu the guests can see should stop offering it, so no guest chooses it. And the kitchen should note it, so the board, the prep list and tomorrow's order reflect it.

The difficulty is the "at once". A call across the pass reaches the people in the kitchen and the nearest servers. It does not reach the server at the far end of the room, the host taking a phone order or the guest browsing a digital menu at a table.

Running out of a dish is not always a failure. A kitchen that never runs out of anything has usually prepared too much and thrown the rest away. Selling out of a popular special at nine o'clock can be a sign of good prep, not bad.

What matters is how the venue handles it. Our guide to running out of a dish at half past eight covers the decisions behind the call: when to stop selling, what to offer instead and how to prep better next time.

For a guest, an 86 is only a problem if they hear about it too late. A guest told before they order that the lamb has sold out chooses something else and thinks nothing of it. A guest told after ordering, or after waiting, feels let down, especially if they chose the venue for that dish.

The goal is simple: no guest should order a dish the kitchen can no longer make. Every minute between the call and the moment every order point knows is a minute in which that can happen.

For the team, an 86 that does not reach everyone causes extra work and awkward conversations. The server has to go back to the table, the kitchen has to deal with an order it cannot make and the manager may need to offer something to make up for it.

A clear process removes all of that. When the call reaches every order point at once, the servers simply stop offering the dish, and the evening carries on.

The 86 is a small example of a larger subject: kitchen communication. Every service depends on information moving quickly and accurately between the kitchen and the floor: what is available, what is running low, which tables are waiting, which guests have allergies.

Agree how each kind of information travels. In a small venue, a call across the pass and a note on the board may be enough. In a larger one, or one with digital menus, the information needs to travel through the systems as well as the voices.

The best 86 is the one the team saw coming. A kitchen that calls "four left on the lamb" gives the servers time to sell the last portions to the right tables and to warn guests who are still deciding.

Make "running low" a call of its own, made at a set number of portions for the dishes most likely to run out. It turns a sudden stop into a planned ending, and it reduces the number of guests who choose a dish moments before it disappears.

Many kitchens keep a board at the pass showing what is 86 and what is running low. The board is a simple, visible record that every cook and server can check before taking or sending an order.

Keep it up to date through the service, and clear it at the end, carrying forward anything that will still be unavailable tomorrow. A board that still shows last night's 86 confuses the next service.

The floor team's part is to know what is 86 before every order, and to tell guests early. A good habit is to mention any 86 when presenting the menu, so guests choose from what is available rather than from what is printed.

When a guest asks for a dish that has gone, offer an alternative they are likely to enjoy: a similar dish, the server's own recommendation or the special that is still available. A disappointment handled warmly is quickly forgotten.

Updating a QR menu is the part of the 86 that most venues forget. A guest browsing the digital menu at their table, or ordering from it, sees whatever the menu says, not what the chef called across the pass. If the digital menu still shows the lamb, the guest may order it, and the call has failed.

The digital menu must change the moment the dish is 86ed, and change back when it returns. That is only practical if the 86 is made once, in one place, and reaches every menu automatically, rather than relying on someone to remember to update each screen.

The same applies to every other menu the guest can see: the online ordering page, the delivery apps and any screen in the venue. A dish that is 86 in the kitchen but still available on a delivery app will be ordered, and the order will have to be cancelled or changed.

Know every place the menu appears, and how each one is updated when a dish runs out. Where a channel cannot be updated quickly, consider taking the dish off it earlier in the evening than the dining room.

Sometimes a dish comes back: a delivery arrives, a fresh batch is ready or the problem is fixed. Bringing it back should be as clear as taking it off. The chef calls it, the board is updated and every menu offers it again.

Decide in advance whether an 86 lasts until the end of the service or until the next day. A dish that sold out at dinner may be back at lunch tomorrow; one that is off because of a supplier problem may be gone for a week.

Every 86 is information for tomorrow's prep list. A dish that sells out early every Friday needs more prepared on Fridays; one that sold out because of a bad batch needs a different fix.

Record each 86 with the time it was called and the reason. Over a few weeks, the record shows which dishes run out, when and why, and the prep list can follow.

The same record helps the ordering. An ingredient that runs out every weekend needs a larger order before the weekend; one that runs out after a supplier's short delivery needs a backup source.

Look at the 86s each week alongside the orders. A pattern of the same item running out is a sign to change the order, not to keep apologising to guests.

Sometimes a dish is 86ed for reasons other than running out: a problem with an ingredient's quality, a piece of equipment that has failed or an allergen concern with a batch. In those cases, the 86 protects guests as well as the menu.

Treat these calls as seriously as any other, and make sure they reach every order point just as quickly. A dish taken off because of a quality problem must not be served from a menu that missed the call.

New members of the team need to learn the word and the process: what 86 means, who calls it, where it is shown and what to do when a guest asks for a dish that has gone. Kitchen slang is part of every venue's culture, but it is confusing to someone hearing it for the first time.

Include the 86 in the induction, alongside the other words the kitchen uses. Our guide to a restaurant glossary for new managers covers many more.

The 86 is one of many short words a kitchen uses to move information quickly. "Heard" confirms that a call was understood. "Behind" warns someone that a person is passing behind them. "Fire" tells a section to start cooking a held dish. "All day" asks for the total of one dish across every open ticket.

Each word saves seconds and prevents accidents, but only if everyone understands it. A new cook who does not know what "all day" means will answer the wrong question at the busiest moment.

Bars use 86 as kitchens do: a spirit, a beer or a cocktail ingredient has run out. A bar's 86 often arrives at the worst moment, in the middle of a round, and the bartender has to offer an alternative on the spot.

Keep a spare of the drinks most likely to run out, and tell the floor team when a drink is 86, so they stop recommending it at the tables. A cocktail list that keeps offering a drink the bar cannot make frustrates guests and bartenders alike.

Specials are often made in limited numbers, so they are the dishes most likely to be 86ed. Tell the floor how many portions there are at the start of service, and call the count as it falls: "six left on the special".

A special that sells out at eight o'clock is a success, as long as the last guests to order it were told before they chose. Announcing the number at the start lets servers recommend it to the tables most likely to enjoy it.

Sometimes a dish is 86ed for one guest rather than for everyone: the kitchen cannot make an allergen-free version safely tonight, perhaps because a shared fryer cannot be cleaned in time. The dish stays on the menu for others, but not for that guest.

Make sure the server knows before offering the dish, and that the guest is told honestly. "We cannot make that one safely for you tonight" builds more trust than a dish served with an uncertain promise.

How a guest hears that a dish has gone matters. "We have just sold the last of the lamb, I am sorry, but the duck is wonderful tonight" sounds like care. "That's 86" sounds like kitchen talk the guest was not meant to hear.

Keep the kitchen's words in the kitchen. On the floor, say plainly that the dish has sold out and offer an alternative the server genuinely recommends.

Sometimes the last portions of a dish are worth holding back: for a table that booked because of it, or for a large party that has pre-ordered it. Decide who may hold portions and how, so the kitchen is not caught between a server's promise and a dish that has already been sold.

A short note at the pass, such as "two lamb held for table twelve", keeps everyone honest about what is really left.

At the end of service, review the night's 86s with the kitchen: which dishes ran out, at what time and why. Five minutes at the close turns the night's disappointments into tomorrow's prep list.

An invented bistro runs out of its lamb special at half past eight most Saturdays. The chef calls it at the pass, but the digital menu and the far end of the room keep selling it, and several tables a night are told after ordering. The bistro changes its process: the chef calls "running low" at five portions, and the 86 is made once on the till, which takes the dish off every menu and order point at once.

The chef also records each 86 with its time. After a month, the record shows the lamb selling out at almost the same time every Saturday, so the kitchen prepares more of it on Saturdays. Guests stop being told too late, and the lamb sells out later, to more tables.

In servearound, an item is 86ed on the till with a search and a confirmation: it comes off the digital menu straight away and no one can order it until it is put back, with "Back on" restoring it. In the menu library, a dish marked sold out can be set to "Bring back tomorrow", when it returns by itself, or "Keep sold out" until it is turned back on, and it applies on every menu the dish is on.

Digital menu boards and the table's QR menu change at once, so the call reaches the guests' screens as well as the team. servearound does not connect to delivery apps, so those listings are changed on each platform. See point of sale and kitchen and the menus module.

That a dish, or part of one, has run out or cannot be served for the rest of the service.

Nobody knows for certain. It was recorded by the early 1930s, and rhyming slang for "nix" is one common theory.

The chef or the person running the pass, and only them.

At once, through every order point and menu, not only by voice.

It must stop offering the dish the moment it is 86ed.

Yes: a "running low" call at a set number of portions.

The same way it was taken off: called, shown and updated on every menu.

Record them, with times and reasons, for the prep list and the orders.

What does 86 mean? To 86 a dish is to declare it unavailable for the rest of the service, a word used in American kitchens since at least the 1930s, of uncertain origin. When you 86 an item, every order point, every menu and the kitchen's board must know at once, or guests will order a dish that has gone.

Treat running out of a dish as information: call "running low" first, give the floor an alternative to offer and record each 86 for the prep list and the orders. Good kitchen communication, and updating a QR menu and every other menu the moment the call is made, turn the 86 from an apology into a non-event.