Operations insights
How to Check a Paper Menu After Import: Match Missing Items, Misaligned Prices, and Set Options
Start with the confirmed current source, then match every item on the paper menu to its digital counterpart. Keep a discrepancy log to distinguish omissions, duplicates, portion or option assignments, prices, and what’s included. Have the responsible person confirm unclear source material before making changes. Pay particular attention to set menus spanning pages, price-change stickers, and zero or blank prices, so a tidy-looking digital menu doesn’t conceal factual errors.
After importing a paper menu, first match each item on the source to its place in the digital menu. Then check that the name, portion or size, price, and what’s included all match. A tidy-looking page doesn’t prove the information was recognized correctly. Check set menus spanning pages, handwritten price changes, small print in the margins, and zero or blank prices against the source and what you actually offer.
Choose the current source first—don’t import several outdated versions
Gather the dine-in, takeaway, drinks, and lunch menus. Have the responsible person confirm which versions are current, along with prices and availability. If an old printed menu has price-change stickers, clarify what the final price should be; mark items that are no longer sold. Flatten the pages for photos, avoid glare and cropped edges, and check that the PDF includes every page. If something isn’t legible, take another photo or ask the responsible person rather than letting the recognition tool guess.
Keep one matching record for each discrepancy
- Source type, version, page, and item: ____; corresponding digital category, dish, and portion or size: ____.
- Source content: ____; digital content: ____; discrepancy type: omission/duplicate/price/assignment/inclusion relationship/outdated source: ____.
- Affected portion size, required option, add-on, or set menu: ____; are images and translations also affected: ____.
- Basis for final confirmation: ____; responsible person: ____; corrected location: ____; review result: ____.
This record is for locating content errors, not for repeating the full pre-launch check. MenuSnap Menu import supports images or PDFs permitted by the current interface. Import, translation, and image-optimization tasks and usage depend on plan and account conditions. While waiting for results, check existing tasks instead of repeatedly submitting the same materials.
What to check for each type of discrepancy
- Omissions: Check page footers, the backs of pages, and sidebars for serving times, included items, and notes on paying the difference. Don’t look only at the main dish list.
- Duplicates: Confirm whether items with the same name are different sizes, dine-in or takeaway options, or different combinations. Don’t merge them just to remove duplicates.
- Misaligned prices: Match each dish name and portion or size to its price, line by line. Check decimal formatting, multiple prices, and wording such as “starting at” or “extra.” Don’t assume a zero or blank price means free, and don’t copy the price of a neighboring dish.
- Option assignments: Check that drink sizes and side dishes haven’t been turned into separate dishes by mistake, and that required and optional choices appear under the correct dish.
- Set-menu relationships: Review combinations that span pages together. Distinguish what’s all included, where you must choose one of two options, what must be ordered separately, and what requires paying the difference. Don’t let a side-by-side listing replace a clear explanation of these relationships.
- Outdated source material: Ask the kitchen to confirm what is actually served and the responsible person to confirm prices and availability. Keep the basis for corrections instead of faithfully copying old errors.
Group checks by content relationships, not mechanically by page count
You can organize and check one category at a time, but review a set menu that spans pages together with the relevant details on the other page. Have one person check against the source while another checks the digital entries, marking what’s matched and what needs confirmation. Keep dine-in and takeaway options distinct when their prices, portions, or packaging differ. Check category headings separately from the dishes themselves.
Confirm ingredient and allergen information against your restaurant’s recipes and supplier records; don’t fill in gaps based on recognition results or photos. Resolve unclear source wording before checking the target-language version. If the same error is copied into several languages, more content will need correcting.
Review a full selection on a phone
Check that the category, dish name, description, options, extra charges, and image all refer to the same offering. Does a long name obscure the differences? Could portions be mistaken for one another? Do guests have to keep switching pages to find out what’s included? Falling back to the default language doesn’t mean the translation is complete. After making changes, return to the same page and check it again. Make sure any printed backup menu also uses confirmed content.
Finish content checks and service preparations separately
Once content errors are resolved, clarify whether the menu is for browsing only or also accepts orders, who checks the orders, how the kitchen receives them, and how payment is handled. KDS and printing require the relevant plan, configuration, and compatible equipment. Being able to open a menu doesn’t mean the kitchen or payment setup is ready. Contact support about settings you’re unsure of, and continue serving existing orders using the confirmed process.
Keep the current source and discrepancy log. When updating the menu later, follow up only on the affected fields so new staff don’t accidentally restore information from an old printed menu. If the same point still needs explaining during several similar service periods, work out whether it was missed during recognition or simply wasn’t clear, then update the relevant content rather than importing the whole menu again.