Dispatch

Why Dispatch Registers in Excel Lose You Money (and Clients)

A missed shipment, a wrong quantity, an unlogged delivery — here's exactly how Excel dispatch registers create errors that cost you on both sides of the ledger.

Aditi M.
Makoro contributor
Sep 26, 2025
2 min read

An Excel dispatch register feels harmless. It's free, every dispatch clerk can use it, and the numbers seem to reconcile at month-end. The reality is that Excel-based dispatch is one of the most expensive systems a growing factory can run — the costs just don't appear on any line item, which is why nobody notices until a big one lands.

Here's where the leaks happen, and how to put numbers on them.

The Missed Shipment

A dispatch gets entered in the register but never gets invoiced — or invoiced but never entered. In a spreadsheet, the two systems aren't linked. The reconciliation happens at month-end, by which time three or four shipments have slipped through. Each one is a lost invoice, often ₹30,000–₹2,00,000 of revenue that simply never gets billed. One per quarter is enough to outweigh any cost of proper software.

The Wrong Quantity

An operator types 120 cartons when 102 went out, or vice versa. The invoice goes out matching the register. The customer counts 102 on receipt, asks for a credit note for 18 cartons that never shipped, and you can't disprove the claim because your own record says 120. This category alone costs most SME factories 1–2% of dispatch value annually — invisible because it gets buried in credit notes.

The Unlogged Delivery

The goods left, the customer received them, the salesperson confirmed it on a phone call — but the register was never updated. Three weeks later, the customer hasn't been invoiced. The salesperson left, the dispatch clerk forgot. The receivable doesn't exist until someone notices, by which time the customer feels no urgency to pay.

The Client You Lose

The most expensive leak isn't financial — it's relational. A client who has to call you three times to confirm a dispatch, who receives a wrong quantity, who gets the wrong vehicle number, eventually quietly moves their volume to a vendor who has their act together. You don't lose the client in one bad incident. You lose them in twelve small ones, none of which felt material at the time.

What the Register Can't Do

No concurrency control, no validation, no audit trail, no automated invoice generation, no automatic notification to the customer. Each of those gaps is a category of error. Excel's job is calculations, not workflow — and dispatch is fundamentally a workflow problem.

Quantifying the Real Cost

Add up: missed shipments (estimate 2 per quarter × ₹75,000 = ₹6,00,000/year), wrong quantities (1.5% of dispatch value), and the client churn cost (1 lost mid-tier client a year, typically ₹15–25 lakh). For most factories doing ₹5–20 crore of dispatch annually, the leak is in the range of ₹12–35 lakh a year. The cost of proper dispatch software is a small fraction of that, and the conversation should reasonably end there.

Keep reading

All articles