How to Handle Out-of-Stock Items on Your Digital Menu

How to Handle Out-of-Stock Items on Your Digital Menu

A guest opens your menu, decides on the lamb shoulder, calls a server over, and gets told it's unavailable. Not a crisis — just a small, quiet disappointment. Multiply that by four tables tonight and two tomorrow, and it becomes a pattern that chips away at the guest experience in ways that never show up on any report.

Meeting customer demand is one of the most fundamental challenges of restaurant inventory — a customer who can't order their favourite menu item because an ingredient is out of stock is a customer who might not come back. The guest who encounters an unavailable item on a paper menu accepts it as a known limitation of the format. The guest who encounters it on a digital menu — a format they associate with "live" and "current" information — feels a small credibility gap. The menu said it was there. It wasn't. Adobe

Handling out-of-stock items well on a digital menu is not just about removing the item. It's about doing it fast enough that no guest ever sees an item they can't order, and recovering the sales that would otherwise be lost to the substitution decision.

Why out-of-stock handling matters more on a digital menu than on paper

On a paper menu, an unavailable item is an awkward conversation. On a digital menu, an unavailable item that remains visible is a trust problem.

The guest's mental model of a digital menu is that it reflects reality right now — not what was true when the menu was last designed. 82% of customers will forgive a service error if the restaurant resolves it immediately, but 22% of diners will never return to a restaurant after one bad service experience. The key word is "immediately." An unavailable item discovered by the guest before they've spoken to a server is not a service error — it's a menu accuracy failure, and it lands differently. Gocreateqr

The practical difference: when a server informs a guest that a dish is unavailable, the guest has received human communication and can pivot quickly. When a guest orders based on the menu and waits to be told — or notices the gap themselves — the failure feels systemic rather than situational.

This is also why the timing of the update is everything. A customer should never be told a dish is available, only to be disappointed moments later — the kitchen's 86 must immediately translate to a menu update, not a server reminder chain that depends on human memory under service pressure.

Step 1 — Remove the item the moment it's 86'd

The most important step is also the most time-sensitive: the moment a dish runs out, it comes off the menu. Not at the end of service. Not at close. At the moment the kitchen calls it.

On PixPlat, this takes approximately ten seconds:

1. Open the dashboard on your phone (it loads as a mobile-first web app — no separate app required)

2. Navigate to the item

3. Toggle availability to "off"

4. The item disappears from every guest's view immediately — no republishing, no QR code refresh

The toggle is designed for exactly this moment: a manager or floor supervisor with a phone in their pocket, in the middle of service, making a single tap that propagates instantly across every table in the room.

Who should have access to do this? Anyone who is likely to receive the information first — typically the floor manager or head server. Restricting update access to only the owner creates a bottleneck that defeats the purpose. Grant update rights to whoever is running the floor during each service.

Should you tell the kitchen to also call out the 86? Yes — the verbal "86" and the menu update should happen in parallel, not sequentially. The menu update protects guests who are scanning and haven't ordered yet. The verbal call protects the tables that placed an order before the item was removed.

Step 2 — Decide how the item appears when unavailable

Removing an item entirely is the cleanest solution for most scenarios. But some restaurants prefer to display unavailable items with a "sold out" badge rather than hiding them. Both approaches are valid; the choice depends on context.

When a manager marks an item as 86'd in the system, it disappears from server tablets, online ordering apps, and kitchen display screens, preventing orders from reaching the kitchen for items that can't be fulfilled. Complete removal is the standard for permanent 86s; the "sold out" badge is most appropriate for high-demand specials that guests may want to know exist, even if they can't order them tonight. QRMint

The key rule: never leave a fully available-looking item on the menu that cannot be fulfilled. The in-between states (greyed out, badged) are acceptable only if the guest's expectation is accurately set by the label.

Step 3 — Brief your floor team before service, not during it

The digital menu update handles the guest-facing side of an 86. The floor team handles the guest interaction that may still arise — from the table that was already browsing when the item went off, or the guest who asks specifically about a dish that's no longer showing.

The pre-service 86 briefing (5 minutes, every service): Before doors open, the kitchen communicates current availability to the floor team. Any items at risk of running out — specials, limited-quantity dishes, ingredients awaiting a delayed delivery — are flagged. The floor team knows before the first guest arrives which items need extra attention.

This briefing does not replace real-time digital updates during service — it supplements them. The briefing handles predictable 86s; the dashboard handles the unpredictable ones.

The guest script when an item is discussed: Train servers to never say "we're out of the lamb." Instead: "The lamb has been very popular tonight and sold out earlier this evening." The factual content is identical; the phrasing communicates demand rather than shortage. Front-of-house staff should rephrase stockouts as "The gnocchi has been popular tonight and sold out" rather than "The gnocchi has run out" — this communicates demand rather than failure, and it preserves the guest's positive perception of the dish.

Step 4 — Recover the sale with a genuine alternative

An out-of-stock item is not just an item the guest can't have — it's a sale at risk of not being replaced. A guest who was planning to order the lamb and is now told it's unavailable has to restart their decision process, which takes time, creates mild friction, and may result in a lower-margin substitution or simply ordering less.

The goal is to make that restart as smooth and as guided as possible.

