Every courier software demo looks impressive. Clean dashboards, smooth animations, a long feature list. The problem is that demos are designed to show the product at its best, and the courier software features that decide whether your operation runs smoothly at 7 pm on a Thursday — COD reconciliation under pressure, a rider app that works on a cheap Android phone in Gazipur, merchant payouts that balance to the taka — are exactly the ones a demo glosses over.
This guide lists the twelve features that actually matter for a courier business in Bangladesh, in rough order of importance, with the specific question to ask at each demo. Use it as a checklist and you will cut through marketing in under an hour per vendor.
The 12 courier software features, ranked
1. COD management and reconciliation
In Bangladesh, cash on delivery is not a feature — it is the business. Most parcels carry cash, which means your riders are walking around with your merchants’ revenue every day. The software must record every collection at the doorstep, show live cash-in-hand per rider, and reconcile rider settlements against expected collections automatically. If this module is weak, nothing else matters. See how Drix handles COD for a reference of what complete looks like.
Demo question: “Show me the screen where I find out a rider settled 2,000 taka less than he collected — how fast do I see it, and what does the audit trail show?”
2. Rider mobile app that survives real conditions
Your riders use mid-range Android phones on patchy mobile data. The app must be light, work offline and sync later, capture proof of delivery (photo, signature, or OTP), and make status updates a two-tap job. An app riders hate is an app riders will not use — and then your data is fiction. Details on what a working setup looks like: Drix rider management.
Demo question: “Open the rider app on a 10,000-taka phone with mobile data switched to 3G. Book a delivery in a dead zone and show me the sync.”
3. Merchant panel with self-service booking
Your merchants are online sellers — F-commerce pages, small shops, growing brands. They should book parcels, print labels, track deliveries, and read their payout statements without calling your office. Every call the merchant panel prevents is staff time you do not pay for.
Demo question: “Walk me through a merchant booking 30 parcels from a CSV upload, then checking why last week’s payout was what it was.”
4. Public parcel tracking
A tracking page where the end customer enters a parcel ID and sees live status. This one page removes the largest single category of inbound calls for most couriers. It should carry your branding, not the vendor’s. Reference: Drix parcel tracking.
5. Multi-branch and hub support
If you run — or plan to run — more than one branch, the system needs branch-level views, inter-branch transfer tracking, and permissions so a Khulna branch manager sees Khulna, while you see everything. Retrofitting multi-branch onto single-branch software is painful; check it exists before you need it.
6. Merchant payout automation
The system should compute what each merchant is owed — collected COD minus delivery charges minus returns — per settlement cycle, and generate the statement. Manual payout calculation is the second-biggest time sink after COD reconciliation, and errors here destroy merchant trust fastest.
7. Reports and analytics
Delivery success rate by zone, return rate by merchant, rider performance rankings, branch comparisons, COD cash flow. You are buying visibility as much as workflow. Live dashboards beat monthly spreadsheets, and the numbers must be drillable — a percentage you cannot trace to specific parcels is decoration. See Drix reports and analytics.
8. Returns workflow
Returns are a fact of COD life in Bangladesh. The software needs explicit return statuses with reasons, return-to-merchant tracking, and correct payout math when a parcel comes back. Many systems treat returns as an afterthought; your P&L does not.
9. Role-based permissions and audit logs
Who cancelled that parcel? Who edited that COD amount? In a cash business, every sensitive action needs a name and timestamp attached. This is your first line of defense against internal fraud — and an underrated feature until the day you need it badly.
10. Integrations and API
Your bigger merchants run WooCommerce or Shopify stores and will want orders flowing into your system automatically. An API and webhooks for status updates are also what let you connect SMS gateways and payment services. A closed system caps how large your merchants can grow with you.
11. Bulk operations
Booking 200 parcels one at a time is not an option during Eid season. Look for bulk import, bulk status updates, bulk label printing, and bulk assignment to riders. Speed at the hub is a feature.
12. SMS and notification controls
Automatic SMS on booking, out-for-delivery, and delivery keeps customers informed and reduces failed deliveries from unreachable receivers. Check who pays for SMS, at what rate, and whether templates are editable — telecom costs are recurring and real.
Comparison checklist
Score each vendor 0–2 on every row (0 = missing, 1 = partial, 2 = strong) during demos:
| Feature | Weight | Vendor A | Vendor B | Vendor C |
|---|---|---|---|---|
| COD management | High | |||
| Rider app quality | High | |||
| Merchant panel | High | |||
| Public tracking | High | |||
| Multi-branch support | Medium | |||
| Payout automation | Medium | |||
| Reports and analytics | Medium | |||
| Returns workflow | Medium | |||
| Permissions and audit | Medium | |||
| API and integrations | Low–Medium | |||
| Bulk operations | Low–Medium | |||
| SMS controls | Low |
Weight the high rows double when you total. A vendor that scores brilliantly on dashboards but weakly on COD and the rider app is the wrong vendor for a Bangladesh courier, whatever the demo looked like.
Beyond features: the questions that predict regret
Features get you a shortlist. These questions pick the winner:
- Who else in Bangladesh runs on this? Software built for European parcel networks often has no concept of COD-first workflows, cash settlement cycles, or bKash-era payment reality. Local operational fit beats global brand names.
- What does support look like at 8 pm during Eid rush? Get response times in writing. Your peak weeks are when software problems cost the most.
- How does onboarding work? Who migrates your merchant list and open parcels? Who trains your hub staff and riders? A great product with no onboarding plan fails at go-live.
- Can I export my data completely? Parcel history, merchant balances, everything. If leaving is impossible, every future price increase is a hostage negotiation.
- What is the real total price? Setup, SMS, support tiers, per-seat charges, volume triggers. Work through the full breakdown in our guide to courier software pricing in Bangladesh before comparing quotes.
Red flags that should end a conversation
- No live demo with your own test data — only videos or slides.
- The rider app is “coming soon” or is a mobile website pretending to be an app.
- COD reconciliation is described vaguely, or the answer to a cash-discrepancy question is “you can check the reports.”
- No audit trail on parcel edits and cash entries.
- The vendor cannot name a courier operation of your size using the product.
Any one of these is survivable. Two or more means keep looking.
How Drix measures against this list
Drix was built for exactly the operation this checklist describes: a Bangladesh courier running COD-heavy volume across one or many branches, with riders on Android phones and merchants who expect self-service. The core system covers the full high-weight list — COD management with per-rider cash tracking and settlement, a rider app designed for real network conditions, a self-service merchant panel with payout statements, branded public tracking, multi-branch permissions, and drillable reports — with API access and bulk tools for scale.
The honest way to evaluate any of that is the same way you should evaluate every vendor: a live demo against your own workflow. Bring this checklist, bring your hardest questions about cash discrepancies and Eid volume, and score what you see. Book a demo or review how Drix pricing works to start.
The bottom line
Buying courier software is not about finding the longest feature list — it is about verifying strength in the four features that carry a Bangladesh courier operation (COD, rider app, merchant panel, tracking), confirming the operational fit questions, and walking away at red flags. If you are still deciding whether you need software at all, read when Excel breaks for courier businesses first — it will tell you whether this purchase is ahead of you or overdue.
