Cash on delivery isn't a workaround in Pakistan. It's the dominant payment method, accounting for over 80% of e-commerce transactions. International playbooks built around Stripe checkouts and credit card CVVs simply don't apply here.
Running COD e-commerce in Pakistan requires its own operating system — confirmation flows, courier integrations, reconciliation schedules, and blacklists. This guide covers the complete professional approach, from order placement to payment in your bank account.
Why Pakistan Is a COD-First Market
Trust built over decades runs deep. Pakistani consumers grew up being told not to share financial information online. Card fraud was (and remains) real. Online banking penetration outside major cities is limited. JazzCash and Easypaisa changed mobile payments significantly, but even those haven't displaced COD for product purchases.
The practical result: most customers will abandon checkout if the only option is online payment. Offering COD isn't optional — it's table stakes.
The 5 Stages of a COD Order
Every COD order travels through five stages. Weakness at any stage increases your RTO rate and damages profitability.
Stage 1: Order Placement
The order is placed — typically via your website, WhatsApp, or social media DM. At this point you have a name, phone number, address, and product selection.
Risk at this stage: Impulse purchases, incomplete addresses, and orders from numbers that will go unanswered.
Best practice: Show clear delivery timelines at the product page level. If you deliver to a customer's city in 2 days, say that. Uncertainty about delivery time is a hidden cause of RTO — customers cancel mentally when they don't know when to expect it.
Stage 2: Confirmation
This is the most important stage — and most stores skip it.
Within 2 hours of order placement, send a WhatsApp confirmation message:
"Hi [Name], we received your order for [Product] (Rs. [Amount]) with COD payment. To confirm delivery to [Address], please reply YES. Need to change anything? Just let us know."
If the customer confirms: proceed to packing. If the customer doesn't reply in 4 hours: send a follow-up, then flag for manual review. If the customer replies NO: cancel immediately, save the shipping cost.
This single step reduces your RTO rate by 40–50%. The customers who don't confirm were never going to receive the order. You've just identified them before spending on shipping.
Stage 3: Dispatch
Only dispatch confirmed orders. This rule alone will improve your profitability dramatically if you're currently dispatching everything that comes in.
Packing and booking workflow:
- Pack the order with the invoice inside
- Print the courier CN (consignment note) — either the courier's official CN or a branded label with their CN number
- Hand off to the courier representative or drop at the nearest hub
With Kliovo Shop, this step connects directly to 7 Pakistani courier APIs — TCS, Leopards, Trax, BlueEx, PostEx, Swyft, and Sonic. You can book consignments in bulk, print CN labels from the dashboard, and get tracking numbers automatically updated on each order.
Courier selection by city: Not all couriers perform equally in all markets. TCS has the most reliable delivery network in Karachi and Lahore. Leopards has the widest rural reach. Trax is the cheapest for high-volume shippers. Route specific cities to the courier with the best track record in that area — your RTO data will tell you which.
Stage 4: Delivery
The order is in transit. Three things can go wrong: the customer isn't available, the address is wrong, or the rider doesn't attempt delivery properly.
Delivery day reminder: Send a WhatsApp message on the morning of the expected delivery date:
"Your [Product] is out for delivery today. Our rider will arrive between 11am–5pm. Make sure someone is available at [Address]. Need to reschedule? Reply now."
This eliminates most "customer not available" RTOs.
Address correction: If the courier reports an address issue, flag it in your dashboard and send a WhatsApp message immediately:
"Our rider is having trouble locating your address. Can you confirm: nearest landmark, street name, and best time to try again?"
Couriers allow 2–3 delivery attempts. Use all of them before accepting an RTO.
Rescheduling: Offer customers a genuine rescheduling option. A message like "Our rider couldn't reach you today — reply with your preferred delivery slot tomorrow" converts a failed attempt to a delivery in 30–40% of cases.
Stage 5: Reconciliation
This is where COD gets complicated. The courier delivers the order, collects cash, and remits it to you — minus their fee — on a schedule that varies by courier.
| Courier | Remittance cycle |
|---|---|
| TCS | Weekly (Fridays) |
| Leopards | Weekly |
| Trax | 3–5 business days |
| PostEx | Can advance COD before delivery |
| Swyft | 3 business days in major cities |
What you need to track:
- Which orders were delivered (and when)
- Which orders were attempted and failed (and why)
- Which orders are pending second or third attempts
- COD amounts per order
- Courier deductions (fee per shipment)
- Expected remittance date vs actual
Without a system, this becomes a spreadsheet nightmare. With Kliovo Shop's reconciliation reports, you can generate a load sheet per courier, match against remittances, and flag discrepancies automatically.
Disputed RTOs: Sometimes couriers mark orders as RTO when they actually delivered (or vice versa). If your data shows "delivered" but the courier remittance doesn't include that COD amount, that's a dispute to raise. Having digital confirmation screenshots (the customer's YES reply) is evidence in your favour.
Common COD Mistakes
Dispatching without confirmation. The most expensive mistake. Every unconfirmed COD order is a coin flip — and a 30% RTO industry average tells you how the coin lands.
No blacklist. Some customers are serial returners. After two RTO incidents from the same number, require prepayment or reject the order. This is standard practice and completely legal.
Ignoring delivery day reminders. Many stores confirm but skip the reminder. That's leaving 20–25% RTO reduction on the table.
Not using courier API data. Your courier dashboard has delivery attempt data. If a specific area consistently generates RTOs across different customers, route those orders to a different courier or flag them for additional confirmation before dispatch.
COD to Digital Payment Conversion
Every customer who pays COD is a customer who hasn't yet decided to trust you with a payment method. That's a conversion opportunity.
After a successful COD delivery, send a message 2 days later:
"Hi [Name], glad your order arrived safely! For your next order, you can skip the COD and get delivery 1 day faster with JazzCash or Easypaisa. Just reply 'digital' and we'll send you the payment link on your next order."
Stores that run this consistently convert 15–25% of repeat buyers to prepaid over 3–6 months. Prepaid customers have near-zero RTO rates. The compound effect on profitability is significant.
The COD Math, Simplified
At 30% RTO with Rs. 250 forward + Rs. 250 return shipping per order, your RTO cost per order is Rs. 500. At 400 orders/month, that's Rs. 60,000 in pure shipping losses plus Rs. 30,000–60,000 in indirect costs.
Getting RTO from 30% to 12%:
- 120 RTO orders down to 48
- Shipping loss: Rs. 60,000 → Rs. 24,000
- Savings: Rs. 36,000/month
This is what a proper COD operating system delivers. The automation pays for itself in week one.