A qr code restoran is only worth what sits behind it

The square of printed card costs nothing. You can generate one in a minute, print a hundred, and have them laminated by the end of the week.

That is why so many tables in Jakarta and Surabaya already have one, and why so few of them do anything useful. A qr code restoran only opens a link. Everything that matters (whether a diner can order, whether the price is current, whether the kitchen hears about it) is decided by what that link points at, and most of them point at a PDF.

What happens when the code opens a PDF

A diner scans, waits for a file to download over a warung's wifi, and gets a photograph of your menu. Then they pinch and zoom.

Three things follow, and none of them are the code's fault:

The price is whatever the file says, including after you changed it. A PDF is a snapshot; the moment you print the sticker, the menu is frozen.
The dish you ran out of at seven is still on the page at nine, so somebody orders it and somebody has to walk over and apologise.
Nobody can order. The diner reads, closes the tab, and waves at a member of staff. That is the exact interaction the code was supposed to remove.

You have digitised the paper without digitising the ordering. The card is doing one tenth of the work it could.

A code that opens a PDF has moved your menu onto the customer's phone and left every decision on your side of the table. The point was to move the ordering, not the paper.

— Tanzeel ur Rehman, co-founder of Get Menu

What changes when it opens an ordering page

Point the same square of card at an ordering page and the table starts working on its own.

The diner sees each dish with its description and its declared allergens written underneath, so the question is answered before anyone has to ask. Options and add-ons carry their own prices, so extra sambal is a choice with a number attached rather than a note somebody has to remember at the pass. Live stock means the count is honest: while two portions remain the page says two, and the moment they are gone the dish greys itself off, mid-scroll, in front of the person who was about to pick it. Counts run per item and per option, so a dish can be on while one of its extras is off.

Then the order goes through. The kitchen ticket arrives on WhatsApp within about two seconds, and a timer starts. WhatsApp is where an Indonesian kitchen already lives; Meta's own developer documentation treats exactly this kind of business message as a core use of the platform. The table is the address. Because the code is table-specific, the ticket already knows where the food goes, so nobody types a table number and nobody mishears one.

If the same restaurant also delivers, the same page handles it: a GPS pin at checkout, the building picked from a list you wrote, and the delivery fee you set for that building applying itself.

The order rules sit underneath all of it, doing quiet work. Every line is re-priced at checkout against the live menu, so what the customer is charged is what your menu says right now rather than what it said when they opened the tab. A double tap cannot place the order twice. Opening hours are enforced, so nothing arrives after the kitchen has closed. An auto-confirm timer picks up the orders nobody reached during a busy twenty minutes, and the customer follows their own status page (no login, no account) instead of asking when the food is coming.

The reasons a printed code fails to scan

These are worth more than they look, because a code that fails in the room is worse than no code: the diner has already committed to trying.

Size. Roughly one tenth of the scanning distance. A table card read from 30 cm needs about 3 cm of code; a window poster read from two metres needs 20 cm.
The quiet zone. The clear margin around the code is part of the code: Denso Wave, the company that invented the QR code, specifies a four-module quiet zone in its printing guidance. A design that crowds that margin with a border or a logo is the single most common reason a scan fails.
Contrast. Dark code, light background, and real separation between them. Reversing it (light on a dark card) defeats many phone cameras outright, and elegant mid-tones lose their edge under warm restaurant lighting.
The finish. Matte beats gloss on a printed card. Gloss throws glare straight back into the lens.

Our own free QR generator refuses to produce a code whose colour is too pale to survive print, rather than letting you find out after a hundred cards are cut.

Making one you can actually put on a table tonight

The menu already exists: in a spreadsheet, in a folder of photos, on the board above the pass. So this is an evening's work, not a project.

Import the sheet. Prices, categories and item names come across in one upload; photos are compressed for you. Item names can be written in Bahasa Indonesia.
Pick a layout. Twelve of them, and the choice is about how your food photographs, not about features.
Set the options. Required choices, limits, and add-ons with their own prices.
Print the table pack. One code per table, laid out ready for the printer, so the whole room goes live at once rather than table by table.

From there the menu is a live page rather than a file. Change a price at four o'clock and the page has changed by four minutes past, on every table, with no reprint.

What it does not do, stated plainly

Customers do not pay on the page. Money changes hands at the table or the door, in cash or on a card machine. That is deliberate, and it means no card details exist anywhere in the system. If you need payment collected at the moment of ordering, this is the wrong tool and you should stop reading here.

Tax documents are built around the UAE's 5% VAT; outside it, documents issue without tax applied, so anything an Indonesian operator owes stays between them and their accountant.

The interface is English today. Your dish names, descriptions and prices are yours and display exactly as you write them.

Then the table starts earning

Once ordering runs through your own page, the things that were impossible on a PDF become ordinary. A loyalty stamping system counts on its own (per order, per rupiah, or per qualifying dish) and tiers discount a regular automatically at checkout without a code being typed. Scanning the table code again on a later visit can earn a reward. Group orders let a table of eight each add their own dishes from their own phone and arrive as one bill.

And because the order came to you rather than through a marketplace taking 20% to 30% of it, the customer is yours to message. Messages go out inside a sending window of 10:00 to 21:00 in your own local time, with a weekly cap per person, so being reachable never turns into being a nuisance.

A trial runs 15 days with no card required, which is enough to print one code, put it on one table, and watch what a real diner does with it. The full QR code menu guide goes deeper on the mechanics.

Frequently asked questions

Is a qr code restoran free to make?

The code itself is free, and a qr code menu restoran setup should never charge you just to keep the square of card alive. It encodes your web address and nothing else. What costs money is the ordering page behind it. Be careful with generators that route the code through their own domain: if that service disappears, so does every printed card you paid to laminate.

Will my QR code stop working later?

Not if it encodes your own address directly, which is how ours works: nothing sits in the middle, so it keeps working as long as the page it points to exists. That is also the reason to point it at a page you control rather than at a temporary link.

Can a QR code take an order by itself?

No. A QR code only opens a link. If that link is a PDF, the diner gets a picture of your menu; if it is an ordering page, they can order from the table and the kitchen receives it with the table number attached. The card is identical in both cases.

What size should I print it?

About one tenth of the distance it will be scanned from (roughly 3 cm for a table card, 20 cm for a window poster) and leave a clear white margin around it, because that margin is part of the code.

Does each table need its own code?

For dine-in, yes, and it is the point: a table-specific code makes the table the address, so the kitchen ticket knows where the food is going without anyone typing or repeating a number. The print pack produces one per table in a single file.