There is a pattern we see often enough to predict it. A shop buys new billing software. It demos well. Three months later the staff have quietly gone back to the old system, or they keep a parallel register, and the owner cannot understand why.
Almost always, the new system is slower per bill than the old one. Not dramatically. Four or five seconds. That is enough.
The arithmetic nobody does before buying
Four extra seconds per bill, two hundred bills a day, is roughly thirteen minutes. That sounds tolerable written down. It is not tolerable when it lands entirely inside the ninety minutes of the day when there is a queue, and the person absorbing it is the one being shouted at.
Staff do not reject software because it is unfamiliar. They reject it because it makes a hard part of their day harder, and they are correct to.
Where the seconds usually go
- The mouse. Any billing flow that requires moving a hand to a mouse and back has already lost. Barcode, quantity, enter, next item, with the hand never leaving the keyboard.
- Waiting for the server. Item lookup should come from memory on the till, not from a round trip to a database on a connection that is fine until it is not.
- Confirmation dialogs. A box asking "are you sure" on a routine action is an extra keystroke two hundred times a day, to prevent a mistake that happens twice a month and is easily reversed.
- Printing. Generating a PDF and sending it to a driver is much slower than sending ESC/POS commands straight to a thermal printer.
- Doing compliance work in the foreground. Registering an invoice with a remote portal while the customer waits is a design decision, and the wrong one.
How to test this before you commit
Do not watch a demo. Ask to bill fourteen mixed items, including one that needs a quantity change, one return, and a split payment between cash and UPI. Time it with a phone. Then do the same on your current system.
If the new one is slower, nothing else about it matters, because your staff will decide against it within a month and they will not tell you why.
What good looks like
The counter keeps working when the line drops, and syncs when it returns. Compliance happens behind the bill rather than in front of it. The day close reconciles against the drawer. And a new employee can be useful on it after ten minutes of being shown, because that is the actual training budget in most shops.
Read next
- → GST e-invoicing, explained from the billing counter What has to happen between pressing print and handing over the bill, and what your software must do when the government portal is slow. 5 min
- → Before you rewrite the system nobody dares touch The old software is ugly, undocumented, and the person who wrote it has gone. Replacing it is still usually the wrong first move. 5 min