01 · Orders and the floor
Take the order, wherever it starts.
A waiter picks the table and sends the order. Same menu, same kitchen ticket, same bill, whether it came from the floor, a room, or a takeaway counter.
Built in Nepal · IRD CBMS billing inside
One system runs your whole restaurant: kitchen, billing, stock, floor and kiosk.
Orders, kitchen tickets, IRD billing, recipes, stock and vendors in one place. Switch on the self-service kiosk whenever you want it.
- CBMS payload sent to the IRD
- Fonepay, eSewa, Khalti, cash
- Windows app or any browser
Stock
Chicken1.50 kg
Flour2.60 kg
Tea leaves120 g
It's live. Tap a dish on the kiosk and place your own order.
Orders, kitchen tickets, IRD billing, recipes, stock, purchases, vendors, tables, rooms and the kiosk. Guests pay with Fonepay, eSewa, Khalti or cash.
13%
VAT worked out on every bill, automatically
4
ways guests can pay at the kiosk
1
separate database for every restaurant
0
extra books to keep for the tax office
The path of one order
Six steps, one system.
An order enters at the table, the counter or the kiosk, and the same system carries it to the kitchen, onto the bill and out to the tax office. Here is every step it takes.
-
01 · Tap
A guest chooses a dish on the kiosk, or a waiter taps it on the floor.
-
02 · Order
The order is validated and recorded against the table, room or takeaway.
-
03 · Ticket
A kitchen order ticket is created the moment the order is placed.
-
04 · Kitchen
The printer agent on your kitchen machine sends it to your KOT printer.
-
05 · Bill
The invoice is built with the tax already worked out, and a PDF comes with it.
-
06 · Tax office
The billing module prepares the CBMS payload and sends it to the IRD.
That took you two seconds. It takes your kitchen none.
Inside STS
Every screen your restaurant runs on.
Real screens from the software, unretouched. Scroll through the modules, tap any tab to look closer, and try the small demos along the way.
02 · Kitchen
The ticket prints itself.
Every order becomes a kitchen ticket the moment it is placed. The printer agent on your kitchen machine takes it straight to your KOT printer. Status changes go back to the floor live, so nobody walks over to ask if table nine is ready.
Kitchen board · try itTap a ticket to move it along
Live order status, pushed as it changes.
03 · Billing
CBMS is not an add-on here. It is in the billing module.
Nepal wants restaurant invoices reported to the Inland Revenue Department through CBMS. STS builds the invoice, works out the tax, prepares the CBMS payload and sends it. The PDF is generated by the system. You are not keeping a second set of books.
Try the mathIllustrative
VAT 13%156.00
TotalRs 1,356.00
{
"invoice_number": "STS-2084",
"fiscal_year": "2083.084",
"taxable_sales_vat": 1200.00,
"vat": 156.00,
"total_sales": 1356.00
}
04 · Inventory
Sell a plate, lose the ingredients.
Stock moves when the kitchen moves, not when somebody remembers to write it down.
05 · Add-on module
Want guests to order themselves? Switch the kiosk on.
The self-service kiosk is a module on the same system, not a separate product. Guests pick dine-in or takeaway, choose variations and add-ons, and pay with Fonepay, eSewa, Khalti or cash. The order lands in the same queue your waiters use and prints on the same kitchen printer.
Accepted at the kiosk: Fonepay, eSewa, Khalti and cash.
Floor · pick a table
Under it
Boring where it should be boring.
Every restaurant on the system gets its own separate database. Two restaurants never see each other's data, and that separation is enforced by the database itself rather than trusted to the app. Sessions are signed and expire. Staff only reach the screens their role allows. Updates land on every screen the moment they happen.
Separate data per restaurantIsolation enforced at the database
Role-based accessSigned, expiring sessions
Live updates to every screenVersioned, reversible upgrades
Try itPick a restaurant, then send a request from any screen
Each request only ever reaches the restaurant it belongs to.
Desktop
Windows app. One file.
Download it, run it, sign in. Or use any browser if you would rather not install anything.
Questions
Questions you are about to ask.
Something else on your mind? Ask us directly.
Ask on WhatsApp01Does it make bills the tax office accepts?
The billing module talks to CBMS directly. It builds the invoice, records the tax, prepares the CBMS payload and handles the response. Invoice PDFs are generated by the system.
02Can I run two restaurants on one system?
Yes. Each one gets its own separate database. Their menus, orders and bills never touch.
03Will it work with my kitchen printer?
The KOT Printer Agent runs on your kitchen machine and talks to your printer locally, so printing does not depend on a round trip to a server far away.
04How do guests pay at the kiosk?
Fonepay, eSewa, Khalti and cash.
05Do I have to install anything?
There is a Windows app if you want one. The admin side also runs in a browser.
06Is another restaurant's data anywhere near mine?
No. Each restaurant has its own separate database, and the separation is enforced by the database itself, not just by the software.
07What does it cost?
It depends on how many terminals and which modules you want. Ask on the demo and you will get a straight number.
Next
See it running on your own menu.
Send one message. We will set up a demo with your items, your tables and your tax settings, so you are looking at your restaurant and not a sample one.
- 01Send one message
On WhatsApp or by phone.
- 02We load your menu
Your items, your tables, your tax settings.
- 03See your restaurant
Running on STS, not a sample one.
Or call +977 9862041915 · Sitoula Tech Solutions, Itahari