Prepare two or three substitution suggestions per high-demand item before service. If the lamb sells out frequently on Friday evenings, the briefing should include: "If the lamb is unavailable, suggest the braised short rib as the closest match — same comfort food register, similar price point, equally photogenic on the menu."

A server who can say "We're out of the lamb tonight, but I'd personally recommend the short rib — it's been equally popular this week and shares the same slow-braised technique" closes the sale more often than a server who says "The lamb is sold out, can I give you a moment to decide?"

Use the digital menu to guide the substitution. When a guest is told an item is unavailable and needs to reconsider, the digital menu is a better decision tool than a verbal recommendation alone. The server can say "Take another look at the menu — the short rib is just below where the lamb was, and I think you'd enjoy it." The guest sees the photo, the description, and makes an informed pivot rather than an anxious one.

Step 5 — Use the pattern to fix the cause

Every repeated 86 is data. Experienced operators track which items get 86'd frequently and adjust par levels accordingly. If the same special sells out every Friday, the chef increases prep quantities or ingredient orders to match actual demand patterns. barkoder

On a digital menu platform with analytics, you have an additional layer of data beyond frequency: you can see how many guests viewed the item before it was removed, compared to how many ordered it. A dish that is viewed by 80% of guests but sells out by 7pm is a dish whose par level needs doubling, or whose preparation quantity needs forecasting against expected covers.

The pattern analysis that matters most:

Smart menu engineering reduces 86 vulnerability by designing dishes with ingredient overlap. When multiple dishes share key components, running out of one item doesn't cascade into multiple 86'd menu sections. This is the structural approach to the problem: not just managing 86s when they happen, but designing the menu to minimise how often they occur.

The proactive approach: reducing 86s before they happen

Reactive 86 management — removing items when they run out — is the floor of good practice. Proactive 86 prevention is the ceiling.

87% of restaurateurs saw food costs rise in 2024, and 82% expect further increases in 2025, while supply chain disruptions continue to leave restaurants struggling with inconsistent supplies. In this environment, over-reliance on any single ingredient is an operational risk that will eventually manifest as a service disruption.

Par level discipline. PAR (Periodic Automatic Replenishment) is your minimum stock threshold — your early warning system to prevent stockouts. Analyse historical sales and delivery schedules to determine minimum stock thresholds, and set par levels slightly above that to prevent shortages. For high-volume items, par levels should be recalculated seasonally and ahead of any event or promotional push.

Ingredient overlap in menu design. Build the menu so that key proteins and produce appear across multiple dishes — so that a supply disruption on one ingredient doesn't take three dishes off the menu simultaneously. A kitchen that can substitute the same braising liquid across two different protein dishes is far more resilient than one where every dish has a unique ingredient profile.

Pre-service spot checks. A 10-minute kitchen walk at the start of service — specifically checking quantities on high-demand items against expected covers — catches the "we'll probably run out by 8pm" scenario before it becomes a 7:30pm guest disappointment.

What this looks like in PixPlat's dashboard

PixPlat's menu editor handles out-of-stock management directly from the item level:

• Availability toggle — one tap per item, active or inactive, no publishing delay

• "Sold out" label — optional badge mode for items you want to flag as temporarily unavailable rather than hide completely

• Time-based availability — schedule items to appear and disappear by time of day, which handles predictable patterns (breakfast specials, lunch-only items) without requiring manual toggling during service

• Multi-location sync — toggle an item unavailable at one specific location, or across all locations simultaneously if the ingredient shortage is supply-chain-wide

→ For the complete guide to real-time menu management, see Restaurant menu management: updating your menu in real time

→ For how to structure your menu to reduce 86 vulnerability through ingredient overlap, see How to structure your menu categories to increase restaurant sales

→ For the complete digital menu strategy, see The complete guide to digital menus for restaurants

Frequently asked questions

How quickly should I remove a sold-out item from my digital menu?
Immediately — the moment the kitchen calls the 86. Not at the end of service, not when you have a free moment, and not after a server relay. The digital menu is a live document and guests treat it as such. An item that remains visible but cannot be ordered erodes trust in the menu's accuracy. On PixPlat, the toggle takes under ten seconds on a phone — there is no logistical reason to delay.

Should I show sold-out items with a badge, or remove them completely?
Both are acceptable depending on the context. Complete removal is cleaner and eliminates any possibility of a guest selecting an unavailable item. A "sold out" badge is more appropriate for high-demand specials where the demand signal has value — regular guests learn that certain specials are worth coming early for, which builds anticipation and return visits. For standard menu items that run out unexpectedly, complete removal is almost always the better choice.

What if a guest asks why their favourite dish keeps selling out?
This is valuable feedback, not an awkward moment. Train staff to respond: "It's one of our most popular dishes — we're working on making sure we have more available. Tonight I can suggest [alternative] which you might enjoy just as much." This acknowledges the pattern honestly while redirecting to a sale.

Can I schedule items to go unavailable automatically without manually toggling them?
Yes, on PixPlat. Time-based availability allows items to appear and disappear on a schedule you set in advance — which handles predictable patterns (breakfast specials that end at 11am, happy hour items active from 4–7pm) without requiring manual action during service. For unpredictable stockouts, the manual toggle remains the fastest solution.