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 cafe: show a menu, or remember a customer?
A café does not have an average-order-value problem. It has a frequency problem, and a printed square is one of the few cheap ways to work on it.
Tanzeel ur Rehman · Co-founder, Get Menu · 2 September 2026
Twenty to eight in the morning, the queue reaches the door, and the person at the front is asking what the pão de queijo costs while four people behind them shift their weight. Nobody in that line is going to read a menu. They know what they want. The interesting question for a café is not how to show them a list. It is how to still know who they are next Tuesday.
Search for qr code cafe and two different products come back. One is a code that displays a menu, sold on the argument that it saves printing. The other is a code that takes an order and starts a customer record, sold on the argument that it changes what happens after the customer leaves.
For a restaurant with a long menu and a 40-minute sitting, the first one has obvious value. For a café where the ticket is R$ 12 and the decision was made before the customer got out of bed, showing the menu is not the bottleneck. Being remembered is.
A café's economics run on frequency rather than basket size, so anything that shifts visits per month matters far more than anything that shifts the size of a single order. Moving somebody from six visits a month to eight is worth more than persuading them to add a pastry once.
That is why the machinery that works on repeat visits is where a café should spend its attention. Stamps counted automatically (per order, per real spent, or only on the item you want to move) with nobody having to mark an order delivered for the count to register. Tiers your regulars grow into, with automatic discounts attached, so the reward applies itself instead of depending on a barista remembering a face. Rewards that expire, because an open-ended one sits unused and teaches nobody anything.
The mechanics are dull and the effect is not. A stamp card that reaches 10 stamps is a small, visible reason to walk past the other café on the corner.
Paper loyalty cards fail in the same two ways everywhere: they are forgotten at home, and they are lost. An app fixes neither, because nobody installs an application for a café they visit twice a week. That is a genuinely large ask for a R$ 12 purchase.
The workable middle is the wallet already on the phone. A loyalty card sits in Google Wallet, the no-install retail card Google documents itself, carrying the café's own colours and logo through a designer rather than a generic template, and showing a reward on the front when one is waiting. When a regular opens their wallet to pay for anything else, your card is there. Apple Wallet is built here and awaiting the certificate Apple requires before passes ship; that is worth saying plainly rather than letting somebody find out in month two.
A café can know eighty faces and nine names, and the distance between those two numbers is the whole product. You cannot message a face, and you cannot notice that one has stopped coming in. That is the thing most worth noticing, because a regular who has gone quiet is the cheapest customer anyone will ever win back.
— Anzul Aqeel, founder of Get Menu
The other thing a code can do in a café is take the order at the table. With a code generated for every table, a customer sits down, scans, and the order arrives in the kitchen's WhatsApp group with the table number attached. Nobody stands up, nobody shouts over the espresso machine, and the counter queue is left to the people who are only passing through. An auto-confirm timer covers the minutes when the kitchen is flat out and nobody can look at a screen, and the customer gets a confirmation message the moment they order.
Whether that helps depends on the room. In a café that is really a counter with three stools, it changes little. In one where people settle in with laptops and order twice more before leaving, it is the single highest-value thing on this page. Either way the operational rules stay the same. Required choices and limits the kitchen can trust mean a coffee arrives specified rather than guessed. Low-stock alerts fire before it becomes a problem, when there are eleven cheese breads left and an hour of rush to go.
Three things, and all three are cheaper to fix now than after 200 cards come back from the printer.
Whose address is inside the square, because that decides whether your cards still work if you change supplier. What the code opens on: a live qr menu rather than a document, with 57 colour themes and a font picker so the page looks like the café rather than a form. And whether the destination is right for the placement. A cafe qr code on a table should open a menu you can order from at that table. One on a takeaway cup is doing a different job entirely and should land somewhere shorter.
Payment stays at the counter (cash or the café's own card machine) and that is deliberate rather than unfinished. With nothing charged inside the page there are no card details anywhere in the system, which for a small business with a part-time team removes an entire category of risk that is otherwise somebody's responsibility forever.
The paperwork side is quieter but real: a sales dashboard by day, item and channel, an export to a spreadsheet whenever you want it, and a customer list that belongs to the café and leaves with it. Marketing runs in its own lane so it can never delay an order message, with a weekly cap per customer so nobody is pestered. On an order, 3 messages go out in about 2 seconds without anyone typing them.
Often yes, but rarely for the reason the code is sold on. At that size the menu is short and the staff know it, so the saving is not in showing prices. It is in the loyalty card, the order taken at the table without a trip to the counter, and the record of who came back. If none of those three interest you, printing squares will not change much.
No. They settle at the counter in cash or on your card machine exactly as they always did, which is why no card details are stored anywhere. The code moves the ordering, not the paying.
They count on the order itself, without anyone marking anything delivered by hand. That is the point: a loyalty scheme that depends on a busy person remembering to press something stops working at 08:00 on a Monday.
A menu upload, a printed code and two normal weeks. The trial runs 15 days with no card asked for, and the menu can come from a spreadsheet instead of being typed. Old order details are cleared automatically after 120 days, so testing leaves nothing behind you have to think about.
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.