Prepare one clear source of prices
Use the current DineQube menu export or sample format where available. Keep an item identifier when the format provides one; names alone can become ambiguous. Include the item name, category and the price field you intend to update. For options or sizes, preserve the distinguishing variant information.
When an export contains several sales areas or channels, identify which column is the base price. Dine-in, takeaway and online prices can differ. Do not assume that the first numeric column is the restaurant’s intended base price.
Keep currency symbols and explanatory notes out of a numeric price cell unless the provided import format explicitly supports them. A small representative file is useful for checking how the columns are interpreted before uploading the complete menu.
Understand a match before approving it
Two dishes can have similar names and still be different items. A half plate, full plate or boneless option should not be matched simply because most words overlap. Categories provide context; a stable item identifier is stronger when it is available in both the file and the menu.
DineQube’s menu tools let you review proposed price changes before applying them. Check matched items, prices that are already the same and rows needing attention. A row found in your source but absent from the live menu should be reviewed as a new item rather than silently overwriting a different dish.
Review changes in practical groups
- Compare the current price with the proposed new price.
- Review unchanged rows separately so they do not distract from real changes.
- Filter by category when checking a large menu.
- Look closely at unusually large increases or decreases and at size-based items.
- Resolve ambiguous matches before selecting them for application.
- Approve the intended changes and reopen the guest menu to verify the result.
For an image or PDF price list, reading the page is only the first step. Still compare what was read with the original document. A clear photograph and a legible price column reduce uncertainty, but do not replace the owner’s final review.
Check the menu that guests will see
After publishing, open the restaurant QR as a guest and check a few items from every changed category. Verify variants, available items and the cart total. If your team also takes manual orders, check the same dishes in that workflow.
Historical orders should be reviewed against their saved bill, rather than recalculated from today’s menu. Keep a dated copy of the input file and the approved changes so the team can investigate a pricing question later. Agree who is responsible for publishing updates before the next service.
Common questions
Should a menu import replace item photos and descriptions?
A price-only update should preserve other item details. Check the selected import mode and its review screen before applying changes.
Why do some rows still need attention?
An item may be missing, duplicated or ambiguous, or a variant may not match safely. Resolve those rows rather than assuming a similar name is the same dish.
See it with your team
Use your own menu or a room-service example in a DineQube demo. Check the guest screen and the team’s view before deciding.
Book a demo ↗