PDF menu QR code: how to do it, and when to stop

A pdf menu qr code is a printed square that opens the same menu file you send to the printer. It is the fastest way to get a menu onto a phone, it is usually free, and thousands of restaurants started exactly here.

This guide does two things. It shows how to set one up so it does not break, and it is honest about the four points where this setup starts costing you more than it saves.

Setting one up properly

Four steps, in this order.

Put the file somewhere stable. The address the code holds must keep working for as long as the print exists. A file sitting in a personal cloud folder, or one that a colleague can rename, is a menu waiting to go dark.

Keep the same address when you update. Replace the file at that address rather than uploading a new one beside it. If the address changes, every printed square points at last season's prices.

Generate the code and test it on two phones. One recent, one old. Ask somebody who does not know what it should show to scan it and read the third item on the second page aloud.

Print with margin. Leave clear space around the square. A code crowded by artwork or trapped in a laminated fold is a code that fails at the exact moment a hungry customer is trying it.

Done carefully, a menu pdf qr code will run for a season. Here is what it will not do.

Where it lets you down

One: it was never made for a phone screen

Adobe, which created the format, describes a PDF as a file that looks just the way you intended it and points at the ISO 32000 standard behind that promise. On paper that fidelity is the whole point. On a phone it is the problem, because the page keeps the shape it had on A4.

The accessibility guidance is specific about what a phone needs. The W3C's reflow criterion asks that content work at a width equivalent to 320 CSS pixels without scrolling in two dimensions. A fixed page cannot reflow, so the customer scrolls sideways and up and down at once, hunting the price column. Most give up and ask the waiter, which is the exact conversation the code was meant to save.

Two: it cannot know anything

The file has no idea what happened in your kitchen. It cannot tell a customer that the lamb finished at nine, and it cannot show the price you corrected this morning unless somebody exported and uploaded a fresh file.

Every one of those small gaps is repaired by a member of staff, out loud, one table at a time.

Three: it cannot take the order

This is the quiet cost. The customer reaches the end of the menu ready to buy, and there is nothing to press. They put the phone down and wait, or they call, and somebody writes the order on paper and types it again later.

Four: it leaves you with no record

A file has no memory. After a busy month you know your takings and nothing else. Not which dish sold, not who ordered twice, not one phone number you could message on a slow Tuesday.

When a PDF is genuinely the right answer

There are honest uses. A wine list that changes twice a year prints beautifully and reads fine on a phone in landscape. An allergen sheet or an ingredients declaration is a document by nature, and customers expect it to look like one. A set menu for a single event does not need software behind it.

The rule of thumb is simple. If the content changes rarely and nobody is meant to buy from it directly, a qr code for pdf menu use is fine. If it changes weekly, or you want the customer to order from it, the file is now the bottleneck.

"My first restaurant customer sent me a PDF and asked me to make it scannable. I did it in an hour, and two weeks later she called about a price change. Doing that by hand every fortnight is not a system, it is a chore you have given yourself." — Tanzeel ur Rehman, co-founder of Get Menu

What replaces it

A live menu page does everything the file does and then keeps going.

In Get Menu the menu sits at your own address on getmenu.ae, included from the first day, laid out for a phone held in one hand. There are 12 page layouts, colour themes and a font picker, and Arabic item names and descriptions sit beside the English. If your menu is already in a spreadsheet, you upload it instead of typing it again, and photos are compressed automatically so pages open quickly.

Because the page is connected to your kitchen, it can be honest. Stock counts fall as orders come in, counts run per option as well as per item, and a dish greys itself out at zero with nobody watching. Cancel an order and the stock comes back.

Because it can take the order, it does. Every line is priced again at checkout from your live menu, a double tap cannot order twice, and you can set a minimum order value. Then 3 messages go out within a couple of seconds: a confirmation to the customer, a ticket to your managers group, and a dispatch note to your riders group carrying the map pin dropped at checkout. Every send is logged with whether it arrived.

Because it has a memory, the month tells you something. Sales export to a spreadsheet, invoices carry your tax registration number as a PDF the customer downloads without logging in, and old order details are cleared automatically after 120 days while your customer list stays yours. Stamps, tiers and coupons with caps and expiry dates turn that memory into repeat business, and the loyalty card sits in Google Wallet and updates itself.

For tables, a code is generated for every table so the ticket carries the table number, and a group can order from their own phones onto one bill. For delivery, the customer picks a building and unit number from a list you control, with a fee per building.

Payment is cash or your card machine at the door. There are no online payments, so no card details exist in the system. We take 0 percent of your sales, and the trial runs 15 days without asking for a card.

How to move across without a reprint

If your existing square points at an address you control, you do not have to reprint anything. Point that same address at the new menu page and every card in the restaurant is upgraded at once. If the square points at a file inside a generator's account, change the destination there first, then reprint at your own pace.

Our guide to a qr code menu free of charge covers the no-cost options honestly, menu qrcode walks through generating and sizing a code, and if you are choosing between paper, screens and phones, read digital menu boards for restaurants.

Frequently asked questions

How do I make a QR code for a PDF menu?

Upload the file to a web address that will not change, paste that address into a code generator, then print the square with clear space around it and test it on two different phones before printing at scale.

Is a PDF menu bad for customers?

It is workable but awkward. The page keeps its printed shape, so a phone user zooms and scrolls in two directions to read prices that a normal web page would simply fit to the screen.

Can a PDF menu show that a dish is sold out?

No. The file cannot change on its own. Somebody would have to edit and re-upload it every time the kitchen ran out of something.

Can customers order from a PDF menu?

No. They can read it and then call, message, or wait for a member of staff. Ordering needs a page built to accept a basket.

Should I keep a PDF version at all?

Often yes. Keep it for printing, and for documents like allergen sheets, while the ordering menu lives on a page that can change during service.