The sold-out workflow is the seconds-long sequence a kitchen uses to mark an item unavailable across every menu a guest can see—QR codes, tables, and the website. Done right, it sharply reduces the number of guests who try to order something the kitchen can no longer serve, and saves staff from repeating, “Sorry, we’ve just sold out.”
In restaurant slang, to “86” an item means it is no longer available. The term is decades old, but the operational problem it describes is older than the word, and the fix is simpler than the slang. What has changed is that a digital menu can reflect a sold-out item in real time, where a printed menu or static PDF cannot. That does not make printed menus obsolete; it makes the live version an important companion for keeping availability current.
This is the fourth lever in digital menu optimization. Once category structure makes items easy to find, photos make high-margin dishes look worth ordering, and pricing psychology reduces spend friction, the sold-out workflow is what protects the trust those optimizations built. A guest who gets burned by an unavailable dish once remembers it longer than they remember any photo.
Why do out-of-stock items break guest trust?
An out-of-stock item breaks trust because it is a broken promise at the moment of highest intent. A guest has scanned the menu, chosen a dish, built an expectation, and committed—then staff have to walk it back. The disappointment is disproportionate to the price of the dish.
The break is worst at peak service, which is also when kitchens run out of things most often. A Friday dinner rush at a busy tapas bar can sell out of paella between 8:00 and 8:30pm. If the menu still shows paella as available at 8:45, several newly seated tables may try to order it—and each one receives the same apology. The kitchen did nothing wrong; the menu was simply out of date.
Printed menus require manual updates, and a QR code that points to a fixed PDF still shows the outdated file until someone replaces it. A live digital menu closes the gap: the moment the kitchen marks an item sold out, it greys out or hides across every active digital touchpoint—tables, QR codes, and the website—within seconds. A printed menu can remain available for guests who prefer paper, with its QR code offering a current view of availability. For the foundational setup that makes this possible, see our complete guide to digital and QR code menus.
What is the sold-out workflow?
The sold-out workflow is a four-step sequence that takes an item from “just ran out” to “invisible to every guest” in under a minute.
- Call it. The kitchen calls the sell-out the moment the last portion is fired—not when the pan is empty and someone remembers five orders later. The expeditor or head chef owns the call.
- Toggle it. A designated front-of-house staff member taps the sold-out toggle on the digital menu. The item greys out or hides across every touchpoint within seconds.
- Confirm it. The toggler confirms the change is live by checking the menu on their own phone—not the kitchen screen, which may be cached or on a different update cycle. What matters is what the guest sees.
- Notify the floor. A quick verbal heads-up to servers: “sea bass is sold out.” Servers can still guide guests who ask, and they are not blindsided if a guest mentions the dish.
The whole sold-out workflow should take less than 60 seconds. Anything longer and guests are ordering the item in the gap between the kitchen running out and the menu catching up.
| Step | Who owns it | Time target |
|---|---|---|
| Call the sell-out | Expeditor or head chef | At the moment the last portion is fired |
| Toggle sold-out | Designated front-of-house staff | Under 30 seconds |
| Confirm live on guest-facing menu | Same staff member, on their own phone | Under 15 seconds |
| Notify the floor | Expeditor | Under 15 seconds |
Who should own the toggle?
One person per shift should own the toggle—not “whoever is closest to the screen.” Shared ownership means no ownership, and during a rush the toggle is the first thing that gets skipped.
The principle is to avoid assigning it to someone who is routinely away from the pass or unable to reach the menu during service. In a larger venue that is usually a front-of-house lead or manager moving between the kitchen pass and the floor—they hear the sell-out call from the expeditor, keep the menu open on their phone, and can confirm the change without leaving their station. In a small café where one person serves, runs food, and takes payment, that person can own the toggle; what matters is that it belongs to someone who is on the floor and reachable throughout service.
If the owner is working the floor, the owner owns it. The point is that one named person, per shift, knows the toggle is theirs—same as who runs the register or who locks up.
At pre-service briefing, name both the toggler and a backup. If the primary person goes on break or leaves the floor, ownership has to be handed over explicitly—the same way register or locking-up responsibility is handed over. Without a named backup, the toggle quietly becomes nobody’s job the moment the primary person steps away.
Should sold-out items be hidden or greyed out?
The rule depends on how long the item will be unavailable. Grey out short-term stockouts—an item that will return the same service or the next day. Hide items that will be gone for an extended period: a discontinued dish, a seasonal special finished for the year, or something the kitchen cannot remake for a week.
Greying out a short-term stockout keeps the menu structure stable. Guests who saw the dish earlier do not wonder if they are looking at the wrong menu, and returning guests recognise it when it comes back. Hiding, in contrast, makes the menu look inconsistent between a first scan and a return visit.
A greyed-out item should read as unavailable at a glance:
- Reduce its visual emphasis so the eye skips past it, while keeping the item name and “Sold out” label readable—don’t dim it so far that it becomes illegible on a dim screen.
- Overlay a clear “Sold out” label—not a subtle dot or icon. Plain text removes ambiguity for guests reading on a small phone in low light.
- Disable the tap or order action if the menu supports ordering, so the guest cannot add it to a cart by mistake.
For a long menu with many sold-out items—common on delivery marketplaces—too many greyed-out rows can make the list feel empty. In that case, hiding long-gone items and greying out only the temporary ones keeps the category structure scannable without misleading anyone.
How should items come back in stock?
Bringing an item back is the second half of the workflow, and it gets skipped more often than the sold-out toggle itself. A kitchen fires a new batch, the item is available again, but the menu still shows it sold out—so guests order something else, and the new batch goes to waste.
The fix is the same sequence, reversed: the kitchen calls “sea bass is back,” the same designated toggler un-toggles the item, and confirms it live on the guest-facing menu. Treat restocking with the same urgency as selling out. A batch that took 40 minutes to prep should not sit invisible for 20 minutes because no one flipped the toggle back.
This is where most sold-out workflows fail: teams remember to mark things gone, but forget to mark them back. Build the restock step into the kitchen’s batch-ready routine, same as the sell-out call is part of the last-portion-fired routine.
The problem: A neighborhood bistro marks the slow-braised short rib sold out at 7:30pm during a busy Saturday service. The toggler greys it out correctly, but when the kitchen pulls a new batch at 9:15pm, no one un-toggles it. The short rib stays marked sold out through the rest of service. Several tables choose other mains, and two portions remain at closing.
The real-world fix: Treat the restock toggle as a kitchen handoff, not a front-of-house memory task. The moment a new batch is ready, the cook responsible calls “short rib back” to the pass, the expeditor relays it to the toggler, and the toggler un-greys the item and confirms it live on their phone—same 60-second sequence as the sell-out, just reversed. The batch is not “ready” until the menu says so.
How does this protect orders and reduce staff interruptions?
The biggest benefit of a sold-out workflow is not average order value—it is fewer failed order attempts, fewer disappointed guests, and fewer “is this available?” questions that eat staff time during a rush. When guests discover their first choice is unavailable only after ordering, substitutions become rushed. Some pick a lower-priced fallback (which is where pricing psychology works against the kitchen if the anchor item is the one that sold out), others skip the item entirely, and staff get pulled into repeated explanations.
Removing unavailable dishes earlier gives guests time to consider the full menu and lets staff recommend suitable alternatives—the high-margin dish the kitchen actually wants to push that night, ideally one with an appetizing smartphone photo—instead of improvising under pressure.
The reverse is just as valuable. An item that comes back but stays marked sold out is a missed order for the rest of the service, and newly prepped stock that goes to waste at closing.
Pair this with the broader digital menu optimization playbook—structure, photos, pricing, and real-time accuracy—and the menu stops leaking revenue in the places where most venues lose it quietly.
Stop letting out-of-stock items dictate your Friday rush. Nommy’s digital menu lets one staff member grey out unavailable dishes and bring them back the moment a batch is ready—across every table, QR code, and the website within seconds—start free, no credit card required.
A sold-out workflow that runs both directions—marking items gone the moment the kitchen runs out, and back the moment a batch is ready—is what turns a live digital menu from a static list into a menu guests can trust.