Billing your shop can
actually rely on.
Invoicing, accounting, stock and GST for an Indian business - fast at the counter, correct in the books, and still working when the line drops.
- Runs on the machine you already have
- Nothing per seat, per month, for ever
- Your data, in your own database
A Kalviyogi idea · engineered by 369 Tesla at Edunivra Private Limited
What that buys you
The queue does not care that the internet is down.
Scan, bill, take cash or UPI, print. The line drops and the till keeps going - numbering from a block it reserved earlier, and sending everything exactly once when the connection returns.
The idea underneath
A balance is never stored. It is the sum of what happened.
There is no stock_quantity column in this software, and no
balance column either. Ask what is on the shelf and it adds up
the movements. That one decision is what makes two tills safe to use at
once - and it is why an outage costs you nothing.
Why it matters at the counter
Two people billing from the same shelf is normal in a busy shop. If each screen writes down what it did - sold five, sold three - the two can be merged later and both sales survive.
If instead each writes down what it thinks the total is, the second write silently replaces the first and a sale disappears with no error anywhere. You find it at stock-take, months later, and cannot explain it.
Every number this software shows you - stock on hand, what a customer owes, profit for the month - is derived the first way. See the mechanism.
What it does
The whole shop, in one program.
Not a billing app that later needs an accounts package bolted to it. The invoice, the ledger entry and the stock movement are written in the same breath, so the books and the shelf cannot drift apart.
Billing and GST
Tax invoices, bills of supply, credit and debit notes. CGST/SGST or IGST decided by place of supply, never typed by hand.
Real double entry
Every document posts a balanced voucher. The database itself refuses an unbalanced one, so the trial balance cannot be wrong.
Stock that adds up
Batches, expiry, serial numbers and warehouses. Quantity is summed from movements, so a correction is another row, never an edit.
Works offline
The till bills from a block of invoice numbers reserved for it. Two devices offline cannot mint the same number.
GST returns
GSTR-1 and 3B generated and kept as revisions, with GSTR-2B reconciliation. It never claims to have filed for you.
And the rest
TDS and TCS, multi-currency, budgets and cash forecast, quotations, projects and timesheets, a customer portal.
Four screens, one process
Everything is served by the program doing the billing.
A shop runs one thing, not five. There is no separate web server, no queue that has to be running, and no second database to keep in step.
Counter
Scan, bill, take cash or UPI, print, and take goods back against a bill.
Office
Returns, reconciliation, people and devices, and an assistant that answers questions about the business.
Customer portal
What a customer owes and every bill, reached by a revocable link rather than a login they have to remember.
The till
An app that prices the cart on the device and bills with no network at all. Installed on the counter, not visited.
Built, not described
Every number below was produced by running it.
Not estimates, and not a roadmap. These are the counts from the test suites at the last build.
Two things it deliberately cannot do: take a card payment, and file your return for you. Both need an account with somebody else, and it will not pretend otherwise. What it refuses to do.
Against what you already use
Tally, BUSY, Vyapar, Zoho Books - and where this loses.
Every one of them can write an invoice. The differences are in who holds the data, who is accountable when it breaks, and what happens when the connection drops mid-sale.
| BusinessOS | TallyPrime | BUSY | Vyapar | Zoho Books | |
|---|---|---|---|---|---|
| Runs on | Your machine or your server; Windows and Android tills | Windows desktop | Windows desktop | Android, iOS, Windows | A cloud service in the browser |
| Data lives | In your MySQL | On your machine | On your machine | On the device, with sync | On Zoho's servers |
| Priced by | Nothing per seat - it is yours | Licence | Licence by edition | Subscription | Plan and user count |
| Bills with the internet down | Yes - the whole design | Yes | Yes | Yes | No |
| Two tills offline at once | Safe by construction | LAN only | LAN only | Conflict-prone | Not applicable |
| Who is accountable when it breaks | You | You | You | You | They are |
The interesting split is not desktop against cloud. It is who is accountable when it breaks. With Zoho, they are. With the other four, you are - and in exchange nobody can change the price, the terms or the feature list underneath you.
What each one does
| Register or workflow | BusinessOS | Zoho Books | Vyapar | BUSY |
|---|---|---|---|---|
| Sales invoices, credit notes | Yes | Yes | Yes | Yes |
| Purchase bills, debit notes | Yes | Yes | Yes | Yes |
| Quotation to order to challan to invoice | Yes, each part-converts | Yes | Yes | Yes |
| Recurring invoices and expenses | Yes, with catch-up | Yes | Limited | Yes |
| Double-entry accounting | Yes, enforced by triggers | Yes | Weak | Yes |
| Budgets and cash-flow forecast | Yes | On some plans | Yes | Yes |
| TDS in both directions | Yes | Yes | No | Yes |
| Multi-currency | Yes | Yes | No | Add-on |
| Price lists - dealer, wholesale, quantity slabs | Yes, and the server picks the rate | Yes | One extra rate | Yes |
| Price floors a salesman cannot go under | Yes, refused unless approved | No | No | No |
| Bank statement import and reconciliation | Yes, by CSV | Yes | Limited | Yes |
| Automatic bank feeds | No - you import the statement yourself | Yes | No | No |
| Projects, timesheets, billing by the hour | Yes, approve then invoice | Yes | No | No |
| Customer portal - their bills and statement | Yes, a link you can withdraw | Yes | No | No |
| Your own fields, printed on the invoice | Yes | Yes | Limited | Limited |
| Invoice layouts you choose | Yes, with the statutory parts fixed | Yes | Yes | Yes |
| GSTR-1 and GSTR-3B prepared | Yes, portal JSON and CSV | Yes | Yes | Yes |
| GSTR-2B reconciliation | Yes - suggests, never decides | Yes | Yes | Yes |
| Moving in from another system | Reads a Tally or Vyapar export | Import templates | Import from Excel | Import from Tally |
| Filing the return itself | No - a person files on the portal | Yes, Zoho is a GSP | Yes | Yes |
| Card and netbanking gateway | No - UPI QR only, no merchant account | Yes | Yes | Partial |
| Amazon, Flipkart, Shopify sync | No | Yes | Yes | No |
| Loyalty points and promotions | No | Partial | Yes | No |
| Somebody to ring when it breaks | No | Yes | Yes | Yes, plus dealers |
Worth it when
- The till must keep billing when the internet stops.
- Two counters may be offline at the same moment.
- The data has to sit in a database you control.
- You need to change how the software behaves.
Not worth it when
- You want somebody else to run the servers and take the backups.
- You want the return filed for you from inside the product.
- Your accountant works in Tally, and that is the end of it.
- Nobody in reach can run a MySQL database.
Feature sets move. Every competitor row was checked against that vendor's
own published documentation - verify anything material with them before
you decide. The full write-up, including the reasoning behind each
judgement, is in docs/COMPARISON.md.
Who built it
An idea, an engineering practice, and a company.
Three names appear on this software because three different things were needed to make it, and each did a distinct job.
The idea
Kalviyogi
That a shopkeeper should not have to understand accounting to have correct books - and should never lose a sale to a dropped connection.
The engineering
369 Tesla
The build. Offline-first sync, the double-entry engine, the GST rules, and the discipline of proving each by running it rather than describing it.
The company
Edunivra Private Limited
The entity that stands behind it - who you have a relationship with, and who is answerable for the software running your books.
Open it and bill something.
The counter is the fastest way to see what this is.