Guide · October 20, 2026

QR code ordering for a bar: how it works end to end

What the code on the bar actually does, what the guest sees from scan to collection, where the paid order goes, and what to test before doors.

What the code is, and what it is not

A QR code is a printed link. A phone camera reads it and opens a web page, and that is the whole of what the code does. There is no app to install, no account to make and nothing left behind on the phone. Everything that decides whether ordering works at your bar sits behind the code: the menu the page shows, where a paid order goes, and what the people behind the bar have in front of them when it arrives. Judge the system by those three things, not by the square of black and white.

One code for a bar is usually enough. Printing a different code for every post, rail or table is worth doing only if you want the order to carry where it was placed, and it is one more job for the morning of an event. Whatever you print, put the plain web address underneath the code as well, so a guest whose camera will not cooperate can still type it in.

The guest's side, in order

• Scan. The camera opens the menu in the phone's own browser. Nothing is downloaded and nothing is installed.
• Choose. The page shows what this venue actually sells and what is still available, because it is reading one menu rather than a printed copy of one that was true this morning.
• Name it. The guest types a name. That is the name that gets printed and the name that gets called at the counter, so it is worth asking for it plainly and letting them correct it.
• Pay. The card is already on the phone. The order only exists once the payment has gone through, which means nothing reaches a counter that has not been paid for.
• Collect. The screen tells the guest which counter has the order and what name to ask for, and they collect it there.

What happens the moment it is paid

On our side the paid order is written down before anything else is done with it. Only then is it routed: every item on the menu belongs to a counter, so the order is sorted by who makes it and each counter is sent its own part. That counter prints a ticket with the guest's name across the top and the items under it. Staff make what the paper says and put the paper with the cup, the bag or the tray it describes. An order covering two places - a drink at a bar, something hot from a grill - becomes a ticket at each, both carrying the same name, and neither counter waits on the other. Nobody carries a message down the bar, and nobody reads an order off a phone held over it.

• Because the order is recorded before it is printed, a counter that is switched off, out of paper or unplugged is a delay and not a lost order: the ticket is still waiting and comes out when the printer is back. What matters more is that somebody is told the moment a counter stops printing, rather than hearing about it from a guest standing at it.

Setting it up behind a bar

• Put the codes where people already stand still - on the bar top, the back wall, the board, the posts at the end of the rail - at eye level and large enough to scan at arm's length. A code behind a tap, below the counter edge or on a flapping banner is a code nobody uses.
• Let guests' phones use their own mobile signal, and keep your own equipment off whatever they are on. A printer belongs on a cable or on the staff network, never competing with a room full of handsets.

Then the part that is genuinely yours: name each bar the way the floor already names it, assign the items that bar makes, and put one real order through from a phone before doors - scan it, pay it, and watch it print where it belongs. A code that opens a menu proves very little on its own. A paid order that printed at the right bar, with a name legible across the counter, proves the whole path.

See it on your venue's menu

← All guides