Four disciplines that cover a café from the first coffee to the closing count. Nothing decorative — every screen exists because a service needs it.
Build the card once, change a price in a second. Categories keep a long menu legible on a small screen during a rush.
Food, drinks and desserts as filter tabs — the server never scrolls past what they need.
Shoot an item, pick from the gallery, or use the bundled dish library.
Take an item off the card with one switch when the kitchen runs out.
MAD, EUR, USD and more — applied consistently across app and receipts.
A card a new server can read on their first shift.
Tap to build, submit to fire. Each ticket carries its table, its payment method and the server who owns it.
Assign a table number, or mark the ticket for the counter.
"No sugar", "extra hot" — attached to the line, printed on the ticket.
Pending → ready → served, advanced by the server who owns the order.
Orders are written locally first and reconciled when the network returns.
No ticket lost, even when the router is.
Owners hold the accounts. Servers hold a code. Nobody shares a password, and every order stays attributable.
Generate an eight-character code per server — no email, no password to forget.
A server sees the menu and their own orders. Nothing else.
Retire a server without erasing the history attached to their name.
Each establishment's data is separated at the database level.
Accountability without friction at the terminal.
Print it, share it, then read what it all adds up to — by day, by server, by item.
Bluetooth ESC/POS with your logo on the ticket header.
Share the exact same ticket over any messaging app.
Hour, day or month buckets — scrub the chart to read any point.
Cash against card, as a share of the day's take.
Closing the till becomes reading a number, not rebuilding it.