Cash on delivery (COD / CRBT / pay-at-door) remains common across Maghreb and MENA delivery networks. Many teams still run it with shared Excel files and WhatsApp groups. That works — until the first cash dispute.
This article maps the failure modes, the settlement chain (driver → zone → partner → shipper), and what a shipping ops platform must reconcile. Speedliv by Storeino covers parcels, slips, finance settlements, confirmation, and inventory. COD is optional: you can run prepaid or mixed payment on the same parcel truth.
Why Excel + WhatsApp break COD
- COD amount ≠ parcel status — the sheet says “delivered”, the driver says “postponed”, finance has a third version.
- Duplicate files — two “final_v7.xlsx” copies diverge after lunch.
- No structured settlements — who owes whom (driver, zone manager, partner, merchant) is a chat thread.
- Invisible returns — stock and cash diverge when returns never update the same record.
- WhatsApp as system of truth — screenshots are not auditable; night shifts cannot reconstruct the day.
- Multi-country currency and tariff mix — one sheet cannot safely hold MAD, DZD, TND, EGP rules without silent errors.
The settlement chain you must model
COD is not only “collect cash”. It is a chain:
- Parcel carries an optional COD amount when that mode is used
- Driver attempt outcomes update status + collected amount
- Hub / zone closes the driver’s day (settlement)
- Partner or franchise share is calculated from tariffs
- Merchant / shipper invoice or wallet is updated
- Exceptions (partial collect, fake delivery claim, return with cash already moved) need a clear path
If any link lives only in WhatsApp, disputes become archaeology.
What shipping software must trace (no magic)
Without inventing features you do not have:
- Optional COD amount on the parcel
- Operational statuses + slips / barcode scans
- Settlements for driver, zone, and partner
- Invoices / wallet / tariffs
- Optional link to confirmation call center (reduces door refusal)
- Audit-friendly history (who changed amount or status)
Speedliv provides these building blocks as a shipping management platform. It is not “COD-only software” and not a generic business CRM.
Migration path: Excel → system
- Map Excel columns → parcel fields and settlement fields (amount, city, zone, driver, partner, merchant).
- Define roles: hub ops, finance, driver, partner admin.
- Upload cities and zones per country (do not accept a vendor-locked city list).
- Freeze WhatsApp as the system of truth — keep it for human coordination only.
- Run a parallel week: sheet vs system totals must match before you cut over.
- Close each day with driver settlements before the next dispatch wave.
Process checklist (daily / weekly)
Daily
- All delivered COD parcels have collected amount entered (or explicit exception)
- Driver settlements closed for the shift
- Returns scanned and stock states updated
- Open disputes tagged with owner
Weekly
- Partner / zone settlement report vs tariff rules
- Merchant wallet / invoice reconciliation
- Top cancel and refuse reasons (feed confirmation SOP)
- Coverage gaps by city/zone upload quality
KPIs for COD-heavy networks
| KPI | Use |
|---|---|
| Collected vs expected COD | Cash leakage early warning |
| Settlement close time | Finance discipline |
| Door refusal after confirm | Confirmation quality |
| Return rate with COD | Product / address / promise issues |
| Unassigned cash exceptions | Process holes |
Again: COD amplifies the need for discipline; it does not define whether you can use the platform for prepaid flows.
Multi-country note
Import city and zone lists for every country you operate. Maghreb & MENA are the commercial focus; the product is multi-country. Demo MAD sample data is an example, not a limit.
FAQ
Must we use COD to use Speedliv?
No. COD is optional. Prepaid and mixed networks use the same parcels, slips, and settlements modules.
Can we keep WhatsApp for drivers?
Yes for chat. Do not use it as the ledger for amounts or statuses.
What about partner networks?
Model partner tariffs and settlements in the finance layer instead of side spreadsheets.
CTA
Book a meeting at speedliv.com to walk through settlements and optional COD on your network. Demo: https://demo.speedliv.com/en/auth/login · WhatsApp +212 661-962932.
Related: COD delivery management · Logiciel gestion livraison COD · Shipping solution
Concrete Excel failure stories (patterns, not fake customers)
These patterns repeat across Maghreb and MENA networks:
- Afternoon clone: A supervisor duplicates the sheet “to be safe”. Drivers update one copy; finance pays from the other.
- Currency footgun: A multi-country sheet stores amounts without currency codes; partner settlements silently mis-convert.
- Status inflation: “Delivered*” with an asterisk meaning “driver says so” — no scan, no timestamp.
- Return with cash: Parcel returned after a claimed collection; WhatsApp argument lasts three days; ledger never closes.
- Partner shadow books: Each franchise keeps a private COD column; HQ only sees a weekly lump sum.
If two of these feel familiar, you do not have a spreadsheet problem — you have a system-of-truth problem.
Control design for cash
Minimum controls:
- Parcel-level optional COD amount with edit permissions
- Attempt outcome cannot be “delivered” without required fields your SOP defines (scan, photo policy, or OTP — whatever you actually enforce)
- Driver settlement must list parcels and amounts
- Finance cannot mark settled while exceptions remain unowned
- Returns reverse or reclassify cash paths explicitly
Speedliv’s finance building blocks (driver/zone/partner settlements, invoices, wallet, tariffs) exist to support this discipline on a shipping platform — not to promise a full banking product.
Working with partners and franchisees
Partner networks need:
- Shared parcel statuses
- Clear tariff tables by zone
- Settlement reports both sides accept
- A rule for who owns door refusal after confirmation
Side WhatsApp groups between franchise and HQ should not redefine amounts. Put the contract math in tariffs; put the day’s cash in settlements.
Prepaid coexistence
Run a single SOP for parcel lifecycle. Payment mode is a field — not a separate product. When COD is empty/disabled, settlements still close on delivery counts, partner shares, and service fees.
30-day COD hardening plan
Week 1: Freeze amount edits to finance + supervisor roles.
Week 2: Day-close settlements mandatory before next dispatch.
Week 3: Reconcile partner reports; kill duplicate sheets.
Week 4: Feed door-refusal reasons into confirmation training.
Extended FAQ
Should drivers type COD amounts freely?
Prefer amount inherited from parcel/confirmation with supervised override only.
What if we are 90% prepaid?
You still need settlements for delivery fees and partners. Optional COD fields simply stay unused on most parcels.
Does Speedliv replace accounting software?
It traces operational settlements and related finance objects for shipping ops. Keep your statutory accounting tools; integrate rather than invent overlap claims.
Sample day-close agenda (45 minutes)
- Export undelivered COD parcels with amounts (5 min)
- Match driver app collections vs expected (15 min)
- Open exception tickets with owners (10 min)
- Post partner/zone draft settlement (10 min)
- Announce freeze: no silent WhatsApp amount edits after cutoff (5 min)
Run this agenda at the same time daily. Consistency beats heroics.
Document kit to keep beside the platform
- Tariff PDF/sheet mirrored into system tariffs
- COD exception codes list (one page)
- Role matrix (who edits amounts)
- Escalation tree for missing cash
When those live only in a founder’s notebook, growth stalls.
