Most table QR codes still open a file. The guest taps, the phone hesitates, and then they are looking at an A4 page that was designed for a printer. That is a poor menu, even when the dishes on it are right.
A live menu is a page. It has a short address, it fits the screen, and the code on the table does not have to change when the soup sells out.
What the PDF link actually looks like
Venues that upload a menu to their website usually end up with an address like this:
example-bistro.co.uk/wp-content/uploads/2026/02/new-menu-menu.pdf
The path is a filing cabinet. The year, the month and the filename are how the website stored a document, not how a guest looks for food. Replace the file in March and the address changes. The sticker on table four still points at February.
A Quiteful menu does not work like that. The public address is the venue, then the menu:
quiteful.com/harbour-kitchen/menu
A second site keeps the same shape, with the location in the path:
quiteful.com/harbour-kitchen/quayside/menu
The QR code can use an even shorter redirect (/q/…) so the printed code stays small. Guests who share the link can use a short menu address (/m/…). Either way, the page behind the code is the current menu, not a file from a dated folder.
What happens on a phone
Open that PDF on a mobile browser and the failure is immediate:
- The phone offers a download, or drops the guest into a PDF viewer
- The layout is a printed page: two columns, tiny type, a footer full of legal text
- Pinch-zoom is the only way to read a dish, and the guest loses their place
- There is no search, no allergen filter and no way to hide a sold-out item
- A cached copy can survive after you thought you had replaced the file
People do this standing up, one-handed, often on patchy venue Wi-Fi. Asking them to download a document first is an extra step they did not come in for.
A webpage menu scrolls, wraps to the screen and lets someone filter milk or gluten without zooming into a matrix. We have written separately about why allergen filters beat a printed grid.
The code stays. The menu moves.
Reprint cycles usually start because the file changed name, or because the PDF itself was the menu. With a live page, you print the code once. Prices, allergens, descriptions and availability are edited in Quiteful and show on the next scan. That is the same mechanism as real-time menu updates.
If the website still needs a menu, put the same page there with an embed instead of uploading another PDF. One source, two surfaces, no second filename.
When a PDF is still the right file
Keep a PDF if you need a print backup, a press pack or an archive. It is a poor thing to hand a guest as the menu they order from. If you are still weighing that switch, why PDF menus fail covers the reprint and staleness problem in more detail. This piece is about the moment of the tap.
A practical next step
Point the table code at /your-restaurant/menu. If the current menu only exists as a PDF, you can turn that file into a draft menu and review it before anything goes live. Brand the page so it looks like the room, not a generic template — see menu branding.
See how QR code menus work, or read how to put the same live menu on your website.