Ask a unit owner in Surat what their order tracking costs them and the answer is usually “nothing, we manage”. That is true in the sense that no invoice arrives for it. It is not true in the sense that matters, because the cost shows up as margin that was there when you quoted and is not there when you bank the payment.
We have spent the last several months inside weaving units, process houses and made-ups exporters between Udhna and Kim, mostly watching rather than pitching. What follows is where the money actually goes. None of it is dramatic. All of it is recoverable.
The shape of the problem
A typical 80-person unit running 40 to 60 orders a month has an order process that looks like this: an enquiry arrives on WhatsApp, a rate is agreed on a call, a rough note goes into a diary or an Excel sheet, the floor is told verbally or on a second WhatsApp group, the supervisor tracks progress in his head and on a paper slip, accounts is told when it is ready, and the invoice is typed from the delivery challan.
Every one of those steps works. The problem is that none of them are connected, so the same fact — this order, this quantity, this rate, this stage — is stored in six places, and the six places drift apart. Every gap between two of those places is where margin leaks.
Four leaks, roughly in order of size
1. Rate and quantity drift between the quote and the invoice
This is the big one and it is almost never measured. A rate is agreed at ₹186 per metre on a call. The work order gets written as ₹186. Then the buyer negotiates a four percent adjustment on a partial lot, which the partner agrees to on WhatsApp and does not write down anywhere. Accounts invoices at the original rate. The buyer short-pays. Three weeks later somebody reconstructs the conversation from a phone, and a credit note is issued.
In the units we sampled, between two and five percent of invoices had a dispute of this kind in any given quarter. The direct cost is the credit note. The indirect cost is a senior person spending half a day scrolling WhatsApp, and a payment sitting unbanked for three extra weeks.
2. The status question tax
“Where is my lot?” is the single most common message a unit receives. In the units we watched, someone in the office fielded between fifteen and forty of these a day. Each one costs a walk to the floor, a conversation with a supervisor who is in the middle of something else, and a call back.
Call it four minutes each, at thirty a day. That is two hours of an office person’s day, every day, producing nothing except a number that the system should have known. It also costs the supervisor his attention, which is the resource the whole floor actually runs on.
3. Retyping, and the errors it creates
The same quantity is keyed in four to six times: the work order, the delivery challan, the tax invoice, the e-way bill portal, the packing list for an export consignment, and Tally. Each retype is an opportunity to transpose two digits.
Most of these errors are caught. The ones that are not tend to be caught by the buyer, at the point where they are most expensive — a mismatch between the challan quantity and the invoice quantity is a routine reason for holding an entire payment, and a mismatch on the e-way bill is a reason for a vehicle to be detained.
| Document | Typed by | Consequence of an error |
|---|---|---|
| Work order | Office | Wrong quantity produced |
| Delivery challan | Dispatch | Mismatch at the buyer’s gate |
| Tax invoice | Accounts | Payment held, credit note |
| E-way bill | Accounts | Vehicle detained, penalty |
| Packing list | Export desk | Customs query, demurrage |
| Tally voucher | Accounts | Books do not reconcile |
4. Job-work that nobody is tracking
Almost every unit sends material out — to an embroidery job-worker, a process house, a specialised finisher. The goods leave on a challan and are supposed to come back. In practice, the tracking of what is outside is the weakest part of most order systems we have seen, because it lives entirely in one person’s memory.
The losses here are quiet: material that comes back short and is never reconciled, job-work bills paid against quantities nobody verified, and lots that sit at a job-worker for an extra week because nobody was chasing. Under GST there is also a compliance dimension — goods sent for job work have to come back within the prescribed period, and units that are not tracking it are frequently not tracking that either.
Why buying an ERP usually does not fix it
Most of the units we visited had already bought something. Almost none of them were using it beyond the invoicing screen. The pattern is consistent enough to be predictable:
- The software assumes a process that the floor does not follow, so following it means changing how the floor works — which does not happen during a season.
- It is in English, and the person who actually knows where the lot is does not work in English.
- It requires a desktop, and the supervisor is standing next to a machine.
- Entering the data is work for one person and the benefit accrues to another. Nobody sustains that.
- It was sold to the owner and demonstrated to the office. The floor was never in the room.
The lesson we took from this is not that units need better training. It is that any system that requires more than about three taps from the person on the floor will quietly stop being used within a month, and everything downstream of it becomes fiction.
What to fix first, if you fix nothing else
- Give every order one number, and use it everywhere. The enquiry, the work order, the challan, the invoice and the WhatsApp message to the buyer all carry the same reference. This alone kills most of the dispute resolution time, because “which lot” stops being a question.
- Write down every rate change at the moment it is agreed. Not in a chat — against the order. If the only place a four percent adjustment exists is a WhatsApp thread, you will find it three weeks later at the worst possible moment.
- Make stage completion a tap, in the supervisor’s language. Five stages, one tap each, on a phone, in Gujarati. If it takes longer than that it will not be done, and if it is not done the rest is worthless.
- Generate the invoice from the order, not from the challan. The moment a document is typed from another document rather than from the source, you have reintroduced the drift you were trying to remove.
- Track what is outside your gate. Job-work out, job-work in, expected return date. A spreadsheet is fine if it is genuinely maintained; the point is that somebody other than one person can answer the question.
The number that matters
We ask units to measure one thing before they change anything: how many days pass between goods leaving the gate and money arriving in the bank. Not the credit terms — the actual elapsed time. Most owners guess a number that is fifteen to twenty days lower than what their own ledger shows.
That gap between the believed number and the real one is where all four leaks add up. You cannot fix it by chasing payments harder, because the delay is not usually the buyer being slow. It is the invoice going out four days late, the quantity being disputed, and the credit note taking a fortnight.
Fixing the record fixes the cash cycle. That is the whole argument, and it is worth considerably more than the subscription.
Easarc Flow is what we built out of these visits. You can read what it does, or open the live demo and click around a unit’s order book without talking to anybody.