Courier Management Software: What It Actually Fixes (and What It Doesn’t)

A few months ago I sat with the operations head of a mid-sized courier company. It was 7:40 in the evening. Three riders still hadn’t deposited their COD cash, a merchant was calling about a parcel marked “out for delivery” since Tuesday, and someone was scrolling a WhatsApp group trying to find a photo of a signed delivery slip.

None of this was unusual for them. That was the problem.

If you’re currently using Excel, WhatsApp plus lots of phone calls to manage your courier business then this is probably something you’ll already be familiar with. Discover how courier management software can help, where it will make the biggest difference, and things to look out for when choosing a system.

So what is it, really?

One system to keep track of your parcels from the point they are booked, right through to when you get your money (or return). Booking, collection, scanning at our hubs, line haul, last mile delivery, proof of delivery, COD and billing. All staff, whether at the counter, on the road or your accountant will see the same information.

That sounds simple, and the idea is. Getting a team of forty riders to actually use it is the hard part.

The stuff that hurts most without it

The biggest one is the “where’s my parcel?” call. One client of ours had two people doing nothing but answering these calls. They would call the hub, the hub would call the rider, and the rider would call back twenty minutes later, if at all. Once customers got an SMS with a tracking link at each stage, those calls dropped by more than half within a month. Nobody had to be told to stop calling. They just didn’t need to anymore.

The second is cash. COD is where courier companies quietly lose money. A rider collects ₹18,400, deposits ₹17,900, and says two customers paid online. Maybe they did. Without a system that ties every rupee to a delivered AWB, you’re relying on trust and memory, and both run out by the end of the month.

The third is lost parcels. They can be mis-sorted into the wrong bag, wrong shelf or wrong van to another hub. If everything is scanned during handover you know where and by whom the parcel was last touched. That alone settles most arguments.

Features that matter (and a few that don’t)

Every vendor will show you a long feature list. In my experience, these are the ones that decide whether the system works for you:

The rider app. This matters more than anything else. If it’s slow, confusing, or useless without a network, riders will go back to paper within a week. Test it on a ₹7,000 Android phone in a basement parking lot, not on the salesperson’s iPhone. It needs OTP or photo proof of delivery, proper failed-delivery reasons, and COD capture.

Hub scanning. Inbound scan, bagging, manifest, outbound scan. It’s boring, and it’s what keeps parcels from going missing.

COD reconciliation. You should be able to see, rider by rider, what was collected, what was deposited, and what’s short, every evening and not at month end. Merchant payouts should come straight from that.

Rate cards. Your big e-commerce client and the walk-in customer don’t pay the same. Zone, weight slab, volumetric weight, fuel surcharge, COD charge: if you can’t set these up yourself, you’ll be raising support tickets forever.

An API. If you serve online sellers, they’ll want to push orders automatically. No API means manual uploads, and manual uploads mean mistakes.

Some features look great in a demo and get little use. Fancy AI route optimisation is a good example. In dense Indian cities, your experienced riders already know which lane floods and which society guard won’t let them in. Basic area-wise grouping usually gets you 80% of the benefit.

SaaS, custom, or ERP-based?

Most companies end up choosing between three options.

SaaS courier platforms are quick to start with. You’ll be live in a week or two. The catch is per-shipment pricing, which feels cheap at 500 parcels a day and very different at 15,000. You also work the way the product works, not the way you work.

Custom builds fit perfectly on day one. After that you’re paying a development team indefinitely, and if your lead developer leaves, a lot of knowledge leaves with them.

The third option is building on an open-source ERP like ERPNext. We’ve done a few of these, and it’s the route I lean towards for companies past a certain size. Your courier operations sit right next to accounting, rider payroll, vehicle maintenance, and expenses, so your accounts team isn’t re-entering COD figures into Tally every week. You own the data, there’s no per-parcel licence fee, and you can still customise the parts that make your business different.

It isn’t the right answer for everyone. A three-rider local operation probably doesn’t need an ERP. A company with multiple hubs and a messy COD book probably does.

Before you sign anything

A few honest questions to ask any vendor, including us:

What happens to the rider app when there’s no network?
Can I change a rate card myself, today, without calling you?
How does COD reconciliation actually work? Show me with real numbers.
What will this cost me at five times my current volume?
If I leave, can I take all my data with me?
Then run a pilot. Pick one hub and five or six riders and run it for two weeks. You’ll learn more from one rider complaining that the “Delivered” button is too small than from any demo.