What is courier management software, and who inside a network uses it?
Courier management software is the shared system a courier network uses to book, move, deliver and settle shipments, with each role seeing only its part. Unlike a shipping aggregator, which books parcels on other carriers, it runs your own counters, hubs and riders.
Think of it as one shipment record that many hands touch. A booking franchise creates it. A hub scans it into a bag and out onto a vehicle. A destination branch assigns it to a rider. The rider marks it delivered with proof, and collects cash if it is COD. Head office bills the shipper, pays the franchise its share, and remits COD. Every one of those steps adds a timestamped event to the same record.
Head office
Sets rate cards, AWB series, franchise terms and routes; sees every shipment, all COD and every settlement.
Master and booking franchises
Book shipments, print labels, collect payment from walk-in customers, and see their own commission and dues.
Hubs
Receive bags, scan shipments in and out, build connection manifests and resolve shortages or misroutes.
Delivery branches and riders
Build run sheets, deliver, capture proof, record failed attempts and deposit COD at day end.
Shippers and receivers
Track by AWB, receive WhatsApp updates, and for business clients download COD statements or use APIs.
How does AWB generation work in courier management software?
The software issues each shipment a unique AWB (air waybill) or docket number from a series that head office controls, prints it as a barcode on a label, and links every later scan to that number. No two franchises can ever issue the same one.
Networks usually choose between two patterns. Some allot a block of numbers to each franchise, which works even if a counter goes offline briefly and matches pre-printed docket stock. Others generate the next number centrally at the moment of booking, which avoids unused blocks. We support either, and flag gaps or duplicates in a daily report.
At the counter, booking takes under a minute when designed well. Staff enter the destination pincode and the system confirms whether it is serviceable and by which mode. Weight and dimensions go in, the software compares actual and volumetric weight using the divisor on your rate card, picks the chargeable weight and shows the price from the correct client or walk-in rate card, including any fuel surcharge or COD fee. Payment is taken by cash or UPI, and a label prints on a thermal printer with the AWB barcode, destination hub code and route.
Rate cards deserve their own care: zones by pincode, slabs by weight, special rates for contract clients, and different rules for documents and parcels. Keeping them as editable tables rather than code means a new client rate goes live the same day.
Manifests, bags and linehaul: keeping loads accountable
A manifest is the list of what left a location and where it is going, and in courier management software it is created by scanning, not typing. Each bag, each vehicle and each handover has one.
At the origin branch, shipments for the same destination hub are scanned into a bag. The software prints a bag tag with its own barcode and records a seal number. Bags then scan onto an outbound connection manifest for a particular vehicle, train or flight, with the vehicle number, driver name and departure time. The manifest travels with the load and exists in the system at the same moment.
At the receiving end, staff scan the bag tag first. The system compares the seal number, then expects every shipment listed inside. That is where shortages are caught at the handover where they happened, instead of days later when a customer complains.
For linehaul, the connection manifest also gives you a simple ETA board: which vehicles are in transit, which are late, and how many shipments ride on each. If your network runs its own trucks between cities, adding vehicle tracking from your GPS tracking provider makes that board live. Most small networks start with scan times alone, which already show where delays build up.
How does hub scanning work, and why does it matter so much?
Hub scanning means every shipment is scanned when it arrives (inscan) and when it leaves (outscan), so the system always knows which location last held it. Without it, a lost parcel has no last known owner.
A typical hub shift looks like this. Incoming bags are scanned and opened. Each shipment inside is scanned against the bag’s expected list; missing ones are marked short, unexpected ones are marked excess. Shipments meant for another hub are flagged as misroutes on screen, with the correct destination shown, so they go back into the right flow. Sorted shipments are scanned into new bags for onward routes, and those bags onto the next connection manifest.
Speed matters, so scanning screens are built for handheld scanners or phone cameras, big fonts, sound and vibration for errors, and no typing. Where the network drops in a large shed, scans queue on the device and upload when the signal returns, keeping their original timestamps.
Supervisors get a live hub board: bags received, shipments pending sort, excess and short items, and vehicles due. Shortages open a ticket automatically against the last location that outscanned the item, which gives your investigation team a clear starting point rather than a blame game between branches.
What should a delivery-boy app in courier management software do?
A delivery-boy app should show the rider exactly which shipments to deliver today, in a sensible order, let them call and navigate, collect COD, capture proof, and record why any delivery failed. Everything else is optional.
The day starts at the branch. A supervisor scans shipments out to a rider, building a delivery run sheet (often called a DRS). The app loads that run sheet, orders stops by pincode or locality, and shows address, phone button, COD amount and special instructions. Riders can reorder stops themselves, because they know the lanes better than any algorithm.
At each stop the rider records one of two outcomes. Delivered, with proof and any COD collected. Or not delivered, with a reason chosen from a fixed list such as customer not available, address incomplete, refused, or rescheduled at the customer’s request. The reason drives the next step automatically, whether a reattempt tomorrow, a call from the branch, or return to origin.
The app runs on budget Android phones and works through patchy coverage by storing updates and syncing later. It is published under your company’s Google Play account, and an iOS version comes from the same Flutter or React Native code if any riders use iPhones. Hindi and regional-language labels can be added where you approve the wording.
Proof of delivery that stands up when a customer disputes it
Strong proof of delivery combines several signals: a one-time code the receiver shares, a photo of the parcel at the door or of the receiver, a signature where useful, and the phone’s location and time. One signal alone is easy to question; three together rarely are.
OTP-based delivery is the strongest for high-value or COD shipments. The receiver gets the code on SMS or WhatsApp when the shipment goes out for delivery, and the rider cannot mark it delivered without entering it. For documents and low-value parcels, a photo plus the receiver’s name may be enough. You choose the rule per client or per shipment type.
The location check guards against riders marking parcels delivered from the branch. If the phone is far from the address area when delivery is marked, the system flags it for review rather than blocking the rider outright, since addresses in India are often approximate. Photos are compressed on the phone to upload over weak data, and originals stay in cloud storage for the period you decide.
All proof attaches to the shipment’s timeline, so customer care can answer “where is my parcel?” or “I never received it” in one screen, and a business client can download proof for a disputed order themselves.
How does COD reconciliation work in courier management software?
COD reconciliation matches three numbers every day: what riders should have collected, what they actually deposited, and what the network owes each shipper. Courier management software builds all three automatically from delivery events, so the branch accountant checks exceptions instead of adding up slips.
During the run, each COD delivery records the amount and how it was paid, cash or UPI. UPI collections come from your payment provider’s confirmation, so they cannot be marked paid without the money actually arriving. At day end the rider returns to the branch; the system shows the expected cash; the cashier enters or counts what was handed over; any difference is recorded as a shortfall against that rider, with the list of shipments behind it.
Branches then deposit collected cash with head office or into the bank, and the software tracks those deposits too. On the remittance cycle you agree with each shipper, it prepares a statement listing every delivered COD shipment, deductions for your charges if you net them off, and the amount to pay. Payment references are recorded so the shipper’s finance team can match them.
The reports that matter most are ageing reports: COD delivered but not yet deposited, deposited but not yet remitted, and shortfalls by rider or branch. Those three lists show where cash is sitting and for how long, which is exactly what shippers ask about.
Franchise billing, commissions and settlements
In a franchise network, courier management software must calculate who earns what on every shipment: the booking franchise, the delivery franchise, the master franchise above them, and head office. Getting this wrong, or doing it on spreadsheets, is a leading reason franchise relationships sour.
We model your actual agreements as rules. A booking franchise may keep a share of the freight on walk-in shipments. A delivery franchise may earn a fixed amount per successful delivery, more for COD, less for failed attempts. Master franchises may earn an override on everything in their region. Contract clients may be billed centrally even when a franchise picked up the parcel, with the franchise credited its pickup share.
Each franchise gets a login showing bookings, deliveries, earnings, deductions and dues in real time, plus a monthly statement they can check line by line. Head office can set credit limits: a franchise that has not deposited walk-in collections beyond its limit is stopped from booking until it clears dues. Invoices can be pushed to your accounting package; see our Tally integration options.
For wider franchise operations such as onboarding, territory mapping and audits, franchise management software can sit alongside the courier platform and share its franchise master.
Returns to origin, reattempts and other exceptions
Exceptions cost couriers more than clean deliveries, so the software should route each one automatically: reattempt, hold for collection, contact the shipper, or return to origin (RTO). Each path has a clock and an owner.
When a rider records a failed attempt, the reason decides the next move. “Customer asked for tomorrow” schedules a reattempt. “Address incomplete” sends a WhatsApp or SMS asking the receiver for details and alerts the branch. “Refused” for a COD shipment typically starts an RTO after your agreed number of attempts. Ecommerce clients often want to decide themselves, so their panel or API receives the non-delivery report and returns an instruction.
RTO shipments travel back through the same hubs with their own manifests, and the shipper sees them as a separate list with ageing. When the RTO reaches the origin, the franchise or shipper confirms receipt with a scan, closing the loop. Damaged and lost shipments open a claim record with proof and scan history attached.
A weekly exceptions report, by reason, branch and client, usually shows patterns worth fixing: one pincode with repeated address failures, one client with high refusals, one hub with frequent misroutes. That report often pays back more than any feature on the booking screen.
Tracking pages, WhatsApp updates and client APIs
Customers judge a courier by its tracking. Courier management software should publish every scan event to a public tracking page, send WhatsApp or SMS updates at key moments, and give business shippers an API so their systems stay in sync without spreadsheets.
The tracking page takes an AWB number and shows a clear timeline in plain words: booked at the origin branch, received at a named hub, out for delivery, delivered with time. We keep internal codes off the public view and show an honest expected date. The page doubles as your most visited web page, so it loads fast on mobile and links to your booking and contact pages.
WhatsApp messages go out at booking, out for delivery with the OTP, delivered, and failed attempt with a link to reschedule. They reduce “where is my parcel” calls sharply because the answer arrives before the question. See WhatsApp Business API integration for how message templates and costs work.
For ecommerce and B2B shippers, a documented API lets them create shipments, receive AWB numbers and labels, check serviceability and pull tracking events or webhooks. Clients integrated by API tend to stay longer, because switching carriers means redoing that work.
Courier management software cost in India
With BtechWaleTech, custom courier management software starts at ₹60,000 for the web platform and ₹40,000 for the delivery-boy app. The final quote depends on the size and shape of your network rather than on the number of screens.
The main cost drivers are the number of franchise levels and settlement rules, how many hubs and routes you run, per-client rate cards and surcharges, integrations with ecommerce shippers and accounting, UPI collection on delivery, and moving open shipments from an old system. A single-city network with one hub and walk-in bookings sits near the starting figures. A multi-state franchise network with hubs, API clients and weekly COD remittance sits higher.
Running costs are yours and paid directly to providers: cloud hosting, SMS and WhatsApp messages, maps if used, and payment provider charges for UPI collections, plus Google Play’s one-time US$25 registration and, if you publish on iOS, Apple’s US$99 yearly developer membership. Label printers and scanners are bought by you. Maintenance is free for two months after launch, then from ₹8,000/mo a month if you want it. For broader budgets, read custom software development cost.
How long does it take to build and roll out courier software?
Plan on 8–12 weeks to build courier management software for a first rollout, and then a staged move of branches over the following weeks. Switching an entire network in one night is how parcels get lost.
The first two weeks settle the shipment lifecycle, AWB series, rate cards, franchise rules and COD cycle on paper. Booking, labels and hub scanning come next, because everything else hangs off scan events. The delivery app, POD and COD ledger follow, then franchise settlements, tracking page, WhatsApp and client APIs.
Rollout starts with one origin branch, one hub and one delivery branch on a single route, running live shipments while the old system handles everything else. Once that route runs cleanly for a week or two, more branches join in batches. Riders and counter staff learn fastest from short video walkthroughs in Hindi or their language, sent on WhatsApp, and a supervisor at each branch who knows who to call.
Typical delays are label printer compatibility, payment provider activation for UPI collections, and agreeing franchise commission rules internally. Settling those early keeps the calendar honest.
Ownership, data protection and the legal backdrop
You own the platform outright: source code in your repository, database and backups in a cloud account opened in your name, apps under your own store accounts. At handover you receive architecture notes, admin credentials and a recorded walkthrough, and three of us know the code.
Courier data is personal data at scale: names, phone numbers, addresses, sometimes ID proofs. India’s Digital Personal Data Protection Act, 2023 applies to how it is collected and used, so we build role-based access (a franchise sees only its own shipments), encrypted storage, audit logs of who viewed or exported what, masked phone numbers on labels where you want them, and deletion rules you decide with your lawyer.
The wider legal frame for postal and courier services changed recently: the Post Office Act, 2023 came into force on 18 June 2024 and replaced the Indian Post Office Act, 1898, as reported by All India Radio’s News on AIR. What any law requires of your business is for your own lawyer to advise on; our part is to keep the records, access controls and audit trail your advisers ask for.
Courier management software across India
The building blocks are identical nationwide, but pressure points change with the region. Networks based in Delhi and Kolkata run large hubs where scan speed, bag reconciliation and misroute control decide whether the night shift finishes on time. Routes into the Northeast through Siliguri and Guwahati face longer transit and patchy coverage, so offline scanning and honest expected dates matter.
Business clusters shape demand too. Garment exporters in Tiruppur and engineering suppliers in Rajkot send steady B2B shipments where client rate cards and API bookings save time. Franchise-heavy networks across Amritsar, Raipur and Vijayawada depend on clear commission statements and credit limits. Delivery branches in cities like Madurai and Bhopal handle a lot of COD, where daily rider reconciliation stops leakages early.
Language and devices matter everywhere. Counter staff and riders work faster with Hindi, Bengali, Tamil or other labels where you approve the text, on inexpensive Android phones. All our work is remote; there is no office visit, and setup runs over WhatsApp, calls and screen sharing.
Worked example: a regional franchise network moving off spreadsheets
A hypothetical case to show how courier management software is usually phased. Picture a courier network in Punjab with a head office, one hub, eight booking franchises and four delivery branches, handling mostly documents and small parcels plus COD for a few online sellers. Bookings are on a basic desktop program, hub scanning does not exist, and COD is reconciled on paper every evening.
Phase one would cover the booking counter with AWB labels and pincode serviceability, bags and manifests, hub inscan and outscan with shortage alerts, the delivery-boy app with run sheets, OTP proof and cash or UPI COD, and a day-end COD reconciliation screen per branch. A public tracking page would sit on top. Quote lines would start at ₹60,000 for the platform and ₹40,000 for the app, with the total depending on franchise rules and data migration.
Phase two could add franchise settlements with credit limits, WhatsApp updates, an API for the online sellers, and weekly COD remittance statements. Starting with scanning and COD, rather than billing, stops the two biggest leaks first: lost parcels and missing cash.
Red flags and a checklist before you commission courier software
Walk away from any courier management software pitch that cannot show a bag being reconciled at a hub, or a rider’s COD shortfall being traced to specific shipments. Those two flows are where money and parcels go missing, and weak software hides both.
Other warning signs: a system that lets staff type AWB numbers freely instead of issuing them; delivery marked without any proof; COD recorded only as a daily total; franchise commissions calculated outside the system; data hosted on the developer’s own server with no export; full payment demanded up front.
- Shipment volume per day now and in a year, and number of branches, hubs and franchises
- Your AWB format, current series and label printer model
- Rate cards: zones, weight slabs, client-specific rates, surcharges
- Franchise commission and settlement rules, written down
- COD cycle with shippers and how branches deposit cash
- Proof-of-delivery rules by shipment type
- Clients who need API integration, and their systems
- Languages needed on counter and rider screens
Taking over from a developer who stopped halfway? Our page on rescuing an unfinished project explains how we review what exists before quoting.