When should sold-out items leave the menu? A team workflow
Create a workflow that carries sold-out information from the kitchen to your digital menu, covering notification, confirmation, live checks and restoring availability.
When guests discover an item has sold out after choosing it, they have more to do than make another choice: they may become less confident in the rest of the menu. Often, the problem is not that nobody knows. It is that the sequence for passing a kitchen update to the service team and the published menu is unclear. A simple status workflow can close that gap.
Contents
Make notifications unambiguous
A staff member saying that dessert is running low is not enough, on its own, to remove it from the menu. Running low, the last portion has been served and waiting for a new batch are different situations. Agree in advance on the language the team will use. A notification should include the full product name, its status, the time and the person confirming the information. This reduces the chance of changing the wrong item when names are similar.
Imagine serving two varieties of cheesecake at lunch. If the kitchen reports that cheesecake has run out, ask which variety rather than hiding the entire category. Guessing about information that could be clarified in two minutes can leave unnecessary gaps in the menu. A single notification channel also reduces the chance of records getting lost between phone calls, group messages and verbal updates.
Track notification and publication as separate stages
Build a team workflow around the visibility options your business's tool actually offers. Not every digital menu connects automatically to stock, and Orvunai menu publishing should not be treated as a system that independently verifies physical inventory movements. The person making the change needs to record clearly the difference between receiving a notification and updating the screen guests see.
In a small business, one person may handle every task, but separating the steps is still useful. During a busy period, a manager might see the notification and leave the change for later. Recording the stage reached, instead of simply marking the work complete, makes it easier for a colleague to take over. The following example can be used on a task board or in a shared note.
| Status | Task | Completion condition |
|---|---|---|
| Awaiting confirmation | Verify the full product name with the kitchen | Product and status are clear |
| Awaiting publication | Make the appropriate menu change | Change has been published |
| Awaiting verification | Open the table's menu link | Guest view is correct |
Give service staff verified alternatives
Some guests may already have chosen the item before the menu is updated. Give the service team a short explanation of its unavailability and the options that remain. Do not assume an alternative has the same ingredients, portion or price. If a guest has mentioned a particular restriction, the employee should check that alternative's information again, rather than promise equivalence based only on a similar appearance.
Offering an alternative should not become pressure to buy. For example, explaining the differences, prices and portions of two available desserts gives guests room to decide when the daily dessert has sold out. If the digital menu lacks that information, fill the gap first. The team can then focus on providing accurate information now and correcting the record, rather than debating why the unavailable product remained on the menu.
Treat restoring availability as a fresh check
A message saying preparation has started does not mean the item is ready to serve. Before making it visible again, confirm the prepared quantity, presentation and any description changes with the kitchen. Automatically restoring yesterday's product each morning can recreate the same problem if production is delayed. Ownership of the decision to restore availability should be as clear as ownership of the decision to remove it.
At the end of the week, review the records to identify products with gaps between notification and the published-menu check. The aim is to find where a task lost its owner, rather than rank employees. Assign a backup if work regularly stalls at a particular time. If the same product repeatedly causes uncertainty, change its name or the kitchen's notification wording to make the process easier to follow.
Explore the relevant Orvunai product guide to put these steps into practice with your own menu.
Explore QR code menus for restaurants and cafés