Restaurant
The kitchen does not stop when the router does.
UniPOS takes the order, sends the ticket, splits the bill and prints it on the device in front of you. Tables, guests, kitchen notes and delivery references are where the steward expects them, because your business type put them there.
- Tables and kitchen tickets
- Dine-in, takeaway, delivery
- Split and part payments
- Guest QR ordering (early access)
At the counter
Service, kitchen and counter, on the same bill.
A restaurant's software has to keep up with three different tempos at once. UniPOS carries all three without asking the steward to think about which screen they are on.
Tables and sections
Orders belong to a table, and the table carries them until the bill is settled.
Kitchen tickets
The order reaches the kitchen printer as a ticket, with the note the guest actually made.
Order types that mean something
Dine-in, takeaway, delivery and pick-up, each with the reference field it needs — a table, a token, a delivery reference.
Guest counts and kitchen notes
Recorded on the order, printed where they need to be read, and available in the report afterwards.
Split and part payments
One table, four people, three payment methods and one bill that still balances.
Guest QR ordering Early access
Guests scan the code on the table, browse your menu and order to the counter. This one needs a connection.
Menu and price control
One menu, pushed to every outlet, with prices changed once rather than on each till.
Day close that balances
Cash counted against cash expected, tender by tender, at the end of a shift that ran late.
Who this is for
Kitchens UniPOS is shaped for.
A café and a cloud kitchen bill nothing alike. UniPOS is set up for the one you run.
Cafés and casual dining
Tables, a menu, and a bill that takes seconds when the queue reaches the door.
QSR and takeaway counters
Token-based service, fast repeat orders and a counter that never waits for a server.
Cloud kitchens
Delivery-first, with references on every order and no tables to manage.
Canteens and institutional food
High volume, short menus, and a close that has to reconcile against a float.
Bakeries and sweet shops
Products sold by weight and by piece, with stock that has to keep up.
Fine dining
Table service, courses, guests per cover and a bill split however the party wants it.
Questions
What restaurant businesses ask us.
Can it print to the kitchen and the counter separately?
Yes. Kitchen tickets and customer receipts are separate prints, and UniPOS works with standard ESC/POS thermal printers on both.
Am I charged for a second billing terminal?
No. Every plan is per outlet with unlimited billing devices. A counter, a captain's tablet and a takeaway till cost the same as one till.
Does it work with delivery aggregators?
Not yet. Aggregator integrations are on the roadmap and are not something you can buy today, so please do not choose UniPOS on the strength of them. You can take delivery orders directly with a delivery reference on each one.
How does QR ordering work?
A guest scans the code at the table, sees your menu, and their order arrives on the counter. It is in early access and, unlike the rest of billing, it needs a working connection.
What happens to an open table if the tablet dies?
The order is held on the device that took it, so a dead battery is the one case worth planning around — keep the counter as the till of record for open tables during service.
See UniPOS running a restaurant business.
Half an hour, your trade on the screen, and a straight answer about whether it fits.
No card, no obligation, no automated calls.