Cafe point of sale: what to buy, and what it will not fix

A cafe point of sale is the software at your counter. It rings up the drink, prints the receipt and counts the day.

This guide covers three things. What to look for when you buy one. Why a cafe is genuinely harder to price than a restaurant. And which job the counter software does not do at all, which is the job of getting the same person to come back.

What a cafe point of sale is

A cafe counter is a speed problem. A customer orders, pays and leaves inside a minute or two. There is no table service, no course timing, and often no seat.

So the software is judged on a narrow thing: how many taps it takes to sell a flat white with an extra shot and an oat milk swap. Everything else is secondary. When you sit through a demo, count the taps yourself rather than listening to the feature list.

The parts worth checking:

• Modifier speed. Milk, shot count, syrup and size should be one screen, not four.
• A real offline mode. Card networks drop. A cafe cannot stop selling because the internet did.
• Fast refunds and voids. A wrong drink at 8am must not need a manager walking over.
• An honest end of day. Cash counted, card totals matched, and a figure your accountant recognises.
• Menu edits you can do yourself. Changing a price should not need a call to the supplier.

That last one is where cafe contracts quietly hurt. Ask who edits the menu, and what it costs when they do it.

Why a cafe is the hardest place to price a system for

A restaurant has a small number of large tickets. A cafe has a very large number of small ones. So anything charged as a percentage of each sale costs a cafe far more, for every dirham earned, than it costs a restaurant.

It also inverts what a mistake costs. A restaurant can absorb an occasional slow order. A cafe with six people waiting cannot, because the queue is the product. Anything that adds seconds at the counter is expensive in a way a spreadsheet does not show.

"Cafe owners ask us to make the counter faster. Then they describe the real problem, which is that they do not know who any of their regulars are. The queue was never the thing losing them money."

— Anzul Aqeel, founder of Get Menu

What people mean by a cafe pos system uk

Search for a cafe pos system uk and you get two very different products under one name.

The first is the counter software above: a screen, a drawer, a card terminal, a printer, and a monthly licence for each site. That is a real purchase with real hardware and it is usually the right one to make.

The second is an ordering layer. It has no hardware at all. It gives the shop its own ordering page, puts a code on the tables and in the window, sends order messages automatically, and remembers customers between visits. It runs beside the counter software rather than replacing it.

Most of the confusion in this market comes from suppliers of the first quietly claiming to be the second.

Cafeteria pos: the same counter, a harder deadline

A cafeteria has the cafe's problem with a worse clock. A staff canteen or a college servery does most of its trade in two narrow windows, and the queue has a hard end when the break does.

A cafeteria pos therefore lives or dies on throughput, not features. The useful move is to let people order from their own phone while they are still in the room, so the counter is not the only place an order can start.

Being honest about what that is: these are orders placed now, not orders booked for later. There is no scheduled ordering in our system, and no separate collection order type. What it does change is where the order comes from, which is enough to shorten a queue.

It also makes stock behave. Counts fall as orders arrive, and a tray that runs out greys itself out instead of disappointing the last twenty people in the line.

The eleventh coffee, and what a stamp card is worth

Coffee is the clearest repeat-purchase business on any high street. The same face, most weekdays, for years. And most cafes have no idea who those faces are.

A paper stamp card is the traditional answer and it leaks in three ways. Customers forget it, they lose it, and you learn nothing from it because the card holds no record you can read.

A digital stamp card fixes all three. The card lives in the customer's phone wallet with no app to install, using Google's own loyalty card format, so the barista does not hand out anything and the customer cannot leave it at home. Stamps can count per order, per pound spent, or only on the item you want to move. When somebody reaches 10 stamps the reward is waiting for them rather than depending on anyone remembering.

Above stamps sit tiers. A regular who keeps coming grows into a tier with its own automatic discount, applied without a code and without a conversation at the counter. Only the better discount ever applies, so two offers cannot accidentally stack.

What the ordering layer does that the counter cannot

Your counter software serves the person standing at it. Everything else needs a different tool.

• Your own ordering page. A web address that belongs to you, with your menu on it, from the first day.
• A code for the window and the tables. Printed from a designer so it suits the room, not a generic sticker.
• Messages nobody types. The customer gets a confirmation as soon as the order lands, the kitchen gets its ticket, and for delivery the rider gets a link with a map pin dropped at checkout. That is 3 messages in about 2 seconds.
• Live prices and options. Every line is priced again from the live menu at checkout, and add-ons carry their own prices and required choices.
• Stock that manages itself. Counts fall as orders come in and an item greys out at zero.
• One bill for a group. Everyone orders from their own phone and it gathers into a single bill.
• Coupons, upsells and bundles. Each with caps, exclusions and expiry dates, so an offer cannot quietly run for nine months.
• Your menu imported from a spreadsheet. You do not retype a hundred items to get started.

Payment stays deliberately simple. It is cash, or your own card machine, taken the way you take it now. There are no online payments anywhere in the system, so no card details exist in it for anyone to steal, and old order details are cleared automatically after 120 days.

On delivery, it is worth knowing what you are choosing between. UK delivery runs through a small number of large marketplaces, which is why the competition regulator examined the arrangement closely when Amazon took a stake in Deliveroo. Those marketplaces take a share of every order. Your own ordering page takes none, and the customer stays yours. Our trial runs 15 days with no card, so you can compare the two on your own numbers. Current pricing sits on the pricing page rather than in this guide, because a figure written into an article goes stale.

Frequently asked questions

Is Get Menu a cafe point of sale?

No. It does not drive a cash drawer or a card terminal and it does not do your end of day. It is the ordering, menu, stock and loyalty layer that runs beside the counter software you already have. Most cafes using it keep their existing hardware exactly as it is.

Do my customers need an app for the stamp card?

No. The card is added straight to the phone wallet that is already on the device. There is nothing to download, nothing to sign up for, and nothing for the barista to hand over.

How do customers pay if nothing is charged through the software?

They pay you the way they do today. Cash at the counter, or your own card machine. The software takes the order, sends the messages and counts the stamps. It never touches the money.

Can this work for a cafeteria or a staff canteen rather than a high street shop?

Yes. The difference it makes there is that an order can start on a phone in the room instead of only at the counter, so the line at noon is shorter. Be clear on one thing though: these are orders placed now. There is no booking a collection slot for later, because the system has no scheduled ordering.

What should I check before signing a cafe EPOS contract?

Ask for the two year total, not the monthly figure. Ask who edits the menu and what a change costs. Ask what happens to your data if you leave, and how long the notice period is. Then ask to serve a mock morning rush on the demo unit and count the taps yourself.