Cash on delivery fulfillment in Uganda — how MFT runs it
How MFT runs cash on delivery in Uganda: order confirmation before release, dispatch custody, proof of delivery, collected-amount capture and reconciliation against your payout batch.
How a COD order runs in Uganda, stage by stage.
The order these stages happen in, and what is recorded at each one.
1. Confirmation before release
A COD order in Uganda is confirmed with the buyer before it leaves the bench — address, landmark, contact number and the amount they will be asked to pay. An order that cannot be confirmed is held rather than dispatched, because an unconfirmed COD parcel is the single largest source of failed attempts.
2. Release and dispatch custody
Once confirmed, the order is picked, packed and handed to the run for its coverage row. The handover is recorded against a manifest, so at every point the parcel has a named holder — bench, dispatch, rider — and the amount to collect travels with it.
3. Delivery attempt and proof
The rider records the outcome at the door with a reason code — delivered, refused, not reachable, wrong address, part payment. A delivered outcome carries the collection evidence for that order. Re-attempts follow the attempt count agreed at onboarding rather than a site-wide rule.
4. Amount collected is captured per order
Collections are taken by cash at the door, mtn momo, airtel money and captured per order in Ugandan shilling (UGX) — not as a daily lump sum. That is what lets a payout line be traced back to a parcel later.
5. Reconciliation against the manifest
Reconciliation runs daily, against your order manifest. Each line carries order reference, parcel reference, destination town and region, collection method, amount collected in ugx and the rest of the fields listed on the Uganda country page, so you can match cash to orders without asking us to reconstruct a day.
6. Payout and close-out
Payout timing is confirmed in your uganda service schedule. Refused and returned parcels are itemised on the same statement — deduction handling is confirmed in your Uganda service schedule Every payment arrives with its reconciliation reference so each amount ties to named orders.
What every COD line carries
These are the fields a query is reviewed against. Nothing is closed on memory.
- Order reference
- Parcel reference
- Destination town and region
- Collection method
- Amount collected in UGX
- Delivery outcome and reason code
- Attempt count
- Collection date and time
- Payout batch reference
Where COD is configured in Uganda
Straight from the governed coverage table on the country page — cut-off and service level as published there.
| Area | Service level | Cut-off | Status |
|---|---|---|---|
| Kampala — Kampala central, Nakawa, Kawempe, Makindye, Rubaga | Same day to 1 working day | Same-day dispatch on orders confirmed before the daily cut-off | Live |
| Wakiso — Entebbe, Kira, Nansana | 1–2 working days | Same-day dispatch on orders confirmed before the daily cut-off | Live |
| Jinja — Jinja town and Njeru | 2–3 working days | Scheduled runs — confirmed at onboarding | Scheduled |
| Mbarara — Mbarara city | 2–4 working days | Scheduled runs — confirmed at onboarding | Scheduled |
| Gulu — Gulu city | 3–5 working days | Scheduled runs — confirmed at onboarding | Scheduled |
Not listed? Read how route review works on the Uganda page, or confirm the exact town with an operator on WhatsApp.
Uganda: the questions this raises
Answered from the same governed coverage rows the country page uses.
Run COD in Uganda with cash you can trace.
Tell us the towns you sell into and your monthly volume. An operator confirms what runs on those routes before you promise anything to a buyer.