veroliworksProject review

THE VEROLI FIELD NOTES / MENUS & PRINT

A QR menu checklist that starts with the customer.

Plan the menu, the destination, and the physical scan before printing a stack of table tents.

START HERE

Use a stable menu URL you control, readable menu content, accurate prices, and a printed proof tested on real phones. Decide separately whether customers are browsing or placing orders, and keep another way to view the menu.

Decide what the QR code should do.

A QR code is a doorway to a destination. It does not create an ordering system. Choose whether customers need to view a menu, place a pickup order, request catering, or pay at a table. Those are different tasks and may need different platforms.

A browse-only menu can be a fast mobile page with categories, prices, and useful descriptions. Ordering adds choices about item availability, modifiers, tax settings, payment processing, notifications, and who handles incoming orders. Confirm those operational details before putting “Order here” on a table tent.

For a food truck, also decide where changing hours and locations will appear. Avoid making staff edit the same information in several places without a clear owner.

Prepare one approved menu dataset.

Use one row per item. A spreadsheet is fine, but consistent fields matter more than the tool. Start with the structure below and keep the approved version in one place.

Example menu-content row, for planning only
FieldExampleCheck
Category / itemLunch / Grilled chicken bowlSame name on the register and menu?
DescriptionChicken, rice, beans, salsaApproved by the kitchen?
PriceEnter your current priceCorrect size and add-on charges?
ChoicesRice choice; optional extra proteinWhich choices are required?
AvailabilityLunch hours onlyWho updates sold-out items?
Photo / languageApproved photo; reviewed translationsDoes the photo match the item?

The restaurant should confirm ingredient, dietary, and allergen statements. Do not infer those from a photo or an old description. If the menu needs English and Spanish, review both versions with someone responsible for the food and pricing.

Keep the destination stable.

Choose a short, meaningful path on a domain the business controls, such as your-domain.example/menu. That is an example address, not a live service. Update the menu at that address when items change so the printed code can remain useful.

Before using a QR provider, ask what happens if a trial ends or a subscription is canceled. Does the code encode your menu address directly, or does it depend on the provider’s redirect? Who can change the destination? Record the answer before printing.

Include a readable website address near the code. It gives customers another route and helps them recognize where the scan should lead.

Test the menu as a customer would.

  1. Open the menu on a phone using cellular data, not just your business Wi-Fi.
  2. Find a common item, its price, and any choices without pinching or sideways scrolling.
  3. Test every category, language option, order button, and contact link.
  4. Check that no sign-in, app download, or confusing permission request blocks browsing.
  5. Ask someone unfamiliar with the menu to complete a realistic task.

A text-based mobile menu is often easier to read and maintain than a photograph of a paper menu. If a PDF is necessary, test its text size, file weight, and navigation on the actual devices customers use. Keep a printed menu or staff-assisted alternative available.

MAKE IT USEFUL

Your next step, on paper.

Save the plain-text worksheet and fill it in at your own pace. It opens in any text editor. No signup or submission.

Download the worksheet ↓

LET’S FIND YOUR STARTING POINT

What’s your
next move?

Build a brief, then call us to discuss it. The form saves a copy on your device; it does not send anything.

Your details stay in this browser until you download the brief. Read our privacy notice. No mailing-list signup.

Ready to talk? Call (956) 867-4214