Used POS systems for restaurants: what actually transfers
The hardware is the cheap part and it is the only part that actually transfers. Everything that makes it work belongs to somebody else.
Home / Blog / QR code menu free: what you get, and what you don't
The square of ink genuinely costs nothing and always will. The whole argument is about what you put at the other end of it.
Anzul Aqeel · Founder & Director, Anunzio International FZC · 2 September 2026
You have twelve tables, a laminator, and no intention of paying an agency to put a square of ink on them. You type the obvious search, and thirty seconds later a black-and-white pattern is on your screen for nothing. That part is real. What the download button never mentions is that the pattern is only an address. Everything a guest meets after scanning depends on what you parked at the other end.
A free generator gives you one thing: an image file that encodes a web address. It does not store your menu, host it, update it, or know the link is a menu at all.
That single fact explains every limit below it. The usual sequence: somebody searches "menu qr code generator free", downloads a PNG, points it at a PDF in a cloud drive, and prints. The PDF stays a photograph of paper: pinch, zoom, tilt, give up, wave at a waiter.
One distinction catches people out after the printing is done. A static code bakes the destination into the pattern itself. Denso Wave, the company that invented the QR code, explains how the pattern carries its data and survives damage, not what happens after the scan. A dynamic code points at the generator's redirect and can be re-aimed later. That is the part free plans limit, by capping how many you keep or expiring the link.
The image is free; the destination and the reprints are not, and those are the lines that reach your accounts.
Price two of them. With a static code, any change of destination means a fresh card for all 12 tables plus spares. A laminated set redone quarterly is one set of facts paid for four times in a year. And every guest who cannot read a document on a phone asks a member of staff instead, in the busiest hour.
Three things, and they decide whether the code earns its place on the table. A generated image cannot accept an order, cannot tell the kitchen which table sent it, and cannot pull a dish off the page when the last portion leaves the pass.
Accepting an order needs a cart and a checkout behind the link: every line re-priced against your live menu at checkout, a minimum order value on delivery, and a second tap that cannot create a second order.
Knowing the table needs one code generated per table, not one copied onto all of them. When the table is the address there is nothing to type and nothing to mistype, and the ticket reaching the kitchen carries the seat number.
Pulling a sold-out dish needs stock counts that fall as orders come in. Give a dish a count and sold out flips itself at zero with no one watching; cancel an order and the portions come back. On a PDF the salmon stays until somebody makes a new one.
Ask five questions. A generator fails all five, by design rather than neglect.
Does the thing behind the code accept order-shaped information (items, quantities, a name, a number) or does it only display? Does it know which table the order came from? Can it run out of something? Does anybody get told an order exists without a person retyping it? Can you change a price tonight without touching the printed card?
A menu system answers yes five times. On Get Menu: the storefront sits on your own address at getmenu.ae, included from day one; the menu is uploaded from a spreadsheet instead of typed item by item; and when an order lands, a confirmation reaches the customer the moment they order, a ticket lands in the managers' WhatsApp group, and a rider dispatch carries the GPS pin dropped at checkout. That is 3 messages in about 2 seconds, none of them typed.
For a four-table café whose menu changes twice a year, a free code in front of a well-built mobile page is a defensible answer.
Point the code at a short address you control rather than the generator's redirect: a domain you own can be re-aimed for nothing, while a rented dynamic code stops the day the free tier does. Skip the PDF and publish a plain mobile page with real text. Print at three centimetres minimum on matte stock, because gloss under a downlight throws the scan back at the camera. Then test the printed card, not the screen, at night, on the oldest phone in the building.
Done that way a qr menu costs nothing and works. It simply stops there.
Free stops paying at one of three moments: the first reprint, the first night spent answering the phone, or the first month a marketplace takes the volume. The third is the expensive one. AED 100,000 of orders handed to an app at 28% is AED 28,000 gone before rent, and the customer's phone number leaves with it.
"A QR code is a piece of paper with an address written on it. Every argument about QR menus is really an argument about what you put at that address — the square takes thirty seconds and anyone can make one for nothing."
— Anzul Aqeel, founder of Get Menu
What sits at the address turns a scan into a second visit. Stamps land per order, per dirham, or only on the dish you want to move, on a loyalty card needing no app. Invoices go out carrying your TRN with 5% VAT, in the shape the UAE Federal Tax Authority sets out for tax invoices. The Apple wallet card is built and awaiting a certificate; the Google one runs today.
It is good enough when the menu changes rarely, nothing sells out mid-service, and a person takes the order anyway. Print a static code onto a link you control, use a mobile web page rather than a PDF, and it holds until the first price change.
A static code encodes the destination in the pattern, so it can never be re-aimed: change the link and you reprint. A dynamic code points at a redirect owned by the generator, so the destination can be edited later, which is why free plans cap or expire it.
No. A generator produces an image; taking an order needs a cart, a checkout, a re-price against the live menu, and somewhere for the ticket to arrive. Styling the square changes nothing behind it.
No app: the code opens a web page in the browser the phone already has. Payment is cash or your own card machine. There are no online payments in the system, so nothing card-shaped is stored.
The trial runs 15 days with no card details asked for, which covers two real weekends of service. After that it is a flat monthly subscription with 0% commission on orders; current figures live on the pricing page rather than here, where they would go stale.
Further reading
The hardware is the cheap part and it is the only part that actually transfers. Everything that makes it work belongs to somebody else.
Commission is the only software bill that grows every time the kitchen has a good night, and most owners have never worked out the month's total on paper.
One city wrote the fees into law, which makes them the clearest public numbers available on what delivery actually costs a restaurant.
Fifteen days with everything switched on. No card, no commission, ever.
Questions from other owners are answered in the community.