Confirm an imported menu by comparing it with a restaurant-approved reference, then checking how representative orders behave from selection through routing. A visual scan alone is not enough: an item can have the right name while its required options, price, availability, or destination are wrong.
Start with high-risk items and every ordering channel you plan to use. Record each result, assign any mismatch to an owner, and retest the corrected item before accepting the menu. The sampling sheet below gives you a practical starting point.
1. Prepare the approved menu reference
Choose one version of the menu as the source of truth. It might be an export from the old system, a spreadsheet maintained by the manager, or a menu document supplemented with an option list. Whatever form you use, have the person responsible for menu decisions approve it before the comparison starts.
Give that version a date and keep a copy unchanged. If prices or recipes change during the migration, record the change separately and update the reference deliberately. Otherwise, a reviewer may flag a correct new price as an import error, or accept an old price that was meant to change.
For each item, capture enough detail to distinguish it from similar records:
- Item identifier, if one exists, category, internal name, and guest-facing name.
- Base price and each size or other price variant.
- Modifier groups, available choices, extra charges, and whether a choice is required or optional.
- Selection rules, such as the minimum and maximum number of toppings.
- Availability by day, time, channel, or location where those restrictions apply.
- Expected preparation destination and any instructions staff need to see.
Also identify items that should not be available, including retired specials and seasonal dishes. An imported item that should be hidden can cause as much trouble as a missing one.
Ask the person responsible for tax configuration to review how the approved items should be treated and compare that decision with the new setup. Keep that review separate from the menu-price comparison; this check is not a substitute for tax advice.
If your restaurant management software supports more than one location or ordering surface, note which version of the menu belongs where. A lunch item may be correct at one location and incorrect at another. A printed menu alone may not show those differences.
2. Compare imported records with a sampling sheet
First check the overall shape of the import. Are the expected categories present? Are there obvious missing items, duplicates, or retired dishes? A count can help you spot a gap, but matching counts do not prove that the records match.
Then build a sample that covers different kinds of risk. Include at least one straightforward item from each category, every high-volume or high-consequence item, and examples with required choices, optional extras, multiple sizes, and restricted availability. Include items with similar names that staff could easily confuse. Check every location and channel that will use a different menu configuration.
The following is a hypothetical example for a single-location restaurant. Its approved menu has four categories: burgers, sides, drinks, and desserts. The rows are a starting sample, not proof that the rest of the menu is correct. Record the imported result beside each reference and add rows for the restaurant's own high-risk items.
| Sample | Approved reference | What to check after import | Result and action |
|---|---|---|---|
| House burger | $12 base; one required doneness choice; cheese optional for $1.50 | Name, base price, required choice, cheese charge, kitchen destination | Pass only if all match; otherwise record each difference |
| Fries | $4; available in store and online; no size choice | Both displays, price, absence of an unwanted size requirement | Compare each channel; assign any mismatch |
| Iced tea | Small $3; large $4; one size required | Both variants, prices, selection rule, beverage destination | Check each size; retest any correction |
| Seasonal pie | $6 when offered; currently unavailable | Not selectable on active ordering surfaces | Record any surface where guests or staff can select it |
For each row, compare the actual imported record with the reference rather than simply marking that the item exists. A modifier may appear under the wrong item, allow too many selections, or carry a charge that belongs to a different size. Check the relationship as well as the text.
Guest-facing names deserve a separate look. A short kitchen name may be useful to staff but confusing on an online menu. Check spelling, descriptions, and labels where guests see them, then confirm that the associated item is still recognizable to the team preparing it.
Sampling reduces the work; it does not guarantee that every unsampled item is correct. If you find the same type of error more than once, expand the review to all items affected by that category, modifier group, or import rule. If a shared cheese modifier has the wrong price, for example, check every item that uses it.
3. Run simulated orders across the full path
A record comparison checks the setup. An order check shows whether the setup behaves as intended. Before opening to guests, ask the provider how to create simulated or test transactions that do not charge a real card, send a guest message, or dispatch a courier. Confirm how test orders will be identified and removed or excluded from operational reports.
For each sample order, compare three things: what the person selecting the item sees, what the preparation team receives, and what the order should cost. If online ordering, a counter terminal, or another surface uses a different menu configuration, repeat the relevant checks there. Ask how orders and routing can be inspected safely without sending a real customer communication.
Continue the hypothetical example with a house burger, optional cheese, large iced tea, and fries. The expected menu subtotal is $12 + $1.50 + $4 + $4 = $21.50. That figure includes only the listed menu items and cheese. It excludes tax, tips, delivery or dispatch charges, and any other fees. The responsible person should review applicable tax configuration separately; do not treat $21.50 as the final payable total.
In the simulated order, confirm that the burger requires a doneness choice, that cheese adds $1.50 once, and that the large tea adds $4 rather than the small-size price. Check that the displayed choices and quantities match the order received for preparation. The burger and fries should reach the designated kitchen destination, and the tea should reach the designated beverage destination if that is how the restaurant has configured its workflow.
Try a few failure-prone paths as well. Can the order proceed without a required choice? Can someone select more toppings than the approved limit? Does changing a size update the price correctly? Can the unavailable pie be selected? Note the expected behavior before each check so the reviewer is not guessing afterward.
Where staff rely on printed tickets or kitchen screens, include the actual equipment in the review. Ask whether the selected restaurant POS hardware will display or print the details the team needs. A correct total is not enough if a required preparation choice is missing from the ticket.
A live service pilot is different from these simulated checks. If you plan a limited live pilot after the menu passes, define who will monitor orders, how staff will report errors, and when to stop or correct service. Use normal, authorized customer transactions for live service, not invented guest messages or practice charges.
4. Resolve differences and sign off
Keep one issue log for the review. Each entry should identify the location and channel, item, expected result, actual result, owner, and status. Attach a screen capture or transaction reference when useful, taking care not to include unnecessary customer information.
Separate a mismatch from a menu decision. If the imported burger price is $13 while the approved reference says $12, the owner must determine whether the import is wrong or the reference needs an authorized update. Do not quietly change the benchmark to make the result pass.
Prioritize issues that can produce an incorrect charge, make an unavailable item purchasable, omit a required choice, or send an order to the wrong preparation destination. A minor spelling issue still needs an owner, but it may not carry the same operational risk. Agree on which issues must be closed before the affected channel or location goes live.
After a correction, repeat the original check and any related order path. If a shared modifier changes, retest the items that use it. If routing changes, inspect the resulting preparation details. Mark an issue closed only when the reviewer records the corrected result, not when someone says the change has been made.
For sign-off, save the approved reference version, the sampling sheet, the issue log, and the results of the simulated orders. The menu owner should accept any remaining low-risk issues explicitly, with an owner and deadline. Keep the tax review with the responsible person, and repeat affected checks when a menu change is made after approval.
Before choosing or configuring a restaurant POS, take this sheet to the provider and ask how your team can inspect imported options, simulate orders, and verify routing without affecting guests. Discuss your menu requirements and agree on who will make corrections and confirm the final sign-off.
Frequently asked questions
How many menu items should a restaurant check?
Cover every category and menu configuration, then include high-volume items, variants, complex modifiers, and unavailable items. Expand the sample when you find a recurring error; a fixed percentage alone does not account for menu risk.
Should we compare prices or complete orders?
Do both. Compare imported prices and option relationships with the approved reference, then simulate orders to check selections, quantities, preparation details, routing, and the expected subtotal.
Who should approve the migrated menu?
The person accountable for the restaurant's menu should approve the reference and sign-off. Involve the people responsible for preparation, ordering channels, and tax configuration in their respective checks.
