How to make a QR code for a restaurant menu

Make the menu work before making the code

A guest is seated, the lunch queue is growing, and the menu link opens a sign-in screen. The code may have scanned perfectly, but the experience has already failed. Start by opening your menu on a phone that is not signed into the account used to publish it. Check whether a visitor can read the dishes and prices without requesting access, installing an app, or searching through a folder of similarly named documents.

Choose a destination you can maintain: a mobile menu page or a publicly shared PDF. QRSwivo stores the link; it does not host your menu file, build an ordering system, or update dish descriptions for you. Keep a physical menu or staff assistance available for guests without a suitable phone or connection. The shorter menu-destination overview helps you compare a page with a PDF before following the setup below.

Give the destination a small acceptance test

Check the menu on cellular data as well as the restaurant's Wi-Fi. Read a few long dish names and the smallest price text without relying on the owner's large display. Open the first and last page of a PDF and check that the file is the current version. If a platform offers a preview link and an editing link, confirm you have copied the visitor-facing link. Public access should be a conscious publishing choice, not an accidental side effect of sharing your whole drive.

For a menu website, check the route a guest actually needs. Linking directly to the menu is usually clearer than linking to a homepage with several competing promotions. For multiple branches, make the branch name visible and verify its prices, opening information and contact details. These are content checks your team must perform; a successful QRSwivo save cannot tell whether the kitchen serves an item or whether a price is accurate.

Create the code and separate the two links

Open the QRSwivo generator, paste the full public menu URL and generate a code. Name it for its real placement, such as Main dining room menu. Save the private management link in a controlled place, then keep the public QR image and URL with the artwork. The printer needs the public code. They do not need the private management credential, which would allow changes to the destination.

If an account will make ongoing ownership clearer, sign in and claim the guest code using its saved management link. Claiming revokes that guest credential, so tell the responsible colleague which account now owns it. QRSwivo does not provide a shared staff-role system. Avoid inventing a team permission process by passing an account password around; decide who is responsible and use the business's approved credential arrangements.

1. Scan the generated image and confirm the correct public menu opens.
2. Copy the public QR URL into the restaurant's placement inventory.
3. Save editing access separately and verify the responsible owner can reopen it.
4. Choose a download for the layout and keep an untouched original copy.

Design the table card around the guest's next action

Use a plain instruction such as Scan for our menu, followed by a readable alternative or an offer of help. Do not promise ordering or payment if the destination only displays dishes. Leave the QR's clear border intact and keep it away from the card's trim edge, folds and decorative text. A recognizable restaurant name on both the card and the destination helps guests understand the connection, although branding alone does not establish safety.

Request a physical proof on the intended material. A glossy cover, curved holder or reflection from an overhead light may change the result compared with a flat screen preview. Try the card while seated at a real table and on more than one phone. The size and quiet-zone guide explains how to reserve enough space. Do not treat a successful office scan as approval of every dining-room placement.

Rehearse a lunch-to-evening change

As an example, a restaurant may use a lunch page during one service and an evening page afterwards. Prepare and verify both destinations before switching. Open the existing code's editor, save the evening URL, then scan the original table proof again. An already-open lunch tab will remain on the lunch website; make a fresh scan through the public QR URL when checking the update. Restore lunch afterwards if you are only rehearsing.

Think carefully before placing one code everywhere. If all cards use the same QR, a destination change affects every copy that reaches that record. Separate branches or different menus may need separate codes and clear names. The destination-update guide covers confirmation and rollback. There is no automatic menu schedule in QRSwivo, so a shift-based change needs an assigned person rather than an assumed timer.

Give the next shift enough information to act

Keep a short handover note: which code serves which room, who controls it, the intended destination, and where to report a problem. Staff should be able to distinguish a camera that sees no code from a menu website that will not load. For the first problem, examine the card and placement; for the second, try the public URL directly and check connectivity. The scan troubleshooting guide gives that distinction a useful sequence.

Include a visual inspection of your own cards in an existing opening routine. An added sticker can point somewhere unrelated without changing your legitimate record. If a guest reports an unexpected payment or login request, provide the menu another way and investigate rather than telling them to continue. The quishing guide explains those warning signs. Protecting the table card and protecting digital editing access are separate jobs.

Before putting the cards on every table

Release the finished card only after someone other than its designer has followed the whole journey. Ask that person to start with the physical card, not a link already open in a staff chat. Record which menu they reached and whether they needed help. Keep the result with the approved artwork so later reprints use the same public code and the team can repeat the check after a website or menu-provider change.

• The correct branch menu is public, current and readable on a phone.
• The approved printed card scans in the actual holder and lighting.
• A named owner can edit the code and has rehearsed a destination change.
• Private management access is excluded from the artwork and print brief.
• Guests have another way to get the menu, and staff know how to report a problem.