When a guest orders an item that the kitchen cannot produce, the problem is bigger than one cancelled line. The restaurant may lose the whole basket, pay for a refund, receive a poor review and teach the guest to try another brand next time. Yet many GCC operators still manage unavailable items through verbal messages, WhatsApp groups or a single POS terminal.
Why menu availability breaks across channels
Availability changes throughout the day. A branch runs out of a prepared sauce, a bakery sells its last batch, or a delivery rider arrives during a temporary kitchen pause. If the change is recorded in one system but not pushed to online ordering, delivery marketplaces and menu boards, guests see a promise the operation cannot keep.
Multi-branch groups have an extra problem: availability is local. A product may be sold out in Doha while remaining available in another branch. Central teams need a branch-level view, not a global on/off switch.
Define the control states
Use a small set of clear states: available, low stock, temporarily paused, sold out for the day and permanently unavailable. Each state should have an owner and an expected next action. “Temporarily paused” should include a review time; otherwise it becomes a hidden permanent outage.
Set rules for high-risk items and modifiers. If a signature protein is unavailable, the system should show which combos and add-ons also need to pause. Removing only the parent item leaves broken choices in the customer journey.
Connect the kitchen signal to every selling channel
The kitchen or branch supervisor should be able to update availability at the point where the problem is discovered. That update should flow to the POS, QR ordering, direct web ordering, delivery integrations and customer-facing menu displays. If a channel cannot receive live status, assign a maximum delay and a named person to check it.
Use a simple escalation: kitchen marks the item, supervisor confirms the reason, front-of-house sees the replacement rule, and the digital channel receives the new state. For Qatar, Saudi Arabia and the UAE, document whether the same menu applies across branches or whether local production rules require separate availability.
Measure lost sales and recovery
Track more than the number of 86ed items. Measure minutes unavailable, orders affected, cancellations, substitutions, refunds and the value of baskets that contained the item. Compare the result by branch, daypart and channel.
Recovery should be deliberate. Offer a valid substitute only when the kitchen can fulfil it consistently. If a guest has already paid, record whether the refund, replacement or credit was completed. This creates a useful service-recovery loop instead of leaving staff to improvise.
Build a weekly availability review
Review the top unavailable items each week. Some problems are purchasing issues, some are preparation-capacity issues, and others are menu design problems. A product that repeatedly sells out at 8pm may need a larger batch, a different cutoff, a smaller service promise or a more profitable replacement.
Unidiner helps operators connect POS, kitchen, inventory and online ordering workflows so teams can make a change once and keep the guest-facing promise aligned. See Unidiner online ordering and connect the kitchen workflow to a clearer operating process.
Image plan: featured operational stock visual for the topic; supporting stock visuals for the control-states and measurement sections. Alt text should describe the restaurant workflow shown. Stock sourcing remains documented if media retrieval is unavailable.