A menu item is not available simply because it exists in the recipe book. It may be sold out, waiting for a preparation batch, restricted to a daypart or temporarily unavailable at one branch. When it remains live online, guests place orders the kitchen cannot fulfil. The result is a substitution call, refund, delay and avoidable loss of trust.
Define availability states
Use simple states such as available, low stock, sold out, scheduled, branch-only and manager approval required. Each state needs an owner and a response. A kitchen lead may mark a batch sold out, while a manager may approve a substitute. Avoid free-text updates that different teams interpret differently.
Synchronise every sales channel
The POS, website, kiosk and delivery menus must use the same availability decision. A change made on one channel but not another creates drift. Set routines for opening checks, peak-period reviews and closing updates. Where systems support it, use recipe and stock signals to suggest an item change, but retain human approval for unusual exceptions.
Protect modifiers and bundles
Availability also applies to sides, sauces, toppings and combo components. A burger may be available while the selected side is not. If the system allows the order, the kitchen inherits the problem. Map dependencies and define substitution rules before a peak shift. Show the customer a real choice rather than accepting an order that must be renegotiated.
Review lost sales and recovery
Track unavailable-item cancellations, substitutions, refunds, delayed orders and channel-specific complaints by branch, item and daypart. A repeated shortage may require a different par level, supplier plan or menu decision. A repeated channel mismatch requires a publishing control. The goal is accurate availability, not hiding demand.
Unidiner links menu, POS, kitchen, inventory and online ordering workflows. See online ordering and menu controls. For wider systems support, visit Tradify Services.