For restaurants in Nepal
Restaurant back-office for kitchens that bill on paper
Your guests keep getting the bill you write by hand. Your staff enter the order on the phone already in their pocket, and the app builds the bill they copy out.
Everything a paper bill never records — how long table seven waited, how much rice actually left the store, who still owes you, what should be in the drawer — falls out of that by itself.
Free for your first 6 months. Runs on hardware you already own.
It is not a POS. It is the book behind the bill you already write.
The restaurant software sold here is capable, and it is billing-first: it exists to be the terminal that prints the guest's bill. If your restaurant bills by hand, that does not fit, and buying a printer and a till is not the answer to a bookkeeping problem.
Nothing about your service changes. The waiter still writes the bill. What changes is that the numbers underneath it stop disappearing.
What you know by the time the last table leaves
Which table has been waiting forty minutes
The clock starts when the first order goes to the kitchen and stops when the bill is generated. You see the tables that waited too long, not only the ones that complained about it.
The rice that left without a bill
Write your recipes once. The app compares what the kitchen should have used against what the store actually lost, item by item. That gap is the number nothing else in your restaurant shows you.
Credit with a name on it
Khata is only allowed against a registered customer who is inside their credit limit. The database itself refuses the sale otherwise — not a warning a busy waiter taps past at nine on a Friday.
Who you owe, and by when
Supplier udhaaro carries a due date, not just a running total. You can see what falls due this week before the supplier is standing in your doorway asking.
The drawer, counted every day
What should be in the drawer against what was actually counted, with the difference recorded and signed. Money you take out for yourself is recorded as your drawings, not buried inside “expenses”.
The QR money that lands tomorrow
Fonepay, eSewa and Khalti pay you the next day and keep a cut. Both the gross and the net are kept, so the day's sales and what actually reaches the bank can be made to agree.
One bill, three ways of paying
Cash, QR and khata against a single bill, recorded as one transaction, with only the cash part landing in the drawer.
A menu the guest scans at the table
Put a QR sticker on each table and the guest reads your current menu on their own phone — prices with VAT and service charge already inside, veg and non-veg marks, photos. Nothing about what a dish costs you appears on it.
A closed month that stays closed
Lock a Nepali fiscal month and the books refuse to change. A voided bill keeps the time it was billed, so a bill cancelled at midnight cannot be made to look like it never existed.
Five exports your accountant can open
Sales register, purchases, stock movements, expenses and stock on hand, as spreadsheets, carrying both the Bikram Sambat and the English dates.
A kitchen screen that keeps up on its own
An order sent from the floor appears on the kitchen rail the moment it is saved. Nobody stands there refreshing a page.
A different screen for each job
The kitchen rail carries nothing about money. Your accountant reads everything, exports it and closes the month without ever standing at the till. You see all of it, plus who changed what.
It runs on hardware you already own
The bookkeeping software itself is free
It is built to be self-hosted on a machine you already pay for, alongside whatever else that machine is doing. There is no monthly hosting bill attached to it.
Your books are separated by the database, not by good intentions
One installation can hold several restaurants, and the wall between them is enforced inside Postgres — row-level security on forty tables and forty-four composite keys — rather than by a line of code somebody has to remember to write in every new screen. A test suite signs in as one restaurant and attacks another's orders, menu and kitchen rail; it has to fail to get in before anything ships.
Copied off the machine every night, and checked before it is kept
A full copy of the database goes off the machine automatically at 4:30 every morning — after the trading night has closed, so a backup never splits one night in half. The script verifies the copy first and refuses to upload one that fails the check. A backup nobody has verified is not a backup.
Nothing to install on your staff's phones
Every screen is a web page, built for a phone held in one hand in a dim dining room, and dark by default so it is not a torch in a guest's face. No app store, no download, no device to buy.
Free for your first 6 months
The first 6 months of use cost you nothing.
After that it is paid, and the price is simple. We have not put a number on this page because we would rather agree it with you directly, once you know what the software is worth to your restaurant.
Restaurants are set up one at a time, by hand. Write to us and we will talk through how your floor runs before anything is switched on.