- Define the approved change
- Check each ordering surface
- Reconcile the kitchen and bill
A shared menu is useful only when the restaurant knows where each change applies and how failures are handled.
Illustrative decision process, not a product screenshot or customer result.The best menu management system for a restaurant is the one that makes an approved change predictable across the places where the restaurant sells. A dashboard showing an updated item is only the beginning. The guest, cashier and kitchen must receive compatible information, and the restaurant needs a way to identify a channel that has not updated.
Use one controlled item change to evaluate competing systems. This guide focuses on consistency across channels; modifier design, unavailable items and price approvals have their own practical tests in this collection.
Start with a channel map
List every place that presents the menu: ordering website, customer app, cashier POS and any other system the restaurant actually uses. Include branch-specific menus and scheduled offers. Do not assume that all these destinations share one data source merely because their designs look similar.
For each destination, ask who owns the record, how updates reach it and whether a person must approve or repeat the change. If an external marketplace needs a separate manual update, record that dependency. A clearly documented manual task is more useful than an unsupported promise of universal synchronisation.
Define one complete change
Choose a test item in an authorised demonstration environment. For example, change the description of a lunch bowl, add one permitted side and make the item available only at a test branch. Keep the price unchanged initially so the team can isolate description, choice and availability behaviour.
Write the expected result before touching the software. Name the branch, affected channels and intended start time. This turns the demonstration into an acceptance test instead of a tour of attractive screens.
| Destination | Check after the change | Evidence to retain |
|---|---|---|
| Ordering website | Correct description and permitted side | Visible item and basket result |
| Customer app | Same intended rules for the selected branch | Fresh session and existing basket result |
| Cashier POS | Staff can select the approved version | Test receipt or order record |
| Kitchen handoff | Preparation choices remain clear | Kitchen-facing order detail |
| Other branch | Unaffected menu stays correct | Branch selection and item check |
Ask the supplier which destinations are included in the quote. This table describes evaluation requirements, not a claim that Restrova or another supplier automatically controls every channel.
Test an order already in progress
A menu change can happen while a guest has an item in their basket. Open a test basket before the change, apply the update and then continue checkout. Ask what happens when the original choice is no longer valid.
The guest should be able to understand any correction before accepting the final order. The restaurant also needs a record of the version that was actually sold. Avoid silently treating a current menu description as proof of what an earlier customer ordered.
Make failed updates visible
Ask the demonstrator to explain the recovery process when one destination cannot receive a change. Is there a status, a retry, a staff task or another control? Who notices the problem during service?
The exact mechanism can differ between systems. The operational requirement is that the restaurant can identify the affected destination and stop relying on an update that has not happened. Include mobile connectivity and staff handover in the discussion rather than judging only the successful path.
Give each change an owner
Separate the person proposing a menu change from the responsibility for checking it. A small restaurant may have one owner performing both roles, but the two tasks still need to happen. Record what changed, when it should apply and which channels were checked.
For a multi-branch restaurant, define which changes are central and which are local. A branch running out of a side should not accidentally remove the side from every restaurant unless that is the intended rule.
Apply the test to Restrova
Review Restrova’s ordering website, branded apps and POS information, then take the channel map to a demonstration. Confirm the exact menu controls, channel coverage and branch behaviour included in your proposed setup.
The related settings video introduces configuration. It is not evidence that every channel-update scenario in this article is supported. Ask the team to demonstrate your actual requirement and record any manual step or limitation in the scope.
Questions restaurant owners ask
Does one dashboard mean every menu updates automatically?
No. Confirm the destinations connected to that dashboard and the update process for each. External systems may have different ownership or update rules.
What should we test first?
Start with one item, one branch and a small change. Check the menu, basket, accepted order and kitchen-facing detail before expanding the test.
Can staff keep using the previous menu during a change?
Ask how the proposed system handles existing sessions and orders. Agree a change window and a recovery procedure appropriate to the restaurant’s service.
Your next practical step
Bring a list of your real sales channels and one sample menu change to the demonstration. Leave with a completed channel map and named responsibilities, not just a screenshot of the edited item. See the menu availability guide for the next operational test.
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.


