- Confirm item and branch scope
- Check new and existing orders
- Restore availability after verification
A sold-out control needs an owner, a clear scope and a plan for orders already accepted.
Illustrative decision process, not a product screenshot or customer result.An unavailable-item control is useful only when the restaurant understands what it stops and what still needs a person’s attention. Hiding an item from a fresh menu does not by itself resolve a guest’s existing basket or an order the kitchen has already accepted.
Evaluate restaurant menu availability as an operational workflow. The key questions are who makes the decision, which branch and channels it affects, what happens to in-progress orders and how the item returns to sale.
Define what is actually unavailable
Start with the smallest accurate scope. The entire meal may be unavailable, or only a size, side or optional ingredient. A supplier delay at one branch may not affect another branch that has sufficient stock.
Ask the proposed software supplier which levels it can control. If a system only supports whole-item availability, the restaurant needs a different procedure from one with verified option-level controls. Record that limitation in the menu plan rather than assuming the more detailed feature exists.
Give the decision a clear owner
Agree who can mark an item unavailable and who checks that the change reached the relevant channels. During a rush, a cook may identify the shortage while a manager or cashier updates the system. The handoff needs to be short enough to use during service.
Record the branch, item, reason and expected review time in a form the team can access. A verbal instruction can be missed when shifts change. A software control may help, but the restaurant still needs responsibility for checking the outcome.
Test three stages of the same order
Use an authorised demonstration with no real customer order. Prepare one fresh session, one basket containing the item and one accepted test order before changing availability.
| Order stage | Question to resolve | What the restaurant should observe |
|---|---|---|
| Fresh menu | Can a guest still select the item? | Current branch and channel behaviour |
| Existing basket | What happens at the next checkout step? | Clear correction before acceptance |
| Accepted order | Who reviews the fulfilment problem? | Named staff task and customer communication |
| Cashier order | Does the same restriction apply? | Staff visibility and any approved override |
| Other branch | Is its availability unaffected? | Correct scope of the change |
The goal is to understand the result at each stage. Do not accept a demonstration that only refreshes the first menu screen and stops there.
Keep stock and menu controls separate until verified
A physical stock count, an inventory balance and a menu availability flag may be connected in some systems, but that connection must be demonstrated. Ingredient recipes, units, waste and timing can all affect whether a stock number should change an item’s availability.
If the proposed setup uses a manual sold-out decision, document it clearly. If the supplier offers automatic availability based on stock, ask which ingredients and rules drive the decision and test a small example. See the inventory unit guide before relying on quantities that use different pack sizes.
Handle already accepted orders explicitly
An accepted order may need a substitution, partial cancellation or another agreed resolution. The restaurant should contact the customer through its approved process and explain any change in price or delivery expectation.
Ask the supplier to show how the final order, kitchen instruction and settlement remain consistent after the correction. Do not mark an order fulfilled simply to clear it from a queue. The POS correction guide provides a complementary test for financial adjustments.
Restore availability deliberately
The item should return to sale only after the restaurant confirms it can fulfil new orders. Decide whether restoration is manual or follows a verified schedule or stock rule. Check that an old timer or shift change will not unexpectedly make the item available again.
Repeat the original channel checks after restoring it. If one branch remains unavailable, verify that its status is still correct. Keep the reason for any ongoing restriction visible to the staff who will answer customer questions.
Test the workflow with Restrova
Review the inventory, ordering website and app pages, then request a demonstration using your real menu structure. Confirm the availability controls included in your scope and any steps that remain manual.
The related settings video is an introduction to configuration. It does not establish automatic ingredient-to-menu availability or the specific exception handling described here. Those remain requirements to verify in the live session.
Questions restaurant owners ask
Is hiding an item enough to prevent every new order?
Not necessarily. Test existing baskets, staff ordering and all connected channels. Ask the supplier to explain when the availability check happens.
Should every stock difference make an item unavailable?
No universal rule fits every restaurant. First understand the item’s recipe, units and fulfilment requirements, then agree a control the team can verify.
What should staff do when the item returns?
Confirm the kitchen can fulfil it, restore the correct scope and check the affected channels. Communicate the change to the next shift.
Related Restrova demonstration
This configuration introduction provides context for discussing the proposed setup. It does not establish account ownership, every menu control or the specific acceptance checks in this guide.
Restrova Settings Demo | Restaurant System Setup & Configuration
Restrova’s settings demonstration introduces system preferences and configuration for restaurant ordering and operations.
Watch this demonstration on YouTube · Published
Written overview, not a transcript. Use a live demonstration to verify the specific requirements in this guide.


