From June to September, every courier company in Bangladesh runs a different business. Monsoon delivery is not normal delivery with occasional rain — it is waterlogged streets in Dhaka and Chattogram, ferries delayed on river routes, parcels soaked into worthless pulp, and riders navigating knee-deep water with a bag of electronics and a pocket full of COD cash.
The monsoon does not have to mean months of failed deliveries and merchant complaints. Couriers that treat the rainy season as an operating mode — with its own packaging standards, routing rules, rider policies, and customer communication — keep their success rates respectable while competitors drown in exceptions.
This guide covers the operational changes that matter: protecting parcels, planning around water, keeping riders safe, and being honest with merchants about what the rain does to timelines.
What the monsoon actually does to a courier operation
It helps to name the specific failure modes, because each has a different fix:
- Waterlogging kills routes, not the city. Dhaka does not flood evenly. Specific corridors — parts of Mirpur, Badda, Dhanmondi 27, Chattogram’s Agrabad and Muradpur — go under after an hour of heavy rain while nearby streets stay passable. Routing, not cancellation, is the answer.
- Parcels get destroyed. Cardboard and paper invoices do not survive a downpour in an open rider bag. A wet parcel is a return, a refund, and often a lost merchant.
- Riders slow down and get hurt. Wet roads mean slower, more careful riding and genuinely higher accident risk. Productivity per rider drops just as delivery attempts get harder.
- Intercity legs stretch. Ferry ghats back up, highways flood in low sections, and rural last-mile roads turn to mud — a challenge we cover more fully in our post on courier service in rural Bangladesh.
- Customers are not home, or will not come out. Doorstep handovers take longer, and “come tomorrow” failures rise.
Waterproofing: the cheapest fix with the highest return
Start with the parcel itself, because a dry parcel that arrives a day late is a minor complaint, while a soaked one is a permanent one.
- Poly-wrap at booking, not at the hub door. Make waterproof outer wrapping a standard for monsoon months. Many merchants will do it themselves if you tell them it is required — put it in your merchant guidelines and pickup checklists.
- Waterproof rider bags. Proper rain covers or waterproof bags for every rider cost little against the value of the parcels inside. Inspect them at the start of the season, not after the first destroyed batch.
- Protect the paper. COD receipts and invoices in a soaked bag become unreadable, and unreadable paperwork becomes cash disputes. Digital proof of delivery through your app removes the paper problem entirely.
- Stage parcels off the floor. Hubs in low-lying areas flood too. Pallets and raised shelving protect the day’s throughput from a bad drainage hour.
Routing around water, not through it
The difference between a good and bad monsoon day is usually decided at morning dispatch.
Build a waterlogging map of your own zones
Your riders already know which streets go under. Capture that knowledge: list the chronic waterlogging points in each delivery zone, which rain intensity triggers them, and the workaround route. Review it each season. This is operational gold that lives in riders’ heads until someone writes it down.
Sequence deliveries by weather window
On days with forecast heavy rain, deliver the vulnerable zones early. A zone that floods by 3 PM should be a morning zone during monsoon, even if it is an afternoon zone the rest of the year. Dispatchers who assign routes with rider management tools can re-sequence zones in minutes rather than re-briefing every rider by phone.
Decide the hold rules in advance
Some days, parts of the city are simply not deliverable. Define in advance what triggers a hold — standing water above a threshold, an official weather warning — and which parcels wait versus which go out with adjusted routes. A pre-agreed rule beats a panicked argument at noon.
Rider safety and the cash problem
A rider down with an injury costs more than any day’s parcels, and pushing riders into dangerous water is both wrong and bad business.
- Issue rain gear at the start of the season and replace it when it fails.
- Slow the targets: monsoon parcels-per-day expectations should be explicitly lower than dry-season ones, so riders are not incentivised to take risks.
- Empower refusal: a rider who judges a street unsafe should be able to mark the attempt and move on without penalty.
- Shorten the cash loop: wet, chaotic days are when COD cash gets lost or miscounted. More frequent deposit checkpoints and per-parcel matching through COD management keep the cash side clean when the physical side is messy.
Communicating delays without losing merchants
Merchants can forgive weather. They cannot forgive silence.
- Adjust the promise seasonally. If inside-Dhaka delivery is normally next-day, say plainly that heavy-rain days may add a day. An honest monsoon SLA beats a broken standard one.
- Update statuses in real time. When a parcel is held for waterlogging, the status should say so within the hour. Merchants who can see “delivery attempted — area waterlogged, rescheduled” in parcel tracking do not flood your phone lines, and neither do their customers. Drix supports hold and delay reason codes on statuses precisely so a rain-delayed parcel explains itself.
- Flag affected zones proactively. A short morning notice — “deliveries in these areas may be delayed today due to waterlogging” — sent to merchants shipping into affected zones converts angry calls into informed patience.
A worked example: a heavy-rain day plan
As an illustration, consider a courier running 600 parcels a day across Dhaka when the forecast shows heavy rain from early afternoon:
| Time | Action |
|---|---|
| 7:00 | Dispatch reviews waterlogging map against forecast; flags four vulnerable zones |
| 7:30 | Vulnerable zones assigned first-run priority; riders briefed on workaround routes |
| 8:00 | Merchant notice sent for the four flagged zones |
| 13:00 | Rain begins; dispatch checks rider positions and pulls two riders off a flooding corridor |
| 14:00 | Held parcels marked with reason codes; statuses visible to merchants |
| 17:00 | Early deposit checkpoint for riders returning wet; cash matched per parcel |
| 18:00 | Day review: attempted versus delivered by zone, holds logged for tomorrow’s first run |
The specifics are an example, not a prescription — the pattern to copy is that every monsoon decision (route, hold, notice, cash) has a time and an owner.
Measure the season, not just the day
Monsoon performance deserves its own numbers. Compare delivery success rate, first-attempt success, and average delivery time for monsoon months against dry months, by zone. The zones with the biggest seasonal gaps are where your waterlogging map, sequencing, and packaging rules need work next year. Season-over-season views in reports and analytics make this a ten-minute review instead of a spreadsheet project.
If your monsoon overlaps with an Eid season — as it regularly does — the two stresses compound, and the preparation disciplines from our Eid rush guide apply doubly.
Monsoon delivery is a system test
The monsoon is, in the end, a stress test of systems you should have anyway: packaging standards, zone knowledge, honest statuses, rider safety rules, and daily cash discipline. Couriers that pass it earn something valuable — merchants learn that their parcels and their money are safe with you even in the worst weeks of the year.
Drix keeps the moving parts visible when the weather is trying to hide them: live parcel statuses with hold reasons, zone-level dispatch, per-rider cash matching, and season-over-season reporting in one place. To see how it holds up on your rainiest day, book a demo — or start with a plan that fits your volume on our pricing page.
