- Approve the price and scope
- Test orders around the change
- Reconcile quantities and actual receipts
Historical sales should remain explainable without replacing earlier prices with today’s menu.
Illustrative decision process, not a product screenshot or customer result.A restaurant menu price change is complete when the approved price appears in the intended places and the restaurant can still explain orders sold before the change. Editing the current menu is one task; preserving an understandable sales history is another.
Use this process when evaluating menu management software or planning a controlled update. It covers operational approval and reconciliation, not tax or accounting advice. Confirm any formal record-keeping requirements with the restaurant’s own adviser.
Write the change before applying it
Create a short change record with item identity, old price, new price, affected branches and channels, intended start time and approver. Include any modifiers or bundles whose prices depend on the same item.
Avoid identifying an item only by its display name if several sizes or branch versions share that name. The person applying the change should be able to select the exact record without guessing. Where the software provides versioning or an audit trail, ask to see it; otherwise, agree an external record that staff can maintain.
Separate the commercial decision from the update
The restaurant decides what to charge and when. The operator applies that decision to the relevant system. A manager then checks the result through an order, not merely by reading the edit screen.
In a small business, one person may perform all three activities. Keeping the steps separate still helps catch a wrong size, branch or start date. For multiple branches, specify whether local managers can vary the price and who reviews exceptions.
Test the orders on both sides of the change
Use test data and an agreed demonstration environment. Create a completed test order at the old price, leave a second item in a basket and then apply the new price. Start a third order after the change.
| Test record | Question | Evidence to inspect |
|---|---|---|
| Completed earlier order | Does its original price remain understandable? | Order detail and receipt |
| Existing basket | How is a price change explained before acceptance? | Basket and final confirmation |
| New order | Does the approved price apply? | Item, subtotal and accepted order |
| Another branch | Is the intended branch scope preserved? | Branch-specific order |
| Modifier or bundle | Does its price remain correct? | Selected options and full calculation |
Ask what happens if a staff device has not refreshed or a channel update fails. Record the recovery task and the person responsible.
Reconcile using the prices actually sold
Consider an illustrative item sold ten times at PKR 600 before a change and eight times at PKR 650 afterward. With no discounts, refunds or other adjustments in this simplified example, the total is PKR 6,000 plus PKR 5,200, or PKR 11,200.
Multiplying all eighteen sales by the current PKR 650 price produces PKR 11,700, which is PKR 500 too high. This is why an owner needs transaction-level evidence or a report that preserves the relevant historical prices. The example is a calculation exercise, not a customer result.
Check discounts and corrections separately
A list-price change does not explain every difference in receipts. An order may include a documented discount, refund or correction. Ask the demonstrator how the proposed reports distinguish those adjustments from a change in the menu’s base price.
Choose one authorised test correction and follow it through the order detail and closing report. Do not make the report agree by overwriting an earlier transaction. The shift-closing guide explains how to keep unresolved differences visible.
Plan a recovery path
If the wrong price reaches a channel, stop and identify the scope before making another change. Decide which future orders need the corrected price and which accepted orders require a separate customer or settlement review.
Restoring the old menu price may fix future ordering, but it does not automatically resolve every order taken during the error. Keep a record of the affected period and ask the supplier how to retrieve the relevant transactions without exposing unnecessary customer information.
Ask Restrova for the specific reporting evidence
Use Restrova’s reporting and analytics and POS information to prepare a demo request. Bring the three-order test and the arithmetic example. Confirm historical price visibility, permissions and correction behaviour in the proposed configuration.
The related dashboard video introduces statistics, recent orders and the sales overview. It is not proof of every audit or price-history capability described above. Request those exact screens and outputs before treating them as included product features.
Questions restaurant owners ask
Should old receipts display the new menu price?
The restaurant needs to retain an understandable record of what was actually sold. Ask the supplier to show how earlier orders remain identifiable after a menu update.
Can we change every branch at once?
That depends on the verified controls and the restaurant’s policy. Test the intended branch scope and check at least one branch that should remain unchanged.
What is the smallest useful acceptance test?
Use one completed order, one existing basket and one new order around a price change. Inspect their calculations, then reconcile the resulting sales against the actual prices applied.
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.


