Operations
The credit register no software respects
Udhaar is not an edge case in Indian retail. It is a core part of how business is done, and most systems treat it as an afterthought bolted to invoicing.
Walk into most shops and there is a book. Not a ledger in the accounting sense, but a running record of who owes what, updated in pen, understood entirely by the person who keeps it. It exists in shops that have had software for years.
Why it survives
Because it does something the software does not. It records a relationship, not a transaction. It knows that this customer always settles on the fifth, that this one is good for it but slow, that this one had a bad year and the balance is being carried deliberately.
Most systems can store an outstanding amount. Far fewer make that amount visible at the counter at the moment it matters, when the customer is standing there and a decision has to be made about whether to extend more.
What a system has to get right
- Visible at the counter, not in a report. A balance that requires leaving the billing screen is a balance nobody checks during a sale.
- Part-payments without ceremony. Customers pay something on account. If that needs an accountant, it will be recorded in the book instead.
- Reminders that do not damage the relationship. A WhatsApp message with the balance is often easier for both sides than a phone call. A shop owner will not use a tool that makes a good customer feel chased.
- Ageing that reflects the trade. Thirty, sixty and ninety days is a template from somewhere else. Many trades run on a fortnightly or festival-season cycle.
The honest test
If the book is still on the counter six months after go-live, the system did not replace it. It sat beside it. And a business with two records of who owes what has, in practice, no reliable record at all.
We ask about the book in the first conversation, because it tells you more about how a shop actually runs than any feature discussion will.