Most billing software is designed for a business that makes a few large sales a day. A kirana store makes the opposite shape of business: a great many small ones, to people who will be back on Thursday.
That difference changes which features matter and which are decoration.
Speed is the whole requirement
At a kirana counter there is usually someone waiting. If billing a routine sale takes longer than writing it in a notebook, the software loses, and it loses quietly: the shopkeeper keeps the app for month-end and goes back to paper for the counter.
This is why the number of taps to complete an ordinary sale matters more than almost anything else on a feature list.
Udhaar is not a side feature here
In a lot of shops, credit is most of the relationship. The customer buys through the month and settles when they settle, and the record of that is the single most valuable thing in the business.
What matters is that the balance is tied to actual bills rather than being a running number. When someone questions a total, the useful answer is which purchases make it up, on which dates. A single figure invites an argument; an itemised statement ends one.
Half your stock is not in any catalogue
Loose goods, an item bought in for one customer, something a supplier sent that you have not listed yet. A real counter always has sales that do not correspond to a tidy product record.
Software that insists you create a product before you can bill it is software that gets abandoned in the first week. The workable pattern is to bill the item on the spot and turn it into a saved product afterwards, when there is a quiet moment.
Most kirana shops are not GST-registered, and that is fine
A large number of small shops fall below the registration requirement, and a billing app that assumes GST everywhere makes their life harder for no benefit: tax columns that do not apply, fields that cannot be filled, jargon that means nothing.
What such a shop needs is a plain bill, a parcha, with the shop name on it. And if the business later crosses the threshold and registers, the switch should be a setting rather than a migration to a different product.
The regulars problem
A kirana store's customer list is genuinely useful, unlike in trades where every customer is new. The same forty families buy the same things, and knowing who owes what and who has stopped coming is real information.
But it only becomes information if entering a customer takes two seconds. If it takes a form, the counter will bill everything to Cash Sale and the customer list will stay empty.
Stock, honestly
Full stock tracking in a kirana store is more ambitious than it sounds. Loose goods, weight-based sales and mixed units make an accurate live count hard to maintain, and a count nobody trusts is worse than no count.
The realistic version is tracking the items where it pays: the packaged goods that sell steadily and cost real money to overstock. Starting with everything is how stock tracking gets abandoned.
What to ignore
Multi-warehouse handling, elaborate purchase workflows, and dashboards with a dozen charts are not what makes a kirana counter work. They are what makes software look impressive in a demo.
The honest checklist for this trade is short: how fast is a routine bill, is udhaar tied to bills, can you sell something that is not in the list, and does it work when the internet does not.
Getting started without losing a week
The most common reason a kirana shop abandons billing software is the setup, not the software. Someone decides to enter the entire catalogue before making the first bill, gets four hours in, and never opens the app again.
The approach that actually survives is the opposite. Start billing on day one with almost nothing entered, and let the product list build itself out of what you actually sell. After two weeks the items you sell daily are all in there, and the ones you have not entered are the ones that barely sell.
The same applies to customers. Add them as they buy on credit, not in advance. A customer list built from real sales is accurate; one built from memory has forty names and twelve of them are spelled wrong.
Whatever you choose, choose it once and keep it. A shop that bills some sales in the app and some on paper ends up with two incomplete records instead of one useful one, and the month-end reconciliation between them costs more time than the billing ever saved.
How Vanij fits
Vanij runs in a simple no-GST mode for shops that are not registered, keeps udhaar tied to the bills that created it with shareable statements, and allows a one-time item at the counter that can be saved as a product later. Billing works with no connection at all.
See also five udhaar khata mistakes and shop billing software.