COD done right: courier collection and settlement without leaks

Why COD still matters in the Saudi market

Despite the spread of digital payments, cash on delivery remains the option a wide slice of shoppers asks for: those who want to see the product before paying, those who do not yet trust a store they are buying from for the first time, and those who simply prefer cash. A store that kills COD outright loses sales; a store that offers it without controls loses in a different way — late cash, unexplained discrepancies, and a relationship with couriers built on mutual suspicion.

So the real question is not "should we offer COD?" but "how do we offer it without turning it into a silent bleed?". The answer does not start with technology. It starts with understanding the path an amount travels from the customer's door to the store's account, and pinpointing exactly where documentation goes weak.

COD also deserves to be managed as a business line in its own right, not a marginal checkbox on the payment page. It carries a real operating cost — counting, handover, and deposit time, refusal risk at the door, daily reconciliation effort — and in return it carries revenue from a customer segment that would not have bought otherwise. That trade-off is not settled by impressions but by your own operating data: COD's share of total orders, its doorstep refusal rate, and the full cost of its cycle from collection to deposit.

Where the cash actually leaks

In manual operations — notebooks, WhatsApp messages, and an evening Excel file — the same gaps repeat in almost every business:

• Collection without instant proof: the courier takes cash at the door and records it "later", making his memory the system of record.
• Gap between due and collected: a verbal discount, a customer who paid less, or an order changed by phone and updated nowhere.
• Delayed handover: cash sits in the courier's pocket for days, today's collections blur into yesterday's, and sorting them out becomes impossible.
• Rejections and returns: an order refused at the door with no documentation later gets booked as missing money — an honest courier gets blamed, or a real error slips through.
• Retroactive monthly reconciliation: when discrepancies surface weeks later, nobody remembers the details, so they get closed "amicably" and small losses compound into a painful number.

Note that none of these gaps requires bad faith. The mere absence of point-in-time documentation is enough to turn ordinary mistakes into unrecoverable losses and unrepairable trust.

And as orders grow, these gaps grow faster than linearly. Two couriers can be reviewed by sight and memory; 10 couriers across 3 cities exceed any supervisor's mental tracking, and the simple question "how much cash do we have on the street right now?" becomes a question with no trustworthy answer — a question an operations manager must be able to answer precisely at any moment of the day.

The COD lifecycle: from order to settlement

Real control means every amount lives inside a documented cycle it can never leave. In Pixa's dispatch module the flow passes through five clear stations:

• 1. Creation: the order is registered with its exact COD amount from the first moment — no amounts added verbally en route.
• 2. Assignment: the order is assigned to a specific courier, and the expected amount becomes part of his operational custody for that day.
• 3. Documented collection: at the door, the courier records proof of delivery and the collected amount through the driver app — a mobile web app with OTP login that shows the day's tasks and documents each delivery as it happens.
• 4. Running balance: every collected amount posts immediately to the courier's balance, so a supervisor can see at any moment how much cash each courier is carrying and for exactly which orders.
• 5. Settlement: at handover, a dated settlement closes out the ledger balance against the cash delivered — and any difference surfaces immediately, attributed to specific orders rather than to "last month".

The value is not in any single station but in the unbroken chain. As long as every amount is linked to an order, a courier, and a timestamp, ambiguity loses its room to operate — and ambiguity is the habitat leakage lives in.

The cycle also needs explicit handling of the unhappy paths, since they cause most of the confusion: an order refused at the door has its refusal documented with proof on the spot, leaving the courier's custody formally; an order postponed by the customer returns to the scheduling queue, not to a grey zone; an amount collected short for a documented reason has the difference and its cause recorded where it happened, not in someone's memory. When every exception has a predefined path, the exception loses its power to become an excuse.

Courier settlements: daily discipline, not monthly stocktakes

The most important working rule in COD: your risk equals your unsettled balance. A courier carrying one day's collections is a bounded risk you can review in minutes; a courier carrying two weeks of cash is a postponed problem no matter how honest he is. So make settlement a short, fixed rhythm — daily or near-daily — and make its closure a documented event, not a courtesy.

When closing, handle discrepancies with one rule announced to everyone: every difference is attributed to specific orders with its cause recorded the same day (refused delivery, documented discount, entry error). This procedural fairness protects both sides — the store from silent loss, and the honest courier from suspicion he did nothing to earn. And when management needs the big picture, the custom report builder lets you assemble a balances-and-settlements report delivered on a schedule by email or WhatsApp, keeping the numbers in front of decision-makers without anyone requesting them.

Apply a simple separation of duties as well — it raises control quality considerably: whoever collects does not close the settlement, and whoever closes the settlement works from the system's numbers, not the courier's slip. This separation needs no large org chart — one supervisor owning the daily close is enough — but it shuts the door through which most manipulation, and most honest mistakes, enter.

If your business also runs its own fleet, wiring the COD cycle into the same live tracking platform means a courier's position, order status, and cash balance are read from one screen — not stitched together from three disconnected tools.

Side by side: manual COD vs. an integrated system

A controls checklist you can start this week

Do not wait for a full transformation project — these controls can be phased in, and their effect shows quickly:

• Ban uncaptured collection: an amount not documented at the door does not exist in the system.
• Set a ceiling on cash a courier may carry before handover is mandatory, and watch it through the running balance.
• Document rejections and returns as independent events with proof — never a grey zone.
• Close a dated settlement per courier on a fixed rhythm, recording the cause of every difference the day it appears.
• Review just two indicators weekly: total unsettled balances and average balance age — together they measure the health of the whole cycle.
• If you also invoice business customers, look at billing integrations so the cash cycle never drifts apart from the invoice cycle.

Then scale gradually: start with one team until the daily habit settles, then extend to the remaining teams under the same unified rules. As you grow, watch a third indicator alongside balance size and age: the share of settlements closed on their own day. It is the first thing to slip when discipline starts to loosen — and the easiest to catch before the evening Excel file sneaks back in through the emergency window.

Cash on delivery is not the enemy of e-commerce; the enemy is managing it with tools that were never designed for it. When every amount becomes a documented record inside a closed cycle, COD turns into a competitive advantage that wins you the customers who hesitate to prepay — instead of a daily source of anxiety.

Want to see the COD cycle and settlements run on a scenario from your own operation? Talk to the Pixa team and we will walk you through it step by step.