Five-Stage Postal Dispatch Automation

For every batch, a notice PDF had to be fetched for each postal reference, the envelope booked with India Post, and the resulting receipt uploaded back against the correct notice. Done by hand this was roughly 165 hours of work per batch across the whole cycle, and the failure mode was silent: a receipt filed against the wrong notice looks fine until the day someone needs it. Volume made it worse rather than easier, because the same handful of steps repeated thousands of times is exactly where attention fails.

We built a single Windows application covering all five stages — Download, Prepare, Book, Collect and Return. The download stage alone replaced around 55 of those hours: on a live batch, 9,842 postal references resolved to 1,085 unique notices and were fetched in 46 seconds with no failures. That 9x gap is the heart of it — many references share one notice PDF, and the client's own export revealed which, so the naive approach would have downloaded the same document nine times over. Before anything is booked, spend-cap and volume-anomaly guards run against the prepared batch, so an unexpected size or cost stops the run rather than discovering it afterwards. On a later live batch 5,839 receipts were collected and returned against their notices, each stamped with its own real booking date rather than one blanket value. It ships as a single installer that needs no administrator rights and installs only for the user who runs it. Reliability came from treating the network as unreliable rather than assuming it would behave. On one live run, four of 5,839 uploads failed with a transport-level connection reset — not a rate limit — and would have been abandoned on first attempt; the retry logic now covers any transient failure, while the heavier throttling response stays reserved for genuine rate limiting. The uninstaller is covered by continuous integration proving it never removes documents the client has already downloaded, because the worst outcome for a tool like this is not failing to run — it is destroying work that was already done. The application is in regular production use on every batch. MassMail reports that the capacity it has freed up, and the accuracy it can now demonstrate to the firms it dispatches on behalf of, have both helped the business take on more work — which is the outcome that matters more than the hours saved.