Most billing apps are abandoned during setup, not during use. The install goes fine, then the first screen asks for a product catalogue, a tax configuration and a customer list, and a shopkeeper with a counter to run closes it and goes back to the notebook. That is a reasonable decision. Nobody should spend an evening on data entry to find out whether a tool suits them.
So do it the other way round. Make one real bill, for a real customer, with a real amount, in the first ten minutes. You will learn more about whether this works for your shop from that one bill than from an hour of configuration.
The ten minutes
- 1
Put in your shop's name
It appears at the top of every bill you give out, so it is worth typing properly rather than as an abbreviation you will want to change later.
- 2
Add one product — the thing you sell most
Name, selling price, and the unit you sell it in. If you sell rice by the kilo, choose kg now; changing units later means re-checking any stock you have already recorded.
- 3
Raise a bill for the next customer who buys it
Pick the item, set the quantity, take the money. If they paid in full, mark it paid. If it is on udhaar, add them as a customer first so the balance has a name to sit against.
- 4
Share or print it
Send it over WhatsApp, or print it if you have a thermal printer paired. This is the step that tells you whether the tool fits your counter, because it is the only one your customer sees.
What to do on day two, and what can wait a month
The setup that matters is the setup that changes a number you will later rely on. Everything else is tidying, and tidying can happen whenever you have a quiet afternoon.
| Do it early | Why it cannot wait |
|---|---|
| Cost price on your main items | Without it, every profit figure the app shows you is blank or wrong. It is the single most valuable field in the product record. |
| The unit each item is sold in | Changing kg to piece later invalidates the stock quantity you have already been recording against it. |
| Opening balances for anyone who owes you | Their khata starts from whatever you enter. Start it at zero and you have quietly written off what they already owe. |
| Your own staff logins | If someone else is billing on your account, every entry carries your name, and you lose the one thing a per-person login gives you. |
| Can wait | Why it is safe to leave |
|---|---|
| The full product catalogue | It builds itself as you sell. A list typed up front is also a list that contains things you have not stocked in a year. |
| Categories | Useful for reporting once you have enough products to need grouping. Meaningless with eleven items. |
| Low-stock thresholds | Worth setting once you know what actually runs out. Guessing at them on day one produces alerts you learn to ignore. |
| Your logo on the bill | Genuinely cosmetic. Nobody has ever stopped buying because a receipt lacked a logo. |
The mistake worth avoiding on the first day
Entering the MRP instead of your own price. It feels more correct — it is the official number, after all — but if you routinely sell below it, every bill then needs a discount at the counter, and two things go wrong. Your margin reporting compares your cost against a price you never charge, and your discount report fills up with give-aways that were never really discounts. Enter what you charge. If you genuinely do sell at MRP, then MRP is what you charge, and there is no conflict.
The first bill is not a test of the software. It is a test of whether the software gets out of the way while a customer is waiting.
If it took more than a couple of minutes with somebody standing at the counter, that is worth knowing early. A billing app that is slower than your notebook at the busiest hour of the day will be abandoned by the end of the month, however good its reports are.