To keep a sold-out item off a kiosk, give one person clear authority to mark it unavailable, then check that the change reaches every kiosk before accepting more orders. Also ask what happens to a guest who selected the item before the change. A hidden menu button alone does not settle an item already sitting in a cart.
Build the procedure around four points: who makes the change, what happens to active carts, how the update reaches the order and kitchen, and who approves the item’s return. Verify the workflow with your software provider before relying on it during a rush.
1. Assign ownership of the availability change
Start with the place where staff will learn that an item is gone. A cook may know the last portion is on the grill, but the person controlling the menu may be at the counter. Decide how that message travels and who is responsible for acting on it.
For each shift, name a primary person and a backup. Give both the access and training they need to make the change. If only a manager can edit availability and that manager is away from the floor, decide who can reach them and what staff should do in the meantime.
Next, identify the system that controls the kiosk menu. Is the change made in the kiosk software, the restaurant POS system, or another menu tool? Ask whether one change covers all kiosk devices and whether it also affects other ordering channels. Do not assume that marking an item unavailable on one screen changes it everywhere.
Write down the exact item staff should change. A menu can contain similar names, separate sizes or a bundled meal that includes the unavailable food. Ask your provider whether those related listings must be changed separately. Your procedure should tell staff what to check, rather than relying on them to remember every variation under pressure.
If an update cannot be made promptly, choose a fallback. A staff member might direct guests to the counter while the kiosk is taken out of service, following the provider’s instructions. A paper sign can help explain the situation, but it should not be the only barrier if the kiosk still accepts the order.
2. Decide what happens to an active cart
The hardest case is a guest who selected an item just before it sold out. The item may disappear from the menu while remaining in that guest’s cart. Ask the provider when the system checks availability: when the guest adds the item, during order review, at submission, or at more than one point.
Set an acceptance rule before the demonstration. A practical rule is that an unavailable item must not become an accepted order. If it is already in a cart, the guest should receive a clear instruction to remove or replace it before completing the order. Ask what the screen actually says and whether the guest can continue with the remaining items.
Also agree on the exception path. If an order was accepted before staff marked the item unavailable, who checks whether the kitchen can still make it? If it cannot, who contacts or assists the guest and arranges a replacement or refund under the restaurant’s normal procedure? That is a separate problem from preventing a new order after the change.
Use this hypothetical simulation to make the discussion concrete. A guest adds a mushroom sandwich to a cart. Before the guest submits it, the shift lead marks the sandwich unavailable. The desired result is a clear prompt that prevents the sandwich from being submitted and allows the guest to revise the cart. This is an acceptance target, not a claim about any particular system.
Run the scenario in a sandbox or other practice mode confirmed by the provider. Do not use a real card payment, send a guest message or dispatch a courier. If the provider cannot simulate the full path safely, ask for a demonstration of the available steps and document which behavior still needs checking before a live service pilot.
3. Check the update from kiosk to kitchen
An availability change is only useful when the relevant screens and order flow reflect it. Check each kiosk, not just the device where staff made the change. Ask whether a device must refresh, how staff can tell an update has arrived, and what happens if a kiosk temporarily loses its connection.
Then follow the order path. Compare the menu display, active cart, order confirmation and kitchen ticket or display. The kitchen display system is a useful place to check what the kitchen would actually be asked to prepare. A menu that looks correct at the kiosk is not enough if an older cart can still produce an accepted order for the sold-out item.
The worksheet below turns those checks into a staff procedure. Its expected results are targets to agree with the provider, not assumptions that every product handles availability in the same way.
| Check | What staff should look for | If the target is not met |
|---|---|---|
| Availability control | The designated staff member can mark the correct item unavailable. | Use the backup owner and keep affected kiosks out of service if necessary. |
| Kiosk menu | Every affected kiosk no longer offers the item for a new selection. | Check refresh or connection steps; direct guests to staffed ordering until resolved. |
| Active cart | A guest cannot submit the unavailable item and receives a useful next step. | Ask the provider for a safe workaround; do not rely on the menu change alone. |
| Order and kitchen | The simulated confirmation and kitchen output do not contain a newly submitted sold-out item. | Trace where the update failed before putting the workflow into service. |
| Restoration | Staff confirm stock and see the item available again on each affected kiosk. | Leave it unavailable until the discrepancy is resolved. |
Record who performed each check and what they saw. If the menu changes on one device but not another, ask whether the issue is a delay, a connection problem or a separate configuration. The answer determines whether staff should wait, refresh or stop using the affected kiosk.
A simulation checks the flow without creating real transactions. A live service pilot is different: guests may place genuine orders, so assign someone to monitor the kiosks and kitchen, handle exceptions and stop the pilot if the agreed rule is not met. Do not treat a successful simulation as proof that every service condition has been covered.
4. Restore the item only after a stock check
Returning an item to the menu deserves an owner too. Before switching it back on, have the kitchen confirm that the ingredients are present and that the item can be prepared as described. A delivery arriving at the back door is not the same as the kitchen being ready to sell.
Agree on a minimum usable quantity or another clear kitchen signal for your operation. If an item depends on a garnish, sauce or side that has not arrived, decide whether staff should keep the item unavailable or offer an approved alternative through the normal menu process. Do not quietly return a listing that promises something the kitchen cannot serve.
Once the designated person restores availability, check each affected kiosk again. Confirm the correct item and related listings are visible as intended, and run a safe practice check if your setup permits one. Tell the kitchen and counter team that the item is back so they are not working from different assumptions.
Keep a short shift record: item, time marked unavailable, person responsible, time restored and any devices that needed attention. This is not a substitute for checking the screens. It gives the next shift a way to spot recurring delays and ask the provider a precise question.
Next step: Take the worksheet to your software evaluation and ask the provider to walk through the active-cart and multi-device checks with your team. Compare those requirements with the Fleksa restaurant kiosk and ask how availability would be configured for your location.
Frequently asked questions
Is hiding a sold-out item from the kiosk menu enough?
Not necessarily. A guest may already have it in a cart. Check whether the system blocks submission and gives the guest a clear way to revise the order.
Should staff change availability on every kiosk?
That depends on the setup. Ask where the change is controlled and whether it reaches every device automatically. Staff should still verify each affected kiosk.
What should happen if an unavailable item reaches the kitchen?
Follow your restaurant’s exception procedure: check whether it can be prepared, assist the guest if it cannot, and resolve the order as appropriate. Then investigate the availability flow before relying on it again.
