Every kirana and retail counter in India runs on three unpaid jobs: chasing udhaar, guessing stock, and adding up the day after the shutter comes down. None of these jobs sell anything. All three can run themselves on WhatsApp — the app your customers already answer — while you handle the counter.
This is a practical playbook, not theory. We build automation software in Pune and the flows below are the exact ones small retailers set up first. Every script is copy-paste ready, in the Hinglish your customers actually speak.
Job 1 — Udhaar recovery, without the awkward phone call
Most khata money isn't refused — it's forgotten. The customer genuinely doesn't remember it's been three weeks. But calling them feels like an accusation, so the amount sits in the register and your working capital sits in someone else's pocket.
A polite, automatic ladder fixes the forgetting without touching the relationship:
Namaste {{name}} ji 🙏 {{store}} se — aapka ₹{{amount}} ka khata chal raha hai. Jab convenient ho, clear kar dijiyega. UPI: {{upi_id}}. Dhanyawad!
Soft nudge — "jab convenient ho" keeps it friendly{{name}} ji, chhota reminder — ₹{{amount}} pending hai {{store}} par. UPI se turant ho jayega: {{upi_link}}. Koi dikkat ho to bata dijiye, hum samajh lenge 🙏
Direct + payment link + an opening to talkNamaste {{name}} ji. ₹{{amount}} ab ek mahine se pending hai. Request hai is hafte clear kar dein, taaki aapka khata aage bhi aaram se chalta rahe. — {{owner_name}}, {{store}}
Firm but respectful — signed by the owner, not "the system"Two rules we've learned: never send more than one reminder a week to the same person, and stop the ladder the moment payment arrives — an automation that dunns someone who already paid does more damage than no automation at all. (A payment webhook from UPI/Razorpay stops the ladder automatically.)
Job 2 — The 9pm sales report you don't have to add up
If your billing runs on Vyapar, mBillBook, a POS, or even a plain Google Sheet, the day's numbers already exist digitally. The only missing piece is delivery. A scheduled flow reads the sheet or the app's export every evening and sends you one WhatsApp message:
📊 {{store}} — {{date}}
Sales: ₹{{total}} ({{bills}} bills, avg ₹{{avg}})
Cash: ₹{{cash}} · UPI: ₹{{upi}} · Udhaar diya: ₹{{credit}}
Kal se {{pct}}% {{updown}}. Top item: {{top_item}}.
The "udhaar diya today" line is the quiet hero — it makes new credit visible daily instead of surprising you at month-end. If you run more than one counter or shop, the same flow sends one combined message with a line per store. That's the Google Sheets pattern doing retail duty.
Job 3 — Low-stock alerts before the customer asks and leaves
A stock-out of your 20 fastest movers is invisible until a customer asks, hears "khatam ho gaya", and buys it next door. Track just those 20 SKUs in a sheet (most billing apps update stock counts automatically), and let a flow watch the threshold:
⚠️ Stock alert — {{item}} sirf {{qty}} bacha hai (reorder point: {{min}}). Distributor: {{dist_name}}. Reply ORDER to send the usual order.
Goes to you; one reply sends the pre-written order to your distributorThe "reply ORDER" step is an approval — the flow drafts the distributor message but a human presses go. If you work with multiple distributors on WhatsApp, the full pattern is in our distributor & wholesaler playbook — it's the same machinery from the other side of the counter.
Job 4 — Festival & win-back messages that don't feel like spam
Your billing history knows who hasn't shopped in 30+ days. A monthly flow reads that list and sends one respectful nudge — not a daily broadcast:
Namaste {{name}} ji! Kaafi din ho gaye 😊 {{store}} par is hafte {{offer}} chal raha hai. Aapke liye rakh ke bhejna ho to bata dijiye — home delivery bhi hai. 🙏
Marketing template — needs opt-in; send max once a monthBefore Diwali, the same list plus a genuine wish (sent two days before the rush, not on the day) reliably brings old faces back. Keep marketing messages rare and personal — the moment they feel like a broadcast, the block button appears. More ready-made scripts: 21 Hinglish templates.
What this actually saves
| Automation | Manual time it replaces | ₹ impact |
|---|---|---|
| Udhaar reminder ladder | 2-3 hrs/week of calls you avoid making | Weeks-old khata money moves; working capital comes home |
| 9pm sales report | 30-45 min of evening totalling | Daily visibility on credit given & UPI vs cash split |
| Low-stock alerts | Physical stock rounds | Fewer stock-outs on your top 20 SKUs = fewer lost sales |
| Monthly win-back | Doesn't happen manually at all | Lapsed customers return; festival spikes captured |
Who should NOT bother (honestly)
If you have under ~50 regular customers, barely any udhaar, and one supplier — a khata app and your own memory are genuinely enough. Automation earns its keep when the numbers grow past what one head can hold: 100+ khata customers, 300+ SKUs, two counters. Start when the pain is real, not because a blog told you to.
Setting it up without a computer degree
Each flow above is a trigger plus two or three steps. In Yantra you can type the sentence — "har somvar udhaar walon ko polite reminder bhejo aur mujhe summary do" — and Mantra builds the flow; the WhatsApp side works through the Business API (via your own Meta number or an AiSensy account). A failed run never costs a rupee.
Put the khata on autopilot this week
Start free — 1,000 runs a month. Udhaar reminder and daily report templates included.
Start free