A busy Friday has one queue at the counter and one waiter walking back to it between every table. This turns the phone already in their apron into a second till — the order goes in at the table, the kitchen has it before they walk away, and the bill settles where the guest is sitting.
Free download · signs in to your existing workspace · retail counter or restaurant floor, one app
Dining Room · 4 covers
The walk back to the terminal is the part that disappears.
You don't choose an app. You choose a register, and the app follows — because a venue with a counter and a dining room shouldn't have to install twice.
You get the floor: tables laid out by section, coloured by what's happening, each open tab showing what it's run up to. Tap a table to open or pick up its order.
You get the till: scan or tap items into a cart, take payment, print or email the receipt. Hold a cart when someone forgets their wallet and pick it up on any device.
A phone can run the counter at lunch and the dining room at dinner. Switching is changing register — not reinstalling, and not a second login.
The old loop is: take the order on paper, walk to the terminal, key it in, hope you read your own handwriting. Every one of those steps is somewhere an order goes wrong, and the walk is the slowest part of a shift.
Here the order is typed where the guest is sitting. One tap sends it, and each item goes to the station that actually cooks it — the grill's items to the grill, the drinks to the bar. Send again later for the second round; only the new items go.
Items already away are locked. You can't quietly change a quantity that is on the pass, because the ticket in the kitchen wouldn't change with it — and a bill that disagrees with what was cooked is an argument at the end of the meal.
And if a station's printer is out of paper, the app says so. It doesn't tell you the order went through. A ticket everyone believes was sent is worse than one that obviously wasn't.
2 tickets cooking
The floor shows what's free, what's occupied and what's booked in the next couple of hours. Seating a booking opens its tab with the party size already on it, so seating and taking the first drinks order are one motion.
The menu with photos, categories and search. Items that need a choice ask for it — size, doneness, extras — and won't let you send "a steak" without saying how it's cooked, because the kitchen can't guess.
One tap routes each item to the station that cooks it and prints its ticket. Send again after the mains; only the new items go, so nothing is cooked twice.
Cash, card, split or something else, with change worked out as you type what they handed you. The receipt is emailed before you've walked away.
A QR order from the table lands on the kitchen board badged New for staff to glance at and send. It never goes to the kitchen without a human seeing it.
Every ticket carries a timer that turns amber, then red. The board is the thing that tells you table nine has been waiting nineteen minutes before table nine does.
This is the difference between a phone ordering app and a phone till. A sale taken at a table goes through the identical checkout your counter uses: it relieves the same stock, costs at the same FIFO or average basis, applies the same tax rules and takes the next receipt number in the same sequence.
So there is nothing to reconcile at the end of the night. No export, no second set of numbers, no "the app says one thing and the till says another". The day's takings are one figure because there is one system.
The same is true of stock. A dish sold from a phone depletes its ingredients exactly as one sold at the counter does — which is the only way a stock figure stays worth looking at.
Will go through automatically
Cafe wifi, a basement dining room, a market stall on mobile data. The sale is saved on the device and goes through when signal comes back — and lands once, not twice.
Taking orders, refunding, and clearing kitchen tickets are different rights. A chef who only clears tickets opens straight onto the kitchen board and can't take payment.
Sign in once. After that it's a thumb, and it re-locks if the phone is left face-up on a counter for a minute — because this app can take money and give it back.
For a retail counter, scanning is the fast path and the phone already has it. Bluetooth and USB scanners work too, and you can always just type the code.
Properly set, not machine-substituted — switchable from the top bar rather than buried in settings, so a waiter who lands in the wrong language fixes it in one tap.
If a station's printer didn't take the ticket, it tells you which one. Software that reports success it can't verify is how an order gets forgotten.
The honest status. The app is built and running against a real venue's menu, tables and open tabs — what's still ahead is the store paperwork, not the software.
| Platform | Status | How to get it |
|---|---|---|
| Androidio.backoffice.pos | Early access opening | Get on the list → |
| iOSiPhone & iPad | Coming soon | Get the TestFlight invite → |
| Browseravailable now | Live | The full till, floor and kitchen display run at app.bo.ge |
The kitchen display works on any tablet browser today — the phone app adds the camera scanner and the offline queue, which a browser can't give us.
No, and that's the whole point. A sale taken on a phone runs through the same checkout as your counter — same stock relief, same costing, same tax, same receipt number sequence. One system, one set of takings.
No. One download. The register you sign into decides which half you get, so a venue with a counter and a dining room installs once — and a phone can be a till at lunch and a waiter pad at dinner.
The Point of Sale app, with at least one register. For restaurant mode you'll also want your tables and, if you use them, your prep stations and their printers.
You keep taking money. Sales are saved on the device and go through when signal returns, and each carries a key the server checks so an interrupted sale charges exactly once. Refunds are the deliberate exception — they wait for someone to confirm, because money going back out should never replay on its own.
Yes. Taking orders, refunding and clearing kitchen tickets are three separate permissions, and the server enforces them regardless of what any app shows.
Not unless you want one. Tickets print to your prep stations as before. If you'd like a screen, the same app on a spare tablet is one — with wait timers and per-station bumping — at no extra cost.
The download is free and there's no separate mobile seat — it's your normal plan. See pricing.
Tell us your workspace, whether you're a counter, a dining room or both, and how many people are on the floor. We'll put you on the first Android track and set your tables and prep stations up with you.