The ticket is in the kitchen before the waiter turns around
An order punched at the counter or on a waiter’s phone becomes a kitchen order ticket immediately. Stations get their own tickets, so the grill is not reading the fryer’s work off the same slip.
- KOT on punch, printed per station or shown on the kitchen screen
- Rounds, so a second and third order on the same table stay in sequence
- Variations and add-ons print the way the kitchen needs to read them
- Cancels and reprints are an action on the order, not a scribble on a slip
A floor plan that matches the room
Areas and tables laid out as they actually sit, with running tables showing what has been ordered, what has been served and what is still owed. A table is transferred or merged without retyping the order.
- Floor areas and dine-in tables, arranged as the restaurant is
- Running tables with the current round and the running total
- Split a bill down to the item, or merge tables onto one
- Dine-in, takeaway and delivery each taxed and printed per their order type
Open on a float, close on a Z report
The register opens against a counted float and closes against a counted drawer, with cash in and out recorded during service. The difference is on the report at midnight rather than at month end.
- Opening float counted in and attributed to the shift
- Cash in and out during service, each with a reason
- X report mid-shift, Z report to close
- Payment modes reported separately, so card and cash reconcile on their own
Regulars, points and the offer that brings them back
Customer records with order history and credit notes, points and stamps redeemed at the counter, and discounts applied by rule rather than by whoever is on the till.
- Guest records with order history and credit notes
- Points and stamps, redeemed at the counter
- Offers and discounts applied to the bill by rule
- Bills sent to the guest from the restaurant’s own WhatsApp number
Sales, items, hours and staff — exportable
What sold, when it sold, how it was paid for and who sold it, over the range you choose, in a form the accountant can take away.
- Sales and item reports over any date range
- Payment modes, so cash and card reconcile separately
- Hourly reports, which is how a rota gets decided
- Staff reports, and exports for everything
Owner, manager, cashier, waiter
Separate logins with roles that decide what each person may open and do — and, on the plans that include it, attendance and payroll in the same application as the till.
- Multiple staff logins with owner, manager, cashier and waiter roles
- Daily attendance and month sheets
- Salaries, payroll periods and payslips
- Scheduled backups and restore of the restaurant data
The full list
What is in the core, and what your licence decides.
| Module | What it does | Availability |
|---|---|---|
| Sell | Take orders, send KOTs, settle bills and print receipts | Core |
| Orders | Order history, reprint, cancel and refunds | Core |
| Menu | Categories, items, variations, add-ons, pictures and taxes | Core |
| Settings | Restaurant profile, printers, receipt layout, order types | Core |
| Tables | Floor areas, dine-in tables, running tables and rounds | Plan |
| Kitchen | Kitchen screen with live tickets per station | Plan |
| Cash register | Shifts, opening float, cash in/out, X and Z reports | Plan |
| Guests | Customer records, order history, credit notes | Plan |
| Loyalty | Points, stamps and redemption at the counter | Plan |
| Offers | Discounts and promotional offers on bills | Plan |
| Delivery integration | Swiggy and Zomato orders through the Delivery API | Plan |
| Reports | Sales, items, payment modes, hourly and staff reports with exports | Plan |
| Waiter phones | Waiters take orders on their phones over the restaurant Wi-Fi | Plan |
| Second terminal | A second counter PC sharing this restaurant over the LAN | Plan |
| Label print | Sticker and label printing for packed items | Plan |
| Packing station | A packing docket per order for the counter that bags it | Plan |
| Send bills to guests from the restaurant’s own WhatsApp number | Plan | |
| Webhooks | Post order events to BotGenius or any other service | Plan |
| Attendance and payroll | Daily attendance, month sheets, salaries, payroll periods and payslips | Plan |
| Staff and roles | Multiple staff logins with owner, manager, cashier and waiter roles | Plan |
| Backup | Scheduled backups and restore of the restaurant data | Plan |
In every licence
Sell
Take orders, send KOTs, settle bills and print receipts. This is the screen the counter lives on, and it is in every licence.
Orders
Order history with reprint, cancel and refund — so a question about a bill from an hour ago is answered at the counter rather than in a spreadsheet.
Menu
Categories, items, variations, add-ons, pictures and taxes. A variation and an add-on price correctly on the bill and print correctly on the ticket.
Settings
Restaurant profile, printers, receipt layout and order types — dine-in, takeaway and delivery each taxed and printed the way they should be.
Licensed on top
Tables
Floor areas, dine-in tables, running tables and rounds — so the floor on screen matches the floor in the room, and nobody has to remember which table ordered what.
Kitchen screen
Live tickets per station, so the grill and the fryer each see their own work instead of one printer producing a single ticket for the whole kitchen.
Waiter phones
Waiters take orders at the table on their own phones over the restaurant Wi-Fi, and the order is in the kitchen before they have walked back.
Delivery integration
Swiggy and Zomato orders arrive through the Delivery API and sit in the same queue as the counter’s, instead of on a separate tablet nobody watches.
Looking for how SmartPOS fits alongside our other software? Read the product overview on techslideits.com.
See it on your own counter.
Install it and put your own products in. Nothing to uninstall if it is not for you.