Most shopkeepers who put off moving to a billing app are not confused by the app. They are worried about the notebook.
The register on the counter holds years of who owes what and who settled when, and no software demo addresses the actual question: what happens to all of that?
Do not migrate your history. Really.
The instinct is to start by entering the past, and it is the single most reliable way to abandon the whole project. Entering three years of old bills takes weeks, produces records nobody will ever look at, and burns all the enthusiasm before the first real benefit arrives.
Pick a date instead. From that date forward, everything goes in the app. Everything before it stays exactly where it is, in the notebook, which does not stop being valid because you got a phone.
Carry balances, not transactions
The one thing you genuinely do need to bring across is what people currently owe you. Not how it built up, just what it is today.
So for each customer with an outstanding balance, you enter one figure: the amount as of your start date. That is a short afternoon of work for most shops, rather than weeks, and it gives you a complete, usable udhaar position from day one.
If the total for someone is disputed, that is worth settling before you enter it rather than importing an argument into your new records.
Keep the notebook. Do not throw it away.
This should be obvious and often is not. The old register is your evidence for everything that happened before the switch, and it stays your evidence.
Put it somewhere safe rather than on the counter. If an old balance is ever questioned, the detail behind the opening figure you entered is in that book, and nowhere else.
The first week: bill everything, enter nothing in advance
Do not spend a week building a product catalogue before your first bill. Start billing, and let the list build out of real sales.
After a fortnight the items you sell daily are all in there, entered once each, in the natural course of work. The items you never got round to entering turn out to be the ones you barely sell, which is exactly the right answer.
The same goes for customers. Add them as they buy on credit. A list built from real transactions is accurate; one built from memory in a single sitting has names missing and names spelled three ways.
Expect to be slower for about a week
You will be. Anyone who tells you otherwise is selling something.
The first few days of any new process are slower than the thing you have done ten thousand times. What matters is whether it is faster by the end of the second week, and whether the queue moved at all in the meantime. Choose a quiet period to start, not a festival week.
Decide who else needs to know
If anyone else bills, they have to be part of this from the beginning, not told about it later.
A shop where the owner bills on the app and the helper bills on paper has two incomplete records and a reconciliation problem every evening. If it takes a day longer to start so that everyone starts together, take the day.
Some things stay on paper deliberately
Not everything needs to move. Supplier notes, reminders to yourself, the running list of what to reorder: these are fine on paper and forcing them into an app is how people conclude the app is cumbersome.
What belongs in the app is what you need to be able to search, total, or prove: sales, credit, payments, stock. The rest is your own business.
How you know it worked
The test is not whether you like the app. It is whether you stopped reaching for the notebook without deciding to.
Usually that happens the first time a customer questions a balance and you answer with an itemised statement in ten seconds instead of turning pages. That is the moment the switch is real, and it typically arrives inside the first month.
A note on backups, since paper had none
A notebook cannot be backed up, which people rarely think about until one gets wet or goes missing. A phone can, and that is a genuine improvement rather than a feature list item.
Set the backup up in the first week, while you are still paying attention, and check once that you can actually restore from it. A backup nobody has ever tested is a belief, not a backup.
How Vanij fits
Vanij lets you record an opening balance per customer so the carry-over is one figure each, bill a one-time item without creating a product first, and add customers as they appear. Billing works with no connection, so the counter is never waiting on a signal, and your data stays on your own phone rather than on our server.
See also five udhaar khata mistakes and billing for a kirana store.