What does it mean when a dish is 86'd?
In American kitchens, a dish that has run out is "86'd" (eighty-sixed). Wiktionary lists the verb as meaning "to remove an item from menu" or "to cancel an order for food." The same word is also used for refusing service to a guest, so in a busy kitchen, say the dish name with it.
Nobody is sure where the number came from. HISTORY quotes a 1941 New York Herald Tribune line from the soda fountain days: "When a soda popper says the tuna fish salad is eighty-six, he means there isn't any more." Some kitchens also say "68" when a dish is back, but that's less common, so explain it to new staff.
Who needs to know, and in what order?
Speed matters more than the wording. A server who takes an order for a dish that's already gone has to walk back to the table and undo it. That's the moment guests remember.
- The cook calls it early. The best call is two short rib left, not short rib's out. Two left gives the floor time to stop selling it.
- Expo or the pass tells the floor. One person says it out loud to every server, the host and the bar. Don't rely on servers checking a screen.
- Write it where staff look. A small whiteboard by the pass or the server station, with the dish and the time it ran out.
- Check tables that are still deciding. Servers should go back to any table holding menus, before they order it.
- Update every place it's for sale. That means your point of sale (the till), any delivery apps, and the specials board.
If only a garnish or sauce has run out, the chef may serve the dish without it. Then servers must say what's changed when they take the order.
What should servers say and offer instead?
Give servers a swap for each dish before service starts, so nobody has to think about it at the table. Choose something close in style and price, made from stock you have plenty of.
| If this sells out | Offer | Why it works |
|---|---|---|
| Braised short rib | Roast chicken with the same mash | Same comfort, same side |
| Market fish | Shrimp linguine | Still seafood, quick to fire |
| Chocolate tart | Brownie with ice cream | Still chocolate |
| A seasonal beer | The closest beer on tap | Similar style, no wait |
These pairs are examples. Build yours from your own menu.
A short script helps servers whose first language isn't English: I'm sorry, the short rib just sold out. The roast chicken comes with the same mash, and a lot of people who like the short rib order it. If the guest had already ordered and the kitchen ran out after, the manager decides what to offer. A free dessert or a drink is common, but it's your call.
How do you plan quantities so it happens less?
Start with what you sold before. Many kitchens use a "popularity index": each dish's share of the main courses you sold, taken from your sales history. An open textbook on food production and service explains that this share "is applied to the total customer count predicted to be served for a specific meal or day."
Here's a worked example for one Friday dinner.
| Dish | Share of mains (last 4 Fridays) | At 160 mains | Prep |
|---|---|---|---|
| Braised short rib | 15% | 24 | 26 |
| Roast chicken | 25% | 40 | 42 |
| Market fish | 10% | 16 | 16 |
The extra two portions are a small buffer for the dishes that take hours to make. The same textbook mentions keeping some "emergency stock" for when the forecast is wrong. It also warns about the other side: "Constantly running out of products can ruin the reputation of your food service operation."
Your sales history has one blind spot. If the short rib sold out at 8:15 pm every Friday, the till shows 24 sold, but more people wanted it. Write down the time each dish ran out, and add portions until it lasts to the end of service.
Also note the weather, local events and big bookings next to each day's sales, as the textbook suggests. A rainy Tuesday and a game night aren't the same day.
If dishes run out often because the kitchen can't keep up with prep, the menu may be too long. Our guide to how many items to put on a menu can help you trim it.