- Choose variants
- Check the staff record
- Correct a problem
A feature passes when the right person can finish the task, not merely when a button exists.
Illustrative decision process, not a product screenshot or customer result.A restaurant ordering specification should describe what happens to an order, not just name ten features. A long feature list can conceal the absence of a clear handoff between the customer, staff and rider. Use the following acceptance checks with your own menu before choosing a system.
Ten acceptance checks
- Menu accuracy: compare the displayed name, price and availability with the approved menu.
- Item options: select required and optional choices and verify the final total.
- Fulfilment: test each offered pickup or delivery path.
- Customer information: confirm which details are necessary to fulfil that order.
- Staff receipt: identify who notices and accepts the order.
- Kitchen handoff: verify how preparation instructions reach the responsible person.
- Stock exception: try an item that has become unavailable.
- Delivery responsibility: identify the person assigning and closing a delivery.
- Correction: demonstrate a cancellation or mistaken item.
- Closing record: locate the completed transaction in the relevant report.
Run one order through every handoff
Choose a realistic test basket with an option, an unavailable item and a pickup alternative. Ask the demonstrator to use the same order throughout. Switching to another example at each screen can hide manual re-entry. Record each action, responsible role and visible result. An automated handoff and a staff procedure can both be workable, but they need different training and staffing.
Turn observations into requirements
Use three columns: demonstrated, requires configuration, and not established. Do not treat an icon or menu label as proof of an integration. Record the exact device or external service tested. Repeat the test after a connection interruption using the vendor’s supported recovery procedure. Ask how staff identify the authoritative order record when a customer retries checkout.
Decide what matters first
A single counter may value a clear acceptance queue more than advanced campaign tools. A delivery team may need assignment and settlement controls before a complex loyalty programme. Separate launch requirements from later improvements and obtain written scope. Restrova has existing ordering website, POS and delivery pages; use these to structure a demonstration rather than assuming every option is included.
What should the owner keep?
Keep the test basket, results and unresolved questions with the proposal. Confirm pricing through the published pricing page. A feature that cannot be demonstrated should remain a question, not a reason to claim a complete fit. Bring the acceptance sheet to a demo and use it again before launch.
A practical check: Turn a feature list into an acceptance checklist
Illustrative scenario: Use one basket containing two sizes, an optional extra and a sold-out item. Record what the customer sees and what staff receive for each choice.
- Choose variants.
- Check the staff record.
- Correct a problem.
Decision rule: A feature passes when the right person can finish the task, not merely when a button exists.

