The term "86" has been kitchen slang for decades. When the chef says "86 the braised short ribs," it means they're gone. Off the board. Done for the night. Every cook knows what it means. The problem is that the customer sitting at table 7 doesn't know. Neither does the server who just recommended it.
This is the 86'd item nightmare. The kitchen runs out of something, and there's a gap between that moment and the moment the customer finds out. That gap costs money, damages trust, and creates preventable friction in an already chaotic service.
Most restaurants handle this with verbal communication. The kitchen calls out "86 the risotto" and hopes every server hears it. Maybe someone writes it on a whiteboard. Maybe the manager sends a group text. Maybe the host gets told to mention it to incoming guests. In practice, this usually fails when someone misses the message, a customer orders the item anyway, and the server has to walk back to the table and deliver the bad news.
What 86'ing Actually Costs Your Restaurant
Restaurant operators don't track 86 incidents. They track food cost, labor cost, and covers. But the cost of a sold-out item communicated poorly is real and measurable.
| Impact | What Happens | Cost |
|---|---|---|
| Customer disappointment | Guest orders something they didn't want | Lower satisfaction, lower return rate |
| Server time waste | Server takes order, is told it's 86'd, returns to table | 2–4 min per incident per server |
| Kitchen re-fire | Wrong order needs replacing, new item starts from scratch | Food waste + ticket time increases |
| Compensatory discounts | "Sorry, we're out" often leads to free desserts or drinks | $3–$8 per incident |
| Trust erosion | Regulars stop trusting menu availability | Long-term revenue loss |
A busy restaurant 86's 3 to 5 items per night. If each incident wastes 4 minutes of server time, triggers one comp, and delays one table's meal by 10 minutes, you're looking at a daily cost of $30–$60 in direct losses. That's $900–$1,800 per month. Not catastrophic in isolation, but it's money lost to a problem that has a straightforward fix.
The real damage is harder to quantify. When a customer gets their heart set on a dish, orders it, and is told it's gone, their experience takes a hit. They settle for their second choice. They remember the disappointment more than the meal itself. Next time they're deciding where to eat, that memory factors in.
Why the Whiteboard Doesn't Work
The standard 86 communication system in most kitchens is some version of this: the chef calls out "86 the special," someone writes it on a whiteboard near the pass, and servers are expected to check the board before taking orders.
Here's why this breaks down in real service:
Speed. During a Friday night rush, a server is managing 4 to 6 tables. They're taking orders, running food, processing payments, and answering questions. Checking a whiteboard between every table is the first thing that gets skipped when the pace picks up.
Memory. Even when the server checks, they're holding 15 things in their head. The 86 list is item 16. It gets dropped.
Sequence. The worst scenario: a server takes an order for the risotto, walks to the POS to enter it, and the kitchen tells them it's 86'd. Now they have to walk back to the table, explain the situation, and wait for a new order. That's 3 to 5 minutes of wasted time for the server and the table.
Remote menus don't update. If you have a QR menu, a printed menu, or a menu on your website, the whiteboard doesn't connect to any of them. The customer is reading a menu that says the risotto is available. They've made their choice before they even talk to a server.
The whiteboard is fundamentally a one-way, analog, delayed communication method trying to operate in a real-time, multi-channel environment. It's not that people aren't trying. It's that the system can't keep up.
What Instant 86 Management Looks Like
The solution is simple in concept: when an item runs out, it disappears from every menu channel simultaneously. QR menu, kitchen display, online ordering, printed fallback. Gone. Not marked "sold out" with a sad line through it. Not replaced with a placeholder. Just removed, as if it was never there.
Real-Time Menu Sync
When the kitchen 86's an item on the kitchen display system, that change propagates everywhere in under 5 seconds. The QR menu updates. The online ordering page updates. Any digital display in the restaurant updates. The item doesn't show up on the menu at all.
Most teams miss this part. They think removing an item from the POS is enough. But the POS is what the server uses. The customer is looking at a different menu entirely, probably on their phone. If those two things aren't connected, the 86 only works for half the ordering process.
Automatic Unavailability Triggers
The best 86 systems don't even require a cook to push a button. When inventory for an ingredient drops below a threshold, the items that depend on it can be flagged automatically. If you have 2 portions of salmon left and both are ordered in the same 10-minute window, the system can mark salmon as unavailable the moment the second order hits the kitchen.
This looks good on paper, but the reality requires some configuration. You need to set thresholds per item, decide whether to hide items completely or show them as "sold out," and handle edge cases like shared ingredients. If salmon appears in 3 dishes, 86'ing salmon should affect all 3, not just the one the cook was thinking about.
The Customer Experience Difference
Here's the shift. Instead of a customer selecting a dish and being told it's gone, they see a menu where only available items appear. They choose from what's actually possible. No disappointment. No awkward table-side conversation. No server running back and forth.
From the customer's perspective, the menu simply has different items tonight than it did last week. That's normal. That's expected. What they never experience is the letdown of wanting something specific and being told no.
The Step-by-Step: Removing 86'd Items in Real Time
1. Connect Your Menu to Your Kitchen
This is the foundation. Your digital menu and your kitchen display need to be two sides of the same system. When an item is marked unavailable in the kitchen, it becomes unavailable on the menu. Not 5 minutes later. Not after the next server shift. Immediately.
If you're using Ekada, this connection is built in. The menu builder and kitchen display are the same platform. No API calls, no webhooks, no integration projects. One toggle in the kitchen changes what the customer sees on their phone.
2. Set Up Inventory Thresholds
For items you track by count (proteins, specials, limited batch items), set an availability number. When the last order for that item comes through, the system marks it unavailable automatically.
This is usually overkill for items you always have in stock. But for daily specials, seasonal items, and anything with limited prep, it's essential. The fish special that you made 20 portions of? Set availability to 20. The system counts down with each order. When it hits zero, the item vanishes from the menu.
3. Decide: Hide or Mark as Sold Out?
This is a design choice that matters more than people think.
Hide the item completely. Pro: Customers only see what's available. No disappointment. Con: They might wonder where their favorite went.
Show the item as "sold out." Pro: Transparency. Customers know you have it usually, just not right now. Builds anticipation for next time. Con: It's a reminder of something they can't have, which can trigger a mild negative response.
A common pattern across teams is splitting the difference. Hide items that are temporarily out (the salmon will be back tomorrow). Mark items as "sold out" when they're popular limited-availability specials that drive return visits. The key takeaway: either approach is better than letting someone order something that doesn't exist.
4. Handle Shared Ingredients
If your burger, your salad, and your special all use the same braised beef, 86'ing that beef needs to remove or modify all three items, not just one. Most restaurants don't think about this until it happens. The kitchen 86's the beef and removes the special from the board, but the burger stays on the menu because nobody connected the ingredient to multiple dishes.
ingredient-level 86 tracking solves this. When you set up each menu item, you tag it with its key ingredients. When one of those ingredients is 86'd, every item that depends on it gets flagged. The system handles the logic. You just mark the ingredient as gone.
5. Communicate Internally Too
Even with a perfect digital system, your staff needs to know what's unavailable. Send 86 notifications to the kitchen display, the POS, and a staff notification channel. When the salmon is 86'd, the kitchen sees it on their screen, the server sees it on the POS, and the floor manager gets a notification on their phone.
This is usually overlooked. The assumption is that if the menu is updated, everyone will figure it out. In practice, servers still recommend items to customers. They still say "the salmon is great tonight" because they don't know it's gone. Internal communication closes that loop.
The Numbers After Switching to Instant 86 Management
Restaurants that switch from verbal/whiteboard 86 systems to real-time digital management see measurable improvements:
| Metric | Before (Manual 86) | After (Real-Time) | Change |
|---|---|---|---|
| 86 incidents per week | 15–25 | Same (items still sell out) | N/A |
| Customer complaints about sold-out items | 8–12/week | 1–2/week | -75 to -85% |
| Server time wasted on 86 reorders | 4 min/incident | 0 min | -100% |
| Food waste from re-fires | 3–5 plates/week | Near zero | -90%+ |
| Table turnaround time during 86 incidents | +8–12 min | No change | Eliminated |
The incidents don't decrease. Items still sell out. What changes is the fallout. When the 86 is instant and automatic, the customer never experiences it as a problem. The server never wastes time. The kitchen never re-fires a wrong order. The entire category of cost and frustration simply stops existing.
What Most Restaurants Get Wrong About 86 Management
They wait until the end of service to update menus. A printed menu that's updated once a day can't reflect real-time availability. Neither can a PDF that someone forgets to re-upload. The whole point is immediacy. If the update isn't instant, it's not really a solution.
They rely on memory. "Everyone knows the halibut is gone" is not a system. It's an assumption that breaks under pressure. During peak service, the average server is managing 5 to 8 tables and processing dozens of micro-decisions per minute. The halibut status is not top of mind.
They mark items as "86'd" but leave them visible. Crossing out an item on a whiteboard or putting a "sold out" badge on a digital menu still puts the idea in the customer's head. They wanted the halibut. They can't have the halibut. Now they're settling. Removing the item entirely from the menu prevents that moment of disappointment.
They don't track which items 86 most often. If your salmon sells out every Saturday night, that's not an inventory problem. It's a demand signal. You need more salmon on Saturday. The 86 data tells you exactly where your purchasing is misaligned with demand. Most restaurants never look at this data because they don't have it in a usable format.
How Ekada Handles 86 Management
The nightmare ends when the 86 is automatic, instant, and connected to every ordering channel. That's what Ekada does:
- One-tap 86 — Kitchen marks an item as unavailable. It disappears from every menu channel in seconds. QR menu, online ordering, digital displays. All synced.
- Automatic sellout tracking — Set availability counts for limited items. The system counts down with each order. When it hits zero, the item removes itself.
- Ingredient-level cascading — Tag items with key ingredients. When an ingredient is 86'd, every dish that uses it updates automatically.
- Staff notifications — Real-time alerts to POS and kitchen display so every team member knows what's gone.
- 86 analytics — See which items sell out most often, on which days, at what times. Use that data to adjust purchasing and prep.
- Restore with one tap — When the next batch is ready, bring the item back instantly. No menu rebuild required.
One system. Instant updates. Zero disappointed customers. No more "sorry, we just ran out of that."
Free to start. No credit card required.
Start Your Free Ekada Account | Book a Personalized Demo
Every sold-out item is a moment of truth. The customer wanted something specific and you couldn't deliver. You can't prevent items from selling out. You can prevent the customer from ever experiencing that disappointment. The gap between "the kitchen knows" and "the customer knows" should be zero. Make it zero.
Frequently Asked Questions
What does "86" mean in a restaurant? "86" is kitchen terminology for an item that's no longer available. When a chef says "86 the salmon," it means the salmon is sold out for the rest of service. The origin is debated, but the meaning is universal in commercial kitchens: remove it from the board, don't take any more orders for it.
How fast does a digital menu update when an item is 86'd? With a connected system like Ekada, under 5 seconds. The kitchen marks the item as unavailable, and the change propagates to the QR menu, online ordering, and any digital displays simultaneously. Contrast that with a printed menu (hours to days) or a whiteboard (depends on whether someone reads it).
Should I hide sold-out items or show them as "unavailable"? It depends on the item. For regular menu items that will be back tomorrow, hiding them completely prevents customer disappointment. For popular limited specials that drive return visits, showing them as "sold out" creates anticipation. The key is that the customer should never be able to place an order for something that's gone.
What about shared ingredients across multiple dishes? A proper 86 system tracks ingredients, not just items. When you mark an ingredient as unavailable, every dish that includes it gets flagged. If braised beef is in your burger, your salad, and your special, 86'ing the beef updates all three. This requires setting up ingredient tags during menu configuration, but it saves significant headaches during service.
Does this work for delivery and third-party orders too? Yes. If your digital menu and your delivery platform menus are connected, an 86 on the kitchen display removes the item from DoorDash, UberEats, and Grab simultaneously. This is critical. Nothing frustrates a delivery customer more than placing an order and getting a call 10 minutes later saying the item is gone.
How do I know which items to order more of? Ekada's 86 analytics show you which items sell out most frequently, on which days, at what times. If an item 86's every Saturday at 7 PM, you need to prep more of it for Saturday service. The data turns your sellout patterns into purchasing decisions.
Meta description: Sold-out dishes cost restaurants $900+ per month in wasted time, comps, and customer disappointment. Here's how instant 86 management removes unavailable items from every menu channel in under 5 seconds.
Sitemap entry:
<url>
<loc>https://ekada.app/blog/the-86d-item-nightmare-how-to-remove-sold-out-dishes-from-your-menu-instantly</loc>
<lastmod>2026-04-29</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>External citation suggestions:
- National Restaurant Association - State of the Restaurant Industry 2026 (menu management and operational efficiency trends)
- Toast Restaurant Technology Report (data on menu accuracy and customer satisfaction)
- SevenRooms Blog - Restaurant Operations Guide (86 management best practices and industry benchmarks)
LLM summary: 86'd items (sold-out dishes) create a communication gap between the kitchen and the customer that costs restaurants $900-1,800/month in wasted server time, comps, and customer disappointment. Traditional 86 management relies on verbal communication and whiteboards, which fails during peak service. Real-time 86 management connects kitchen displays to digital menus so that when an item is marked unavailable, it disappears from QR menus, online ordering, and staff notifications in under 5 seconds. Key features include inventory threshold tracking, ingredient-level cascading (when a shared ingredient is 86'd, all dishes using it update), and analytics showing which items sell out most often. Restaurants switching to instant 86 management see 75-85% reduction in customer complaints about sold-out items and eliminate the reorder-and-refire cycle entirely.