When several ingredients become unavailable during service, stop the shortage from creating new unfulfillable orders, then work through the orders you have already accepted. Name one person to coordinate the response, identify every affected dish and modifier, and update each ordering channel. Do not assume a change on one screen has reached every other place guests can order.
An ingredient shortage can affect more than the dishes that name an ingredient. A sauce may appear as a default, an extra, or part of a combo. A substitute may be available for one dish but unsuitable for another. A short order-impact matrix gives the kitchen and front counter one shared way to make those calls.
Identify affected items and workable substitutions
Start with the person closest to the stock: usually the kitchen lead. Ask what is unavailable, what can still be used, and whether the remaining quantity is reliable. A container that appears full may already be needed for accepted orders. Treat uncertain stock as unavailable until someone counts it.
Then ask the menu owner or manager to trace each ingredient through the menu. Check main dishes, sides, sauces, modifiers, bundles and scheduled specials. Include items where the ingredient is optional: an order for a dish without the missing sauce may still be workable, while an order with an extra portion may not be.
For each affected item, choose an action:
- Keep selling: The item can be made as described without using unavailable stock.
- Change with guest agreement: A workable alternative exists, but the guest needs to choose it.
- Pause: The item or affected option cannot be fulfilled reliably.
The kitchen lead should approve substitutions for preparation and capacity. The manager should check how the change affects the item description and price. Do not silently replace an ingredient that matters to the guest's choice. Staff should also avoid guessing about dietary suitability or allergens; use the restaurant's established ingredient and allergy procedures.
Write down who made each decision and when. A shift change or late delivery can otherwise leave one employee restoring an item while another is still telling guests it is unavailable.
Pause or update every ordering channel
Make a channel list before touching settings: direct online ordering, marketplace menus, phone orders, in-person ordering, and any other ordering screens the restaurant uses. Assign one person to each channel or give one manager ownership of the whole list. Record the action, the time it was made, and who checked it.
Choose the narrowest safe pause. If a channel lets staff disable the unavailable sauce without removing the entire dish, that may preserve an orderable version. If it cannot separate the sauce from the dish, pause the dish rather than hope guests will notice a note. If a shortage affects many items and changes cannot be made quickly enough, temporarily pausing the affected channel may be safer than accepting orders the kitchen cannot fill.
Check what a guest can actually select after the update. Look at pickup and delivery menus separately if they are configured separately, and check future ordering as well as immediate orders. A change may need to remain in place until stock is received and counted, not merely until the expected delivery time.
For a simulated check, use a safe test environment or stop before submitting an order. Confirm that affected items or options are not selectable and that unaffected items remain available. The simulation must not take a real card payment, send a guest message, or dispatch a courier. If the system has no safe way to simulate the change, ask the provider how to verify it without creating a live order.
Ask ordering providers whether availability can be changed by item, modifier and channel, and how quickly changes appear to guests. Also ask what happens to orders already in progress when an item is paused. Those answers help determine whether one person can safely manage the response or whether each channel needs its own owner. The online ordering buying guide offers a broader set of questions for evaluating a setup.
Use an order-impact matrix for accepted orders
New-order controls do not settle orders that are already in the queue. Have the order lead pull accepted orders from each channel, including scheduled orders. Separate orders already handed off from those still in the kitchen or waiting to be prepared. Do not mark an order resolved just because its menu item has been paused.
The following example is hypothetical. A restaurant has run out of chicken and its house sauce. The kitchen has confirmed that beans and a different sauce are available. Six accepted orders have not yet been prepared. The matrix groups those orders by the action needed; the counts add up to all six.
| Affected orders | Impact | Decision and owner | Orders |
|---|---|---|---|
| Chicken bowls with house sauce | Both ingredients unavailable | Order lead offers bean bowl with available sauce; kitchen approves preparation | 2 |
| Bean bowls with house sauce | Sauce unavailable | Order lead offers available sauce or no sauce | 2 |
| Chicken wraps without house sauce | Chicken unavailable | Order lead offers bean filling if the kitchen can make it | 1 |
| Bean bowl without house sauce | Neither missing ingredient needed | Kitchen prepares as ordered | 1 |
In this example, five orders need a guest decision and one can proceed as ordered. The proposed alternatives are assumptions, not instructions to change those five orders automatically. For each one, the order lead records the guest's choice, updates the kitchen, and follows the channel's process if the guest prefers cancellation. If an alternative has a different price, confirm the amount and handle any adjustment through the applicable order process.
The matrix is a snapshot, not a guarantee that stock will last. If the available sauce runs low while staff are contacting guests, update the count and revisit the offers that have not yet been accepted. Give the kitchen a clear cutoff: do not prepare a changed order until the guest's decision is recorded, unless the restaurant's established process says otherwise.
Prioritize orders by promised handoff time, but leave a trail for every order. A useful record includes the order identifier, channel, missing ingredients, proposed options, contact owner, guest response and final kitchen instruction. If a guest cannot be reached, follow the channel's procedure rather than inventing consent.
Assign communication, handoff and recovery
One manager should own the overall shortage response. That does not mean one person must do every task. The kitchen lead owns stock counts and feasible alternatives; channel owners make and check menu changes; the order lead reconciles accepted orders; and a named staff member handles each guest contact. If the restaurant is short-staffed, combine roles explicitly so none disappears between shifts.
Keep guest communication direct. Say which part of the order is unavailable, offer the options the kitchen has approved, and explain the next step. Give staff a short common script, but let the guest make the choice. For marketplace orders, use the contact and adjustment process provided by that channel. For direct orders, use the restaurant's established contact process. Record the result where the kitchen can see it.
Set a review time based on the next meaningful event: a delivery arrival, a stock count, or a quieter point in service. At that review, compare the matrix with the live menu and the order queue. Are any guests still waiting for a response? Did a paused modifier remain selectable somewhere? Has a substitute become scarce? Update the matrix before making new offers.
Restore items only after the kitchen confirms usable stock and the manager checks the relevant channels. Record who restored each item and verify the guest-facing menu again. A delivery estimate alone is not a stock count.
After service, keep the channel list and a blank copy of the matrix with the shift handoff materials. Review which changes took the longest and which decisions needed a manager. If ordering controls were hard to find, ask the provider for a practical walkthrough before the next busy shift. Your restaurant website and other ordering entry points should also be on the channel checklist, so staff know where guests may encounter an outdated menu.
Use this checklist to assess your current setup, then ask Fleksa about restaurant online ordering, including verified US availability and how your location would manage item and modifier shortages.
Frequently asked questions
Should we pause the whole menu during a shortage?
Not necessarily. Pause the affected items or options if you can do so reliably. If you cannot identify or update them quickly enough, a temporary channel pause may prevent more orders the kitchen cannot fulfill.
Can we substitute an ingredient without asking the guest?
Do not assume a guest accepts a meaningful change. Offer kitchen-approved choices, record the response, and follow the channel's process if the guest wants to cancel or the price changes.
What should we check before restoring an item?
Confirm that usable stock is on hand, account for accepted orders that need it, and update every affected channel. Then check the guest-facing menu and tell the kitchen and order team that the item is available again.
