Back to the guides

QR menus

Seasonal menus: update your offer without confusion

This article was generated using AI. Publisher: QRelay — Sebastian Kula.

One menu change affects the kitchen, service and several online channels. Give content an owner, a checklist and a way to reverse a faulty update.

A seasonal menu can be small: a new soup, two dishes and a drink. Trouble starts when the kitchen uses a new recipe, service remembers the old price and a customer opens an outdated version online. A QR menu makes published content easier to update, but it cannot replace team coordination. Treat the change as a short operation with an owner, a publication time and a rollback plan. The template below also works for a weekly lunch menu or a one-day offer.

1. Set the scope and effective date

Write down exactly what is being added, removed or corrected. “Autumn menu” is too broad; “new soup from Friday, a revised lunch price and removal of lemonade” can be checked item by item. Agree the start time, ingredient availability and who decides if a delivery fails. Do not publish a dish early merely because its description is ready.

Working example: a small bistro wants three new items ready before Friday lunch. The manager selects a quiet period before opening rather than editing during the first orders. They also record that the previous menu remains the reference until checks finish. This is a suggested workflow, not a built-in QRelay scheduler.

2. Create one approved source of information

For each item, collect its name, ingredients, portion or variant, price and availability. Descriptions should support a choice: “roasted pumpkin soup, seeds, bread served separately” says more than “autumn delight”. Confirm ingredients and allergen information with the kitchen, including after supplier changes. Do not assign dietary suitability from the dish name alone.

Keep approved text in one working document available to the responsible people. Avoid scattered, conflicting messages. If you prepare other languages, have each version checked by a suitable person: QRelay does not automatically translate dish names, ingredients or prices. Make variants clear so similar names do not appear to describe different dishes.

3. Assign responsibility instead of “someone will fix it”

Even in a small venue, distinguish content preparation, price approval and checking the published result. Two people can cover these roles; no new jobs are needed. The kitchen confirms the actual product, the manager the price and timing, and someone from service checks the customer view. Agree cover for the publisher’s day off and protect account access under your business rules.

Change sheet to copy into the team notebook
StageOwnerEvidence of readiness
Content and ingredientsKitchen leadConfirmed item list
Prices and start timeManagerEvery variant priced; time agreed
PublicationNamed publisherPrevious text copied; changes listed
Check and decisionSecond checkerQR tested in venue; approve or revert

4. Update the content at the same address and keep a copy

If you use a QRelay menu, edit the existing one rather than deleting and recreating it. That keeps the printed link unchanged. For a code leading to an external page or PDF, update that content or change the existing dynamic code’s destination. A QR graphic looking similar does not prove that a replacement file contains the same address.

Before editing, manually copy the previous names, descriptions, prices and order into a document and take screenshots. This workflow does not assume automatic version history or menu export. Note which fields change. Avoid deleting items hastily when their details may soon need restoring.

5. Check the phone view, prices and customer journey

Open the menu through the physical table code, not just the editor preview. Find the new dish, read its full description and check prices, search and categories. Repeat on a smaller phone and with enlarged text. W3C reflow guidance emphasises reading without scrolling each line sideways; that is a useful goal for an online menu.

Also check contrast in the venue’s actual lighting. Pale text on a pastel background may look attractive on a monitor but be difficult at a table. WCAG specifies at least 4.5:1 contrast for ordinary text. Meeting that ratio for one colour pair is not a complete accessibility audit.

6. Reconcile the other publishing channels

Check your website, Google Business Profile, ordering platforms, entrance board and printed inserts. Updating QRelay does not synchronise them automatically. Google provides separate management for menu information and its menu link; verify the public result separately. Mark each channel as updated, intentionally unchanged or requiring action.

A permanent code cannot change a price printed beside it. An insert promising a specific price or dish through month-end needs a separate decision. Before service, tell the team what changed, what is unavailable and where to find the current version.

7. Prepare a concrete rollback plan

Record the conditions that stop the release: an incorrect price, unconfirmed ingredients or a missing essential product. Name the person who decides to revert and someone to check the result. In this QRelay workflow, rollback means manually restoring saved content or the previous destination, not relying on a promised version-history button.

After reverting, scan the table code again, check affected channels and tell service staff. Keep a note of the time and reason. The next update can then improve the process instead of reconstructing who remembered which version.

8. Review the change after the first service

Collect customer questions, naming confusion, stock shortages and readability feedback. QRelay’s menu counter shows aggregate views, not individual dish choices, unique guests or sales. Check commercial results separately in your own system or notes. Compare similar days and record other changes such as weather or promotions; more views alone do not prove the new menu worked.

  • Approved ingredients and every price.
  • Manual copy of the previous menu.
  • Physical QR and small-screen test.
  • Consistent channels and a briefed shift.
  • Decision owner and manual rollback method.

Sources and further reading

Put it to work in your business

Start with a free account and see how QRelay fits your day-to-day work.