How to stop orders and payments slipping through WhatsApp
The four gaps where orders and payments slip between the chat, the dispatch and the bill, five things to write down for every order, and a daily routine.
The order came on WhatsApp, the dispatch happened from memory, and the bill was made two days later. The payment reminder never went, because everyone thought someone else had sent it. Nothing was lost on purpose. It slipped through the gaps between people.
The four gaps
An order passes through four handovers. Each one is a place to lose it.
- Taken, but not written. The order is a chat, a voice note or a call. It is in someone's phone, not in a list.
- Written, but not dispatched on time. There is no promised date against it, so nothing looks late until the customer calls.
- Dispatched, but not billed properly. The material goes on a challan. The invoice is made later, at a rate somebody half remembers.
- Billed, but not followed up. The invoice has no due date, and collecting it is nobody's job in particular.
Five things to write down for every order
- Who ordered, and what: party, item, quantity and rate
- The date you promised
- The stage it is in today
- Who is responsible for the next step
- The invoice amount and the date the payment is due
One order, written this way, reads like this:
Order 1052. Verma and Sons, Karnal. PVC pipe 1 inch, 400 pcs at list rate. Promised 12 October. Stage: dispatched on 12 October. Next step: Sneha in accounts, payment follow-up. Invoice ₹61,250, due 11 November.
When these five sit in one list that everyone can see, there is far less need to call around and ask. The full set of columns is in the order register format.
Keep WhatsApp for talking, not for remembering
You do not have to stop taking orders on WhatsApp. Add two habits.
- Every order taken in a chat gets an order number, and the number is sent back: "Order no. 1052 noted, dispatch by 12 October."
- Every payment promise made in a chat or on a call is typed into the list as a date.
The chat stays. The memory moves to the list.
A daily routine
| When | Who | What |
|---|---|---|
| Morning | Dispatch | Read the orders promised for today and tomorrow |
| During the day | Whoever does the step | Change the stage when it changes, not at the end of the week |
| Before closing | Accounts | Check that every dispatch of the day has its invoice number against it |
| Evening | Owner | Read one summary: orders received, dispatched and stuck, and money received |
| Tuesday and Friday | Accounts | For each party past the due date, do the follow-up step that is due: a reminder, a call, or a call from the owner |
The steps and the wording are in payment follow-up without spoiling relations.
Count it for one week
Before you change anything, measure your own leak. For one week, write every order on one page as it comes: date, party, item, promised date. On Saturday, mark each line:
- went on time
- went late
- remembered only when the customer called
- billed, with a due date
- not yet billed
That page is your real picture. Do the same count a month later.
Sheet or system?
A shared Google Sheet with the five things above is a fair start, and for a firm with few open orders it may be all you need. It strains when people stop updating it from the godown or the road, and when reminders go only if someone remembers. For that stage there is our Order & Payment Tracker: the same list, with entry from the phone and reminders that go out on their days.
Before you buy anything from anyone, ask to see it working on your own orders from last month. If the demo cannot show your stages, your items and your parties, it will not fit after you pay either.
Want to see this on your own data?
Share last month of your data. We come back with a working demo. No payment for the demo.
