From a WhatsApp message to an invoice: what has to happen in between

Retailers order the way they talk: in a hurry, in a mix of Hindi and English, with shorthand you learn over years. Turning that into a correct invoice involves more than reading it. Here is what has to happen, and where things usually go wrong.

1. Understand what the message is

Is it an order, a question about a balance, or a question about a rate? “Bhaiya balance kitna hai” is not an order and should never create one.

2. Match each item to your catalogue

“Maggi 200g” has to become the exact item in your master, with its pack size, rate and tax. Names vary — brand shorthand, spelling, a pack size left out. When the match isn't certain, the right move is to ask, not to guess.

3. Check the stock

If the retailer wants 20 and you have 14, a good draft says so and shows the quantity you can actually supply, rather than promising what isn't there.

4. Check the credit

Is this retailer already overdue? A warning at this point is cheaper than a bad debt later. It's a warning, not an automatic refusal: you may know something the system doesn't.

5. Prepare a draft

Now there is something a person can look at: the items, quantities, rates, the total, and any flags — short stock, a credit warning.

6. A person approves it

This is the step that should never be skipped. Approve, edit a quantity, or reject. Until you do, nothing has been created, no stock has moved and nothing has been sent.

7. Everything after the yes

Once approved: the order is created, the invoice and its PDF are generated, a confirmation goes back to the retailer on WhatsApp, and the order is ready for dispatch.

Why the approval matters

Software that reads messages will sometimes get one wrong. If it acts on its own, a wrong reading becomes a wrong invoice. If it drafts and waits, a wrong reading costs you a few seconds of attention. Distiqo works the second way, everywhere.