A courier company with one office is a business the owner can hold in their head. Every rider is someone you hired, every merchant is someone you have met, and if a parcel goes missing you can walk to the shelf where it should be. Open a second branch in another city, and all of that ends overnight.
Multi branch courier management is a genuinely different discipline from running a single depot — and in Bangladesh, where merchants expect nationwide COD delivery, the jump from one branch to several is where most growing courier companies either build a real network or quietly bleed cash. This guide covers what changes, what breaks, and what systems you need before the second signboard goes up.
What breaks the day you open branch two
Almost every problem in a multi-branch network is a version of the same thing: information and cash now live in places the owner cannot see.
- Parcel visibility disappears. A parcel booked in Dhaka for delivery in Chattogram passes through at least two branches and one transport leg. If each branch keeps its own register, nobody can answer “where is this parcel right now?” — including you.
- COD cash sits in someone else’s drawer. The Chattogram branch collects cash for a Dhaka merchant’s parcels. That money must flow back, minus charges, on a schedule. Without a system, it flows on trust and phone calls.
- Charges drift. The new branch manager quietly quotes different delivery charges to win local merchants, and your margins become unknowable.
- Accountability blurs. When a parcel is lost between branches, each side blames the other. With paper records, both sides are right.
None of these are people problems. They are structure problems, and they have structural solutions.
The core systems of multi branch courier management
1. One shared parcel database, not one per branch
Every branch must book, receive, and update parcels in the same system, so a parcel has a single continuous timeline: booked at branch A, dispatched, received at branch B, out for delivery, delivered. Merchants and your own head office see the same live status through parcel tracking, regardless of which branch currently holds the parcel.
The moment two branches keep separate records, you no longer run one company. You run two companies that exchange bags.
2. Explicit inter-branch handovers
The transport leg between branches is where parcels vanish, because it is where responsibility changes hands. The fix is a formal handover: the sending branch creates a dispatch manifest listing every parcel in the bag, and the receiving branch scans parcels in against that manifest. Anything on the manifest that was not received is flagged the same day — not discovered three days later when a merchant calls.
Most networks in Bangladesh run a hub-and-spoke shape: regional parcels flow through a central hub (usually Dhaka) rather than every branch shipping directly to every other branch. Fewer transport legs, fewer handovers, fewer places to lose a parcel.
3. COD cash control across branches
This is the heart of it. In a COD-first market, your branches are effectively holding your merchants’ money, and the ledger must answer three questions at any moment:
- How much cash is each rider holding right now?
- How much cash is each branch holding right now?
- How much does the company owe each merchant, netted across all branches?
A centralized COD ledger makes destination-branch collections automatically credit the originating merchant’s balance, so a Dhaka merchant’s payout already includes the Chattogram deliveries — no branch-to-branch phone reconciliation. This is exactly the problem Drix COD management is built around, with rider-level settlement rolling up into branch-level and company-level cash positions.
4. Roles, permissions, and branch boundaries
Branch managers need full control of their own branch and no ability to touch another branch’s records or company-wide pricing. Head office needs read access to everything and sole authority over charge tables and merchant payout approval. Riders see only their own assignments and cash position through the rider app — see Drix rider management for how per-rider accountability works at branch scale.
Clear boundaries are not about distrust. They are what makes trust possible, because every action has a name attached.
5. Branch-level numbers, compared weekly
You cannot manage what you cannot compare. At minimum, review these per branch, per week:
| Metric | Why it matters across branches |
|---|---|
| Delivery success rate | Reveals weak local operations or bad address zones |
| Return rate | Early warning for fake orders or careless attempts |
| COD deposited vs COD collected | The number that catches cash leakage |
| Average delivery time | Merchant experience by region |
| Parcels lost in transfer | Health of your inter-branch handovers |
| Revenue vs branch cost | Whether the branch deserves to exist |
Branch comparison dashboards in Drix reports and analytics put these side by side so a slipping branch is visible in days, not quarters. For a deeper treatment of which numbers to track and target, see the courier KPIs and metrics guide.
Franchise branches change the stakes, not the system
Many Bangladeshi networks expand through franchise or commission-based branches rather than fully owned ones. The operational requirements above do not relax — they tighten, because the branch manager is now an independent businessperson whose incentives only partly align with yours. A shared system becomes the contract in action: the franchisee sees exactly what they earned, and you see exactly what they collected. The trade-offs between the two expansion models are covered in franchise vs own branch expansion.
A realistic expansion sequence
As an example sequence — not a rulebook — a company going from one branch to a small network might:
- Stabilize branch one on software first. Never expand on paper. Your first branch’s digital workflow becomes the template every new branch copies.
- Open branch two in a corridor you already serve through third-party transport, so demand is proven before rent is signed.
- Write the branch playbook — opening checklist, handover procedure, cash deposit schedule, escalation contacts — while there is only one new branch to learn from.
- Add branches only as fast as you can train managers. The limiting resource in courier expansion is trustworthy branch managers, not capital.
Running a multi-branch network on Drix
Drix is built as a multi-branch system from the ground up, not a single-depot tool with branches bolted on. Branches, hubs, inter-branch transfer manifests, branch-scoped roles, centralized charge tables, and cross-branch COD settlement are core features — and merchants get one merchant panel view of their parcels across your whole network, which is what makes your company feel like one company to them.
Because branch count and volume vary so much between networks, Drix pricing is quoted per business rather than off a rate card. Book a demo to walk through your current branch structure, or see how plans are shaped on the pricing page.
Scaling beyond one city is the most profitable move a courier company can make and the fastest way to lose control of one. The difference is almost never the cities you pick — it is whether every branch, rider, and taka lives in one system you can see from anywhere.
