September 7, 2026How to Handle Sold-Out Items on a Digital Restaurant Menu
Keep guests and staff aligned when a dish runs out, with clear availability wording, a publishing check, and a simple reset routine.
Treat availability as part of the menu
A guest can spend several minutes choosing a dish before learning that the kitchen cannot serve it. A digital menu gives your team a place to communicate that change, but only when someone owns the update. Build a small routine around the moment a dish runs out, the message guests see, and the check that confirms the change is live.
This guide is a suggested service workflow, not a claim that menu software tracks kitchen stock automatically. Start with one menu and one shift. Agree with the kitchen on who confirms availability, then give a named floor team member responsibility for updating the guest-facing information. Keep the routine short enough to use during a busy service.
Confirm what is actually unavailable
Before changing the menu, establish whether the entire dish is unavailable or only one size, side, or optional extra. Ask whether the change lasts for the current service or needs another review later. Avoid promising a return time unless the kitchen has confirmed it.
Use the exact dish name in the handoff. “The special is gone” can mean different things to the bar, kitchen, and dining room. “Roasted mushroom toast is unavailable for the rest of lunch” gives the menu editor something specific to act on. If a replacement is offered, get its approved description and price before adding it.
Choose wording that matches the situation
Use a supported availability control if your menu tool provides one. Otherwise, choose a clearly visible text update or remove the item from the current menu according to your service practice. Do not assume every platform offers the same controls. The outcome to verify is that guests can tell what they can order.
When removing an item, retain its approved details in your internal source if you expect to restore it. That avoids recreating the description from memory. A temporary removal should not become a reason to guess a price, portion, or recipe when the dish returns.
| Situation | Possible guest-facing wording | Team check |
|---|---|---|
| Dish unavailable for this service | Sold out for lunch today | Confirm the next review point. |
| One option unavailable | Large size unavailable today | Check the remaining size and price. |
| Return time uncertain | Currently unavailable | Avoid an unconfirmed restock promise. |
| Dish permanently removed | Remove the item from the current menu | Check repeated entries and related descriptions. |
Publish and check the menu guests actually see
An editor preview is not the final check. Open the public page and confirm the exact item and wording. A guest who opened the menu earlier may still be looking at an older view, so staff should continue communicating the change at the table. Do not rely on a digital update alone to reach every seated guest.
- Update every occurrence of the dish in the affected service menu.
- Review availability wording in each published language.
- Complete the publishing step required by your menu tool.
- Open the public menu from the QR code and check the affected section.
- Tell the floor team what changed and how to help guests already browsing.
- Update the current paper menu or give staff a clear verbal correction.
Keep a short record and restore deliberately
Record the dish, affected service, change time, person who confirmed it, and next review point. For a fictional café, the entry might read: “Mushroom toast; lunch; 12:40; kitchen lead confirmed; review before breakfast.” This is an example record, not a measured operating benchmark.
At the next opening check, ask the kitchen whether the dish is ready before restoring it. Confirm that the name, description, options, and price still match the approved menu. Remove temporary wording in every language and check the public page again. Restoring yesterday’s item without a kitchen check can repeat the same problem.
Review repeated gaps with the team
After service, look at any dish that remained visible after it became unavailable. Was the kitchen message unclear, was the editor unavailable, or did the publishing check get skipped? Use the answer to adjust responsibility or simplify the handoff. Keep observations specific rather than assuming the menu itself caused the problem.
A useful routine connects kitchen confirmation, a clear menu update, and a floor-team briefing. Once that works for one shift, use the same record at handover so the next team knows which temporary changes still need attention.