Customers, udhaar & loyalty
Keep customer records, chase udhaar, run a khata ledger, give loyalty points, and share a customer portal — in plain language.
Every shop runs on regulars — the ones who buy on udhaar, the ones you give a little something back to, the ones whose repair you're holding behind the counter. This page shows you how Ezvento keeps track of all of them: their details, what they owe, their points, and a link you can share with them.
Where things live: everything a customer owes you is on one page, Daily → Udhaar / Khata — a Dues tab and an Instalment plans tab. Customers and Service (repairs) are under People. Loyalty is switched on in Settings → Loyalty. This guide tells you the exact name to tap each time.
Keep your customers on file
Go to People → Customers to see everyone you've saved, and to add a new one.
For each customer you can keep:
- Name and phone — the basics. Phone is how you'll reach them for reminders.
- GSTIN — their GST number, if they're a business buying from you. Ezvento checks the number is valid (it runs the official checksum) so a typo doesn't slip through. A saved GSTIN is what lets you raise a proper B2B bill for them — see GST & tax.
- State — needed so GST is worked out correctly on their bills.
- Credit limit — the most udhaar you're willing to let them run up. Set it per customer.
- Opening balance — udhaar they already owed you on the day you started using Ezvento, with the date it is as of. It is added to what they owe, shows under Dues, and is the first thing a repayment clears. You can correct the figure later, but not below what has already been paid against it.
- Loyalty — their points balance builds up on its own once loyalty is on (more below).
Deleting a customer just hides them — their record isn't wiped out. Old bills and history stay intact, so your accounts still add up. You simply won't see them in the everyday list.
Privacy note: when someone opens a customer's detail page, Ezvento quietly logs that it was viewed. This is on purpose — a customer's phone and dues are personal, and the access log is there to protect them.
How "what they owe" is counted. A customer's udhaar is the unpaid amount across their credit bills (including part-paid and EMI bills), plus any opening balance you entered for them. An instalment plan for a bill is that same money on a schedule, not extra. Only a plan for a separate amount is money on top, and it is shown on the Instalment plans tab, not in the Dues total.
Chase your udhaar — the Dues list
Open Daily → Udhaar / Khata (it opens on the Dues tab) to see who owes you money, oldest debts first. It's an aging report — Ezvento sorts every outstanding amount into buckets by how long it's been pending:
- 0–30 days — recent, no worry yet
- 31–60 days — worth a gentle nudge
- 61–90 days — chase properly
- 90+ days — the ones that need real attention
From here you can:
- Record a payment — when a customer pays back some or all of their udhaar, tap Record payment, enter the amount and how they paid. It comes off their oldest bills first, and cash goes into the open shift's cash drawer. A cashier can do the same from the till's Dues screen.
- Send an email reminder to a customer.
- Log a follow-up — note that you called or visited, so you remember where you left off.
- Open a WhatsApp reminder — this opens a wa.me chat with a ready message so you can read it and hit send yourself. (It doesn't send silently in your name; you're always the one who presses send.)
Instalment plans (EMI)
Open Daily → Udhaar / Khata and tap the Instalment plans tab. This is for money a customer pays back in fixed instalments on set dates. (What you are paying a supplier in instalments is kept separately, under Vendors → Instalment plans to pay.)
You can create a plan, open it to see the schedule and record a payment, edit its note and the dates still to come, and delete it. A plan for a separate amount can be deleted only while nothing has been paid on it.
A plan is interest-free — no extra charge is added on top. For each one you get a live repayment schedule: how much is due, and when. As payments come in, Ezvento applies them oldest installment first, and once the whole thing is cleared, the khata closes on its own — you don't have to shut it manually.
A plan can be for a bill, or a separate amount.
- For a bill — a sale made on EMI at the till gets its plan automatically. You can also turn any unpaid credit bill into instalments: tap New instalment plan, pick the customer, and choose the bill. The plan only spreads that bill's due over dates — it does not add to what the customer owes. A payment recorded on the plan goes on the bill, so the customer's dues go down too. Deleting such a plan removes only the schedule; the bill stays under Dues.
- A separate amount — money owed that is not on any bill (a hand loan, an old balance). This is an extra debt, counted on top of the customer's bills.
Loyalty points — give a little back
Loyalty is simple points, no tiers, no complicated levels. A customer spends, they earn points, and they can knock those points off a future bill.
You turn it on and set the numbers in Settings → Loyalty:
- Points earned per ₹100 spent — how fast points build up.
- ₹ value of one point — what each point is worth when redeemed.
- Minimum points before they can redeem — so tiny balances don't get used up straight away.
Once it's on, customers earn points on every bill automatically, and they redeem at checkout in the full register (pick the customer, apply their points). See Billing & payments for redeeming at the till, and Settings for the setup screen.
Honest notes on loyalty:
- There's no screen yet to hand-adjust a customer's points — you can't manually add or knock off points to fix a one-off. Points move only through billing and redemption.
- A points-expiry setting exists but isn't actually enforced right now, so points don't currently lapse even if a expiry looks set. Don't promise customers their points will expire (or count on it clearing your books).
Service jobs — repairs at the counter
Open People → Service. This is a repair intake workflow — handy for electronics, mobile, watch, and similar repairs. Each job moves through clear stages:
Received → Diagnosed → In repair → Ready → Delivered
You can print a job card for each one, so the customer has a slip and you have a tag for the item on your shelf.
Honest gotcha — a service job isn't tied to a customer record. Even if the person is saved in your Customers list, the repair job doesn't link to them — so it won't show up under that customer's history, and it won't appear in their portal (below). Treat repairs as their own separate list for now.
The customer portal — a link you can share
You can give a customer a public, read-only link to their own little page. Share it by copy-link or straight to your WhatsApp. On it, they can see:
- their loyalty points,
- their outstanding (what they owe),
- their last 10 bills, and
- their repair status.
It's read-only — they can look, not change anything.
Note on turning links off: you can't revoke one customer's link on its own. The links all share one shop-wide secret, so the only way to disable a link is to rotate that secret — which switches off everyone's portal links at once. Handy in a pinch, blunt for one person.
A few things that are in the plumbing but have no screen yet
Ezvento honestly isn't hiding these — they exist under the hood but you can't use them from a screen today, so don't rely on them:
- Data export / erase for privacy requests — the machinery to hand a customer their data, or erase it, exists, but there's no button to run it yourself yet.
- Birthday greetings — there's plumbing to wish customers on their birthday, but the customer form doesn't even collect a birthday, so nothing can go out. Don't count on birthday messages reaching anyone.
Where to go next
- Taking udhaar, redeeming loyalty at the till, selling on EMI → Billing & payments
- Switching on loyalty and adding your WhatsApp key → Settings
- Saving a customer's GSTIN so their bills come out as proper B2B invoices → GST & tax
This page covers what the app actually does today. Where a feature is half-built or needs setting up first, it says so plainly rather than pretending.