Tables, not a basket
The floor is drawn as it actually stands, and an order belongs to a table until that table is settled — not to a queue of one-off sales.
A shop till rings up a basket and hands over a receipt in one motion. A bar holds a table open for an hour, splits it between the kitchen and the bar, and only settles it when the guest asks. Tabbo is built for the second kind of point of sale.
The demo opens in a few seconds. No sign-up, no card.
Every part below is built, not planned, and every part is in the demo.
The floor is drawn as it actually stands, and an order belongs to a table until that table is settled — not to a queue of one-off sales.
The waiter takes the order on their phone, at the table. Drinks and food are routed the moment they are entered, not typed in later from a notepad.
Each station sees its own tickets, oldest first — the kitchen display answers one question, what to make next.
Taking a line off, or a discount past a waiter's limit, needs a manager's PIN and stays on the record under their name.
A drink is defined down to the gram and the millilitre, so ringing one up moves the ingredients, not an abstract count of "cocktails."
One account can run several venues, each with its own floor, menu, staff and takings, switched between without signing out.
Tabbo is hospitality management software, not general retail software adapted afterwards. A shop point of sale is built around one moment: an item is scanned, a total is shown, money changes hands. Hospitality has that moment too — it is the till drawer, cash and card — but it is the last step of a much longer one. A table opens, gets a round, gets another, maybe asks for the bill twice before it means it. A point of sale for that has to hold an open account per table for as long as it takes, not just a running total per transaction.
That is the difference Tabbo is built around: the floor plan is the home screen, not a product catalogue. Everything else — the kitchen display, the recipes, the PIN on a void — exists because a bar needs it, not because a generic till happened to include it.
It runs in a browser, which means the till is whatever screen is already in the room: a phone in the waiter's pocket, a tablet at the bar, the computer in the office. Printing a bill needs an ordinary printer. A fiscal receipt needs a fiscal device, which is a separate piece of hardware — Tabbo is not a fiscal register and does not pretend to be one.
| Runs on | Any browser — phone, tablet, till computer |
|---|---|
| Setup | No installation, no engineer's visit |
| Kitchen routing | Automatic, by item, oldest ticket first |
| Fiscal receipt | Not included — a fiscal device stays separate |
| Languages | English and Serbian, on their own pages |
A shop till is built around a single transaction. This is built around a table that stays open, gets rung up piece by piece, and is settled once — with routing to the kitchen and the bar built into that, not bolted on.
No. It runs in a browser, so a phone, a tablet or an ordinary computer is enough. A printer is only needed for printing a bill, and that can be whatever printer you already have.
No. Tabbo runs orders, tables, stock and shifts. It issues no fiscal receipt and is not connected to any tax authority — in Serbia you still need an approved fiscal device alongside it.
Yes — a demo venue opens in a few seconds with no sign-up and no card, and lasts 24 hours before it is deleted.
No installation and no call with a salesperson. If you do not like it, close the tab.