Courier & Parcel Tracking
Booking, bilty, delivery status and COD reconciliation — because the money owed to shippers is the part that actually breaks.
A local courier company can get the parcels right and still fail at the money. Cash on delivery is collected by a rider in Faisalabad, deposited the next day minus his expenses, and owed back to an online seller who is waiting on it to buy more stock. Between the collection and the payout sit undelivered parcels, returns, part-paid consignments and a rider's own account — and that reconciliation, done manually across a few thousand parcels a month, is where trust in a courier is won or lost.
So what gets built leads with COD and the bilty, not with maps: a booking that produces a tracking number and a printed bilty, scan points through the network, a delivery or return outcome per parcel, and a shipper account where COD collected, freight charged and returns all net off into one payable figure with a statement behind it.
What it fixes
- COD collected by riders and reconciled manually, so what a shipper is owed is an estimate until someone sits down with the sheets
- Parcel status known only by phoning the destination office, which means the customer-care desk cannot answer a tracking query
- Returns and undelivered parcels drifting without a decision, sitting in a corner of the office while the shipper assumes they were delivered
- Freight charged by weight and destination, with fuel surcharge and COD service charge applied inconsistently per shipper contract
- Rider accounts — parcels out, delivered, cash collected, cash deposited — tracked in a notebook, which is where shortages hide
- No proof of delivery beyond the rider's word, so a disputed delivery cannot be settled
- Shipper statements compiled by hand at month end, each one queried, each query taking an afternoon to answer
What gets built
A starting point, not a fixed list. The build is scoped to your own process before anything is written.
Booking and bilty
Consignment booked with shipper, consignee, weight, pieces, destination, COD amount and service type, producing a tracking number and a printed bilty with a barcode. Bulk booking by import for e-commerce shippers.
Scan points and tracking
Status updated at each handover — booked, received at origin, in transit, arrived at destination, out for delivery, delivered, returned — so a tracking query is answered from a screen rather than a phone call to another city.
COD collection and reconciliation
COD collected per parcel against the rider, deposits recorded, and a shipper account where collected COD less freight, service charge and return charges nets to a payable figure with a line-by-line statement behind it.
Rider and branch accounts
Parcels assigned out, delivery outcomes, cash collected against cash deposited per rider and per branch, with shortages visible the same day rather than at month end.
Returns and RTO handling
Failed delivery reasons, re-attempt rules, and a return-to-origin flow with its own charge and a hand-back record, so a return is a closed transaction rather than a parcel in a corner.
Tariff and proof of delivery
Weight-slab and zone-wise rates per shipper contract with surcharges, and a delivery record with receiver name, signature or photograph to settle disputes.
Who this is for
Local and regional courier companies and last-mile delivery operators running their own branches and riders, from roughly a few hundred parcels a day upwards, especially where COD for e-commerce sellers is a large part of the volume. It also suits goods transport operators who work on bilty and party accounts. A single rider doing local same-city deliveries for a handful of shops does not need this; a WhatsApp group and a cash book covers it. If you are purely a franchise booking agent for a national courier working inside their system, this is not your build — you are living on their tracking and their reconciliation.
Questions
Can shippers track and get statements themselves?
Yes, and it is usually the feature that wins you business, because the queries that currently flood your customer-care desk are mostly shippers checking status and chasing COD. A shipper portal with live status and a running COD statement moves that load off your staff. It does mean your numbers are visible to shippers immediately, so the reconciliation has to be right — which is an argument for getting the COD accounting correct before opening the portal.
Can it integrate with Daraz or a shipper's online store?
With a shipper running Shopify, WooCommerce or similar, an integration that pushes orders in and statuses back is practical and well worth it at volume. Marketplace integrations depend entirely on what that marketplace currently exposes and on their approval, which is outside our control and changes without notice. Treat each integration as its own scoped piece of work with its own timeline, not as a line item that comes free with the system.
Will this work when our branches have poor connectivity?
It has to be designed for it, and that is a decision to make at the start. Scanning that requires a live connection at every branch will fail in practice, so scans need to queue on the device and sync when the connection returns — which means accepting that a parcel's status may be a few minutes behind at the worst-connected branch. If your branches are routinely offline for hours rather than minutes, say so, because that pushes the design further and costs more.
Tell us how your courier company runs.
We scope it first — what it takes, how long, what it costs. No obligation.