Guest Experience and Hospitality

Telling Guests About Sold-Out Items (86'd Dishes)

How servers and hosts tell guests about 86'd menu items, suggest good alternatives, and keep online menus, delivery apps and the phone line in sync.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing7 min read

On this page
  1. Why the way you say it matters
  2. Build a single 86 chain
  3. When and how to tell guests
  4. Choosing a good alternative
  5. Check allergens before swapping
  6. Off-premises orders and the phone line
  7. Example: a Saturday 86
  8. Learn from what you run out of
  9. Specials and limited items: set expectations up front
  10. Practice the 86 drill
  11. Phrases to drop
  12. Frequently asked questions
  13. References
Guest Experience and Hospitality: Telling Guests About Sold-Out Items (86'd Dishes)Article coverGUEST EXPERIENCE AND HOSPITALITYTelling Guests AboutSold-Out Items (86'dDishes)Ava for RestaurantsInsightsGuest Experience and Hospitality: Telling Guests About Sold-Out Items (86'd Dishes)Article coverGUEST EXPERIENCE AND HOSPITALITYTelling Guests AboutSold-Out Items (86'dDishes)Ava for Restaurants

Key takeaways

  • Tell guests about 86'd dishes before they order, not after; a sold-out item mentioned at the greeting or menu drop is information, mentioned after ordering it is a disappointment.
  • Build a single 86 chain: kitchen to expo to POS to host to servers to every online menu, with one person responsible for each link.
  • Most restaurant traffic is now off-premises, so an 86 that only reaches the dining room is only partly done[1].
  • Suggest an alternative that matches what the guest wanted (the protein, the price, the style), and check allergens before swapping.
  • Track what you run out of and why; frequent 86s are a forecasting problem, not a service problem.

Why the way you say it matters

Running out of a dish is normal. Kitchens prep to a forecast, and some items, such as a fish special or a limited batch of short ribs, are meant to sell out. What guests remember is not that the dish was gone but how they found out. Hearing it from the server before ordering feels like being looked after. Hearing it ten minutes after ordering, while the rest of the table's food is already on the way, feels careless.

Supply pressure makes 86s more likely. USDA's Economic Research Service expects beef and veal prices to rise 8.7% in 2026[2], and food takes roughly 33 cents of every sales dollar[3]. Many kitchens are prepping tighter to protect margins, which means more nights when a popular item ends before service does.

Build a single 86 chain

  1. Kitchen calls it early

    The station cook tells the chef or expo when an item is down to a set number of portions, not when the last one is plated.

  2. Expo announces and records

    Expo calls the 86 to the floor and writes it on the 86 board with the time.

  3. POS marks it unavailable

    A manager or expo marks the item 86'd or sets a count in the POS so servers cannot ring it in.

  4. Host and servers get the word

    The host tells arriving guests if it was a featured item; servers mention it at their next table visit.

  5. Online channels follow

    The same person turns the item off on online ordering, delivery apps and any QR menu within minutes.

  6. Phone answers match

    Whoever answers the phone sees the 86 board or the POS, so callers are not promised a dish that is gone.

Write the name of the person responsible for each step on the 86 board itself. If nobody owns the online menus, nobody turns them off.

When and how to tell guests

Timing is most of the skill. Tell guests at the earliest natural point: during the greeting if a featured special is gone, when dropping menus, or while describing specials. Keep the language plain and move straight to an alternative.

Server lines for sold-out and low-stock items.
MomentWhat to say
Menu drop“Before you look, we've just sold out of the halibut tonight. The cod is excellent and cooked the same way.”
Guest orders an 86'd item“I'm sorry, that one sold out about twenty minutes ago. If you liked the sound of it, the braised lamb has a similar richness.”
After ordering (missed 86)“I owe you an apology: the kitchen ran out just as your order went in. Can I bring you the menu again, and I'll make sure your new dish comes out with everyone else's.”
Low stock“We have three of the short rib specials left, if anyone at the table had their eye on it.”
Limited batch by design“The pastry chef makes twelve of these each night, and they're gone. They're back tomorrow from 5.”

Avoid blaming the kitchen, the supplier or the previous table. Guests do not need the backstory; they need a good choice.

Choosing a good alternative

A strong suggestion matches the reason the guest wanted the dish. Ask a quick question if you are not sure: “Were you after the fish, or something light?” Then suggest one or two options, not the whole menu.

  • Same protein, different preparation: the guest wanted salmon, not necessarily the special sauce.
  • Same style: a guest who ordered the rich braise may want the other slow-cooked dish.
  • Same price band: do not push the most expensive steak as the replacement for a mid-priced pasta.
  • Same dietary profile: if the guest chose the vegan special, suggest another vegan dish.
  • For a missed 86 after ordering, the manager can offer a small gesture, such as a dessert, because the error was yours.

Check allergens before swapping

Substitutions are where allergy mistakes slip in. A guest who ordered the halibut because it was safe for them may not be safe with the cod's sauce. When federal allergen law passed, eight major allergens accounted for 90% of US food allergies and serious reactions[4], so the swap question is routine, not rare. If the original order carried an allergy flag, the server confirms the new dish with the kitchen and keeps the flag on the ticket.

Off-premises orders and the phone line

The dining room is not where most guests meet your menu. National Restaurant Association research shows nearly 75% of US restaurant traffic now happens off-premises[1], and 68% of delivery customers ordered through a third-party service in the past six months[5]. A dish 86'd in the POS but still live on a delivery app produces a refund, a cancelled order or a substitution the guest never agreed to.

Share of US restaurant traffic that happens off-premises
Share of US restaurant traffic that happens off-premisesDonut chart. Off-premises (takeout, drive-thru, delivery): 75%.Off-premises (takeout, drive-thru, delivery): 75%75%
  • Off-premises (takeout, drive-thru, delivery) 75%

Source: National Restaurant Association, 2025[1]

Show the data
ItemValue
Off-premises (takeout, drive-thru, delivery)75%
  • Link item availability between your POS and online ordering if your systems allow it, and test that it works.
  • Where it is manual, put the delivery tablets next to the 86 board and assign one person per shift to update them.
  • If an online order includes an 86'd item, call or message the guest before cooking with a clear choice: a named alternative or a refund for that item.
  • Never substitute silently on a delivery order. The guest cannot ask a server what arrived instead.

Example: a Saturday 86

Example (fictional): at 7:40 pm the grill cook tells expo there are four portions of hanger steak left. Expo calls “four on the hanger,” writes it on the board and sets a count of four in the POS. Servers mention it at their next visit. At 8:05 the count hits zero; the POS blocks further orders, the shift lead switches it off on two delivery apps and the website, and the host updates the phone script. One online order placed at 8:03 gets a call: the guest takes the flank steak instead. No guest at a table is told after ordering.

Learn from what you run out of

Record each 86 with the time it happened and the day's covers. After a month, patterns appear.

  • Items that 86 before 8 pm on most Fridays need a higher prep par for Fridays.
  • Items that 86 because of supplier shortages may need a backup supplier or a seasonal swap on the menu.
  • Items that never 86 and often get wasted may be overprepped or need a menu change.
  • Specials that sell out in the first hour may be underpriced or worth adding to the main menu.

Limited items are not a failure in themselves. A dish that sells out by design, communicated well, can become a reason to book early. The goal is to run out on purpose, not by surprise.

Specials and limited items: set expectations up front

Some dishes are designed to run out: a daily catch, a limited batch of a pastry, a weekend-only roast. Treat these differently from accidental 86s by telling guests about the limit before they set their hearts on the dish.

  • Print “while it lasts” or “limited each night” on the specials card and the website.
  • Post on social media or your Google profile when a popular limited item is back, and when it is gone for the night.
  • For guests with reservations, offer to hold one portion when they book or at seating, if your kitchen can manage it.
  • Count down at the pass and tell servers at set points, such as ten left and five left, so they can mention it.

Practice the 86 drill

Run a short drill once a month at pre-shift. The manager names an item and a time, and each person says what they do next: the cook, expo, the server, the host, and whoever runs online ordering. The gaps show up quickly, usually at the online menus or the phone.

Afterward, update the written 86 chain if anything was unclear, and post it next to the 86 board. New staff should learn it in their first week, along with the lines servers use at the table.

Phrases to drop

  • “We're out of that, sorry.” Say what you do have in the same breath.
  • “The kitchen messed up the count.” Guests do not need to hear who is at fault.
  • “Everyone's been ordering it tonight.” It sounds like the guest is late to the party.
  • “I can check if there's one left,” followed by a long absence. Check first, then offer.
  • “It's not on the menu anymore,” without an explanation, for a regular's favorite. Tell them why and whether it may return.

Frequently asked questions

What does 86 mean in a restaurant?

Kitchen slang for an item that has run out or is no longer available. When a dish is 86'd, servers stop selling it and the POS and online menus should be updated.

How should a server tell a guest an item is sold out?

Early and plainly, followed by an alternative: “We've just sold out of the halibut tonight. The cod is excellent and cooked the same way.”

What should a restaurant do if a delivery order includes a sold-out item?

Contact the guest before cooking and offer a named alternative or a refund for that item. Never substitute without asking.

How do restaurants reduce 86'd items?

Log every 86 with the time and covers, then adjust prep pars by day, add backup suppliers and rethink items that sell out early every week.

References

  1. National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑

  2. USDA Economic Research Service (2026). Food Price Outlook - Summary Findings (opens in a new tab) ↑

  3. National Restaurant Association (2026). Restaurants remain resilient despite challenging business conditions (opens in a new tab) ↑

  4. US Food and Drug Administration (2004). Food Allergies (opens in a new tab) ↑

  5. National Restaurant Association (2026). National Restaurant Association comments to the FTC on the Food Delivery Fees ANPRM (Project No. P267101) (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo