Back to blog

How to Update a Printed Menu QR Code Without Reprinting

Keep a printed restaurant menu QR code in use when prices or dishes change: point it to a stable file page, replace the PDF, and test the new version.

Oct 10, 2026Melis

A printed menu QR code is useful only while it opens the current menu. If the code points directly to a file that changes its address each time you upload a revision, the restaurant has to update every sign—or leave guests looking at stale prices. The practical fix is to make the code point to a stable managed page, then replace the menu file behind that page.

This guide shows how to update a printed menu QR code, what to check before service, and when it is better to create a new code.

First, check what the existing QR code opens

Scan the code with a phone and inspect the destination. If it opens a particular PDF URL or a fixed cloud-storage file, replacing that file may or may not preserve the public URL; this depends on the service and how the link was created. If the code encodes a static URL, editing the QR image itself will not change its destination.

A managed file page gives the QR a stable destination that can remain in print while an authorized owner replaces the file at that address. ShareKit uploads produce a public file page and QR assets; signed-in owners can use the file replacement workflow for eligible uploads. See the restaurant menu QR workflow for the broader setup.

Update a printed menu QR code in five steps

  1. Prepare the new menu. Export the approved menu to PDF. Check prices, dish availability, allergens, hours, language, and mobile readability. Add a visible revision date so staff can confirm which version is live.

  2. Open the existing managed file. Sign in to the account that owns the menu link. Confirm the share URL and QR destination match the code already printed on tables or packaging.

  3. Replace the file. Upload the revised PDF through the file's replacement action. Keep the existing share address when the workflow allows it; do not delete the old file and create a new one unless you are ready to replace the QR in print.

  4. Test the destination. Scan a proof or existing table code from a phone that is not signed in. Confirm the title, preview, prices, and download are current. Test under the actual restaurant lighting and network conditions.

  5. Record the change. Note the revision date, responsible owner, and locations where the code is printed. This makes the next update safer and gives staff a quick verification step.

If the current code is static

A static QR code that points directly to an old file cannot be redirected by changing the artwork somewhere else. There are two options: replace the printed code, or—if the existing encoded URL is a managed page you control—update the resource behind that URL. When planning new menus, create the managed page first and generate the code from that page. For the difference between a code image and an updateable destination, see ShareKit vs. a standard QR code generator.

Keep the digital menu usable

The PDF is part of the guest experience. Use selectable text instead of a scan-only image when possible; keep the page readable on a narrow screen; use descriptive headings; and make high-contrast prices easy to find. Avoid putting critical allergen or safety information only behind the QR code. Leave a printed fallback or a staff-assisted option for guests who cannot or do not want to scan.

Before publishing, have someone other than the person who exported the PDF review the content. A second reviewer can catch a missing modifier, an outdated tax note, or a mismatch between the dish name and the price. Check that the first page opens quickly, the menu is not sideways on a phone, and any embedded links work. If there are breakfast and dinner menus, name them clearly and make the opening screen explain which one is current. These small checks prevent the QR from becoming a faster route to confusing information.

For a price change, define a simple handoff: who approves it, who replaces the file, and who confirms the public link. Avoid having multiple staff members upload competing versions. Keep an internal copy of the approved source and a short change log, but do not expose internal notes in the guest-facing PDF. When an update is urgent, temporarily tell staff which printed signs may still point to an old destination, then scan the live code again after the replacement is complete.

If you are opening a new location, do not copy a QR image from an old design file until you verify its encoded destination. The original code may belong to a former vendor or point to a link that is no longer maintained. Make the account owner part of the restaurant's handover checklist, and store the final code artwork alongside the current menu source. That small bit of ownership hygiene prevents a familiar problem: staff can find the old PNG but no one knows who can update the page behind it.

Track scans carefully

Separate QR placements can help compare activity—for example, a table tent and a takeaway insert can use different uploads even when they display the same menu. ShareKit reports aggregate QR scans, page views, and downloads. Those are not unique-person counts and do not show whether a diner bought a meal. Use them to spot broad trends, then combine them with service feedback and sales data.

Avoid changing several variables at once when you compare placements. If one code is on a table and another is on a bag, note the date range and whether the same menu was available at both locations. Low scans could mean poor visibility, an unclear call to action, weak connectivity, or simply that guests prefer another ordering path; the count alone cannot distinguish those explanations. Use a short observation period, inspect the physical placement, and ask front-of-house staff what guests actually do. Treat the analytics as a prompt for investigation rather than a verdict on the campaign.

Common questions

Will I need to reprint if the menu PDF changes?

Not if the printed code points to a stable file page that you own and can update. Replace the file at that address, then test the printed code before service.

Can I change the destination of any QR code?

No. A static QR code encodes its destination. It can only keep working with a new destination if that encoded URL itself is a redirect or managed page that you control.

Does replacing a PDF update copies guests already downloaded?

No. Replacing a hosted file changes what the link serves going forward; it cannot alter a copy already saved to someone's device.

Can I see exactly which diner scanned the menu?

No. ShareKit provides aggregate file-level counts, not a named identity for each diner.

What should I print beside the code?

Use a short, clear instruction such as “Scan for today's menu,” and provide a fallback URL or staff assistance.

Related: PDF to URL · QR code guide · restaurant menu QR codes

A price change on a Thursday, timed

A neighborhood restaurant changes two main prices and removes a sold-out pasta. The tents were printed six weeks ago. The QR still encodes the tracked scan address for that upload, which redirects to the public file page. The goal is to swap the PDF before 17:00 service without touching the tents.

Give the job a clock.

  • 15:10. Export the PDF from the menu source, not from an email attachment someone forwarded. Put "Revised 22 October 2026, dinner" on page one.
  • 15:20. A second person reads the two new prices aloud against the approval message. They also check that the sold-out pasta is gone, not just struck through in a way a phone cannot see.
  • 15:30. The account owner opens the existing upload and replaces the file. This is the same address the tents already use. ShareKit allows up to five replacements on an upload. The counter is there so a file does not get silently swapped forever. If you are on replacement four of five, say so in the change log before you spend the last one.
  • 15:35. Scan one tent with a phone that is signed out. Read the revision line and both prices on the glass. Then scan a second tent at the darkest table. Two scans catch a bent card that the office scanner will not show you.
  • 15:45. Tell the floor the line they should hear: the tent is current, the revision line says today's date. If a guest already downloaded the old PDF at lunch, that copy on their phone does not change. The next scan does.

That sequence is about twenty-five minutes when the PDF is ready. It becomes an hour when the file is exported from the wrong draft. The draft problem is the usual failure, not the QR.

What the stored date actually does

Replacing the PDF does not extend how long ShareKit has stored the file. Guest uploads carry a 7-day stored date. An upload saved to an account carries a 30-day stored date. Keep One File is a one-time purchase that moves the date for that one upload, its URL, and its QR out by at least a year. Read the current price on pricing before you promise a landlord a code that will outlive the lease.

When that stored date passes, the public page, the download, and the file QR stop serving the file. Deleting the upload takes the public page down sooner. A reminder email can be sent before the date. Keep a copy outside ShareKit. Do not print a code for longer than you are willing to leave the file online, or until you delete it.

If the tent must survive a year of seasonal PDFs, the account date of 30 days is the wrong plan for that single file. Either renew your attention every month, or buy Keep One File for that upload and still replace within the five-swap limit. Five seasonal menus in a year fits. A weekly specials PDF will exhaust five replacements in five weeks. For a weekly sheet, plan a new upload and a new print, or put the weekly sheet on a page you control and keep the QR on a stable menu that changes less often.

When you should reprint

Reprint when any of these are true.

  • The existing code is a static image pointed at a file address you cannot replace.
  • The matrix is cracked, glossy, or smaller than guests can scan from their seat. For a tent read at about 30 cm, start at 25 mm wide plus quiet space, and prove it on site.
  • You have used the five replacements and the next file is a different document, not another revision of this one.
  • The account that owns the upload is leaving, and nobody else can sign in. Ownership is part of the close checklist. Export the SVG and record who holds the login before the last day.

Do not reprint merely because the font on the tent feels old, if the code still opens the current page. Print spend belongs on codes that fail or on placements you are adding, such as a new bar top.

Staff card you can tape inside the pass

Write this on one card. Do not make it a policy manual.

  1. Who may export the PDF.
  2. Who may press replace. One person. Two people replacing on the same afternoon will overwrite each other.
  3. The revision line guests should see.
  4. Which phone is the test phone, and that it stays signed out.
  5. Where the SVG lives, so a stained tent can be reprinted from the same code.
  6. The replacement count, updated in pencil.

More questions from the floor

We replaced the file and one table still shows yesterday.

That table's code is probably a different upload, a photo of an old code, or a PDF the guest saved earlier. Scan that exact tent. If it opens a different address, it was never on this file. If it opens the right address and shows yesterday, you replaced a different upload than the one you scanned.

Can the dishwasher's wet tent be updated in software?

No. Water damage is a print problem. Software can only change what a readable code opens. Reprint that one tent from the SVG.

Will guests need an account?

No. The public page opens without a recipient login. The owner needs an account to replace the file and to use the 30-day stored date instead of the 7-day guest date.

Where do I start a brand-new menu code?

Upload on PDF to URL, print from the SVG, and follow the restaurant menu QR setup if this is the first code in the room rather than a revision.