Sold-Out Items on Digital Menu Boards: An 86 Workflow
In kitchen shorthand, to 86 something is to declare it unavailable. Handling sold-out items on digital menu boards is mostly an operating procedure: someone has to notice, make the change in the right place, and confirm the screen actually changed before the next customer orders.
The technology matters less than the habit. A board that advertises a finished dish produces an apology, a remake or a refund every time somebody reads it.
Decide between a label and a removal before service
There are two reasonable treatments, and mixing them arbitrarily confuses both staff and regulars.
Label the item. Keep it visible with a short overlay such as SOLD OUT or 86. Customers learn the item exists and will return, and the layout stays stable. This suits signature items and anything people specifically visit for.
Remove the item. Take it off the board entirely. This suits daily specials, a category that is finished for the night, and anything you do not want to advertise while it is unavailable.
One caution on removal: some systems leave the vacated position empty rather than reflowing the remaining items. Menuboard Manager's documentation states plainly that with its hide setting, the remaining fields do not reflow to fill the space. Check your own layout with an item hidden before deciding.
Write down who marks it and where
Most availability failures are ownership failures. Agree these four points and post them where the team works:
- Who notices. Usually the person plating or pouring the last portion, not a manager who is off the floor.
- Where the change is made. One system of record. If the point of sale drives the board, the register is the place; hand-editing the screen instead creates a second version of the truth.
- Who verifies. The same person walks out and looks at the board, or asks someone at the counter to confirm.
- Who restores it. Availability that is never switched back is the more expensive error, because you stop selling something you have.
Keep the job small enough to do with one hand during a rush. If marking an item unavailable takes a laptop and five minutes, it will not happen at 7pm on a Friday.
The steps of the workflow, not a claim about any particular system's speed.
Do not assume point-of-sale sync is switched on
Automatic stock updates are commonly available, but they are usually a configured integration rather than a default. Toast's own documentation for the Delphi digital menu board shows that stock subscription and the out-of-stock label are settings a restaurant must turn on, that the default for the out-of-stock label setting is Off, and that changes need publishing before they take effect.
So verify your specific configuration rather than trusting an integration list:
- Mark a low-value test item unavailable in your point of sale during a quiet period.
- Time how long the board takes to change, and note whether it needs a publish step.
- Confirm whether the treatment is an overlay, a price change or a removal.
- Mark the item available again and confirm it returns correctly.
Write the result on the same sheet as the workflow. "Availability syncs in about a minute after publishing" is useful to a supervisor; "it integrates" is not.
If you are choosing a system, evaluate availability handling alongside POS integration rather than assuming the two are the same thing. Confirm the current behaviour for your own point of sale and screens before relying on it in service.
Keep the manual path available
Even with automatic updates, keep a manual override and train it. Networks fail, an item can run out for a reason the register does not know about, and a prep mistake is not a stock count.
Be aware of one interaction: where a system takes availability from the point of sale, a manual toggle can be overwritten the next time the integration sends an update for that item. Menuboard Manager warns of exactly this in its documentation. Decide which source wins in your operation, and make sure staff know which one they are using.
For menus customers read on their phones, availability is a separate surface with separate timing. A guest who already loaded the page may not see a change until they refresh. Our QR menu comparison covers how those channels differ.
Close the loop at open and close
Add two short checks to existing routines rather than creating a new one.
At open: confirm nothing is still marked unavailable from yesterday, and that everything on the board can actually be made today.
At close: note what ran out and how early. A recurring 6pm sell-out is a prep or menu decision, not a screen problem. That pattern is also worth knowing before you schedule dayparts, since the right fix is sometimes a smaller evening menu rather than a nightly overlay.
Frequently asked questions
Should a sold-out item keep its price on screen?
Usually yes when you are labelling rather than removing, so customers can plan a future visit. Make it unmistakable that the item is unavailable now; an unmarked price invites the order you cannot fill.
Is it better to hide sold-out items automatically?
It depends on your layout. Hiding is cleaner for a long list, but check whether your system leaves a gap, and remember that a disappearing signature item prompts questions at the counter.
How fast should the board update?
Fast enough that a customer reading it now is not misled. Measure your own configuration instead of assuming real time, and include any publish step in the total.
Do we still need to tell staff if the board updates itself?
Yes. Customers ask people, not screens. The board reduces bad orders; the team still needs to know what is gone and what to suggest instead.
Make the screen match the kitchen
Sold-out items on digital menu boards are handled well when one person owns the change, one system records it, and somebody looks at the screen afterwards. That habit is worth more than any automation you have not tested.
If you are reviewing your setup, run the availability test above on your current screens, then judge MenuPi against the workflow your team can realistically follow mid-service.