- Identify the original state
- Authorise the correct adjustment
- Reconcile every affected record
An order edit, a cancellation and a payment refund are different actions and should not be treated as interchangeable.
Illustrative decision process, not a product screenshot or customer result.A restaurant POS is often easiest to judge when an order goes wrong. A guest changes an item, a cashier selects the wrong quantity or an accepted order cannot be fulfilled. The system and staff process must explain what changed, who approved it and what happened to preparation and payment.
Use this guide as a set of demonstration requirements. It does not claim that every POS, including Restrova, supports every adjustment in the same way. Confirm the exact behaviour and payment-provider responsibilities in your proposed setup.
Define the original state first
Before testing a correction, record whether the order is only being entered, has been accepted, has reached preparation or has been completed. Separately record whether payment is unpaid, collected or uncertain. These states influence the appropriate action.
For example, removing an item from an unsubmitted basket is different from cancelling food already prepared. Changing an order total is also different from returning a previously collected payment. A useful POS demonstration preserves those distinctions.
Use four controlled correction cases
| Case | Starting condition | What to verify |
|---|---|---|
| Quantity mistake | Cashier entered two instead of one | Corrected quantity and total before acceptance |
| Item change | Restaurant already accepted the order | Current instruction reaches preparation |
| Cancellation | Work cannot be fulfilled | Status, reason and responsible role remain clear |
| Refund request | Payment was already collected | Order adjustment and money movement are reconciled separately |
Use sample values and an authorised test arrangement. Never trigger a real refund or production cancellation merely to complete a software checklist.
Follow the changed instruction through the restaurant
After an authorised item change, ask the kitchen lead what to prepare and the packer what to include. Identify whether they can distinguish the current instruction from an earlier printout or screen state. A successful edit in the cashier’s view is only part of the test.
If a manual notification is part of the proposed workflow, document who sends it and how the receiving person confirms it. Manual steps may be acceptable in some operations, but they should not be hidden behind a claim of complete automation.
Test authority and explanation
Use separate cashier and supervisor roles where the proposed system supports them. Ask which actions require approval and what information is retained about the change. Test an action the cashier should not be allowed to perform.
Record the original reference, reason, authorising person and resulting state. These are useful operating requirements; do not assume an audit trail exists merely because a report lists the final amount. Ask to inspect the actual record.
Reconcile money independently
An illustrative order starts at PKR 1,200 and an authorised item removal reduces the agreed order amount to PKR 900. If no payment was collected, the remaining collection requirement differs from a case where PKR 1,200 was already paid. The restaurant must be able to explain the PKR 300 difference.
For digital payments, confirm which system initiates and confirms any refund and how the result is matched to the order. Do not promise an instant refund when timing depends on another provider. A refund request and a confirmed refund are not necessarily the same state.
Review the closing report after corrections
Ask how the sample changes appear in end-of-shift reporting. Identify the definitions of sales, cancellations, discounts, collected amounts and outstanding amounts used by the proposed system. Do not force unlike report measures to match without understanding their meaning.
Keep an independent calculation for the small sample set. If the report differs, find the exact record or definition responsible. A manager should be able to explain the result without deleting history to make the totals look tidy.
Apply the tests to a Restrova discussion
Review Restrova POS/Admin, order-handoff guidance and the related dashboard demonstration. The video introduces the interface; it does not certify every void, permission or refund requirement in this guide.
Bring the four cases to a demo and record the supported workflow. Combine them with the shift-closing exercise and compatibility checks before approving the proposal.
Correction questions
Is a void the same as a refund?
Do not assume so. Ask the supplier to define its terms and distinguish order cancellation from the movement of money already collected.
Should staff delete an incorrect order?
Use the agreed correction procedure and preserve the explanation needed for reconciliation. Unexplained deletion can make later review harder.
Can a demo use real customer payments?
Use an authorised safe test flow. Production financial actions require the owner’s explicit approval and the appropriate provider procedure.
Related Restrova demonstration
This dashboard introduction provides context for discussing restaurant order records and reporting. It does not demonstrate every report, correction, permission or commercial requirement in this guide.
Restrova Restaurant Dashboard Demo
The Restrova dashboard walkthrough introduces order statistics, recent orders and a sales overview, alongside access to restaurant management tools.
Watch this demonstration on YouTube · Published
Written overview, not a transcript. Use a live demonstration to verify the specific requirements in this guide.


