COD Playbook: How to Reduce Pakistan Ecommerce RTO Under 10%
What you will learn: The confirmation flow, 7 anomaly checks, and 6 auto-triage rules that take Pakistani D2C brands from a 30% RTO rate to under 10% — without changing your courier or your team size.
Inside this playbook
What this guide covers
01
Understanding Pakistan's 30% RTO problem
The real cost — per order, per month, per year
02
The 60-second confirmation window
Why the first minute after order decides everything
03
7 fraud checks that block fake orders
Each check with a real Pakistan scenario
04
Customer blacklisting: the nuclear option
When to block, when to review-only, how to handle appeals
30%
Pakistan industry RTO average
Rs 850+
Cost per returned order
Under 10%
Achievable RTO with this playbook
Section 1
Understanding Pakistan's 30% RTO problem
Pakistan ecommerce runs predominantly on Cash on Delivery. Industry estimates put COD at 68% of all orders placed. That number has not changed meaningfully in a decade, because trust in online payment infrastructure — despite JazzCash and Easypaisa — remains limited for first-time buyers and lower-income segments.
The tradeoff: COD unlocks a vastly larger customer base. The cost: 28–32% of those COD orders return undelivered. Each return costs you Rs 850–1,200 in courier return fees, plus the working capital tied up while the product is in transit. At 500 orders a month with 30% RTO, that is Rs 127,500 in direct logistics waste — before you account for restocking time, customer service hours, and the inventory that cannot be relisted while it is on a truck.
The RTO problem is not uniform across Pakistan. Karachi has a higher RTO rate than Islamabad. Interior Sindh has a higher rate than major cities. This reflects access to couriers, familiarity with ecommerce as a purchasing channel, and fraud concentration. Understanding your city-level RTO breakdown is the starting point for any serious reduction effort.
RTO rate by city — Pakistan industry estimate
Most brands blame TCS or Leopards when orders return. But when you audit the data, the same pattern emerges across all couriers: orders that were dispatched without a genuine customer acknowledgment return at a predictable rate. The courier cannot fix a problem that exists before the box leaves your warehouse.
Section 2
The 60-second confirmation window
A customer places a COD order. They are on their phone. They are thinking about the product. They have purchase intent. That window — the first 60 seconds after order placement — is when your confirmation rate is highest. If you reach them in that window, you will get a response.
Wait two hours and they have moved on. Wait until morning and the intent has faded. Kliovo Shop triggers the COD confirmation message within 60 seconds of order creation, automatically, without your team doing anything.
Confirmation rate by time since order
How the confirmation flow works
Order created
Customer completes checkout on your WooCommerce or Shopify store. Order syncs to Kliovo Shop in real-time.
WhatsApp message sent in under 60 seconds
Kliovo sends a Meta-approved template message to the customer's phone number. The message includes order summary, COD amount, and two interactive buttons.
Customer taps Confirm or Cancel
Confirm moves the order to Confirmed status, ready for dispatch. Cancel removes it from the dispatch queue immediately — no box ships.
No response after 24 hours
Unconfirmed order is flagged by the anomaly detection system. Your team reviews before dispatch — not after a return.
What the message looks like
COD confirmation template (Roman Urdu)
Assalam o alaikum {customer_name}!
Aapka order place ho gaya hai.
Order: {item_name}
COD Amount: Rs {cod_amount}
Deliver hoga: {delivery_city}
Confirm karnay ke liye Confirm dabayein.
Handling the "Reschedule" scenario
Some customers want to confirm but need delivery on a specific day. Add a third button — Reschedule — which opens a flow for the customer to specify a preferred delivery date. This preserves the order while matching customer expectations, reducing refusal-at-door returns caused by timing mismatches.
Section 3
7 fraud checks that block fake orders
Anomaly detection runs 7 automatic checks on every order in 0.4 seconds, immediately after order creation. Even with confirmation flows running, some orders need a human eye before dispatch. These checks surface them. Each check below includes a real-world example from Pakistani ecommerce.
Invalid phone number
CriticalFormat validation + carrier range check. A number that starts with 0311 but has only 9 digits will never receive a call or WhatsApp message. Flag it before the CN is printed.
Real example: Order from "03031234" — 8 digits, courier dispatches, returns because number unreachable.
COD amount is zero
CriticalAn order marked COD with a zero cash-on-delivery amount is almost always a data entry error. The courier will attempt delivery expecting no payment — confusing for both parties.
Real example: WooCommerce sync glitch sets COD=0 on a Rs 4,200 order. Courier delivers, collects nothing.
Unconfirmed COD for 24+ hours
WarningIf a customer hasn't responded to a confirmation message in 24 hours, the order is unlikely to convert. Holding it from dispatch avoids a guaranteed return.
Real example: Order placed Sunday evening. No reply by Monday night. Box ships anyway. Returns Thursday.
Stale order (7+ days old)
WarningOrders sitting untouched for more than a week often reflect cancelled customer intent. The customer may have already bought elsewhere. Dispatching invites a refusal at the door.
Real example: Order from 8 days ago — customer ordered the same item from a competitor 5 days ago.
Dispatched without CN number
CriticalA box that leaves your warehouse without a courier consignment number cannot be tracked. If it goes missing, you have no claim. This check catches sync errors before dispatch.
Real example: Manual dispatch override skips CN generation. Package lost. No tracking, no claim.
Missing city
WarningPakistani couriers route by city. An order with no city (or a city not in the courier's serviceable zone list) will be rejected or misrouted — which causes a return.
Real example: Address: "House 12, Gali 3, near masjid." No city. TCS rejects at sorting center.
High-value COD unconfirmed (>Rs 15,000)
WarningA large unconfirmed order ties up working capital and doubles the logistics loss on return. Any high-value COD order should require explicit confirmation before dispatch — not just a timeout.
Real example: Rs 22,000 saree order unconfirmed for 18 hours. Auto-flagged for manual call before dispatch.
Section 4
Customer blacklisting: the nuclear option
The 6 auto-triage rules categorize orders based on customer history. They are the first line of defense. Blacklisting is the final step — for customers who have clearly demonstrated they will not receive orders, and for whom triage holds are not sufficient.
The 6 auto-triage rules
Undelivered Hold
3+ undelivered orders from same phone
Auto-hold. No confirmation message sent. Manual review required.
Most repeat RTO customers follow a pattern. Same phone, same name variation, different addresses. The hold lets your team investigate before any box leaves.
Double Pending
Same phone number has another pending order
Flag as possible duplicate. Hold second order for review.
Common cause: customer places an order, loses the confirmation message, places the order again. Merging duplicates saves a return and a duplicate delivery.
Coupon Hold
Discount exceeds configured threshold (e.g. 30%)
Hold for review. Verify discount code was applied correctly.
Discount abuse is common. Someone shares a one-time code in a WhatsApp group. Flagging over-discount orders lets you catch this before fulfillment.
Incomplete Address
Address field under minimum character count
Tag for address verification. Contact customer to complete.
"Near school" or "Green Town" with no street or house number will fail at the courier's sorting center. One call fixes this before the box ships.
LO (Left Over) Return Flag
Phone number has undelivered + returned orders in history
Immediate hold. High-risk customer. Require advance payment or reject.
LO-return customers are the highest-risk category. They have a history of ordering and refusing. Holding their orders is almost always the right call.
Non-COD Payment Pending
Prepaid order with no payment confirmation received
Hold until payment is confirmed in JazzCash / Easypaisa / bank.
Prepaid orders dispatched before payment arrives leave you with both the goods shipped and the payment delayed. Confirm payment first.
When to blacklist vs. review-only
Blacklisting is permanent. It means any future order from that phone number gets flagged on arrival — before confirmation, before dispatch, before any resource is spent. Use it for:
Blacklist
- 4+ undelivered orders from same phone
- Known fraud pattern (multiple addresses, multiple names)
- Order refused + confirmed fake to your team
- Repeated abuse of discount codes
Review-Only Hold
- First-time buyer, suspicious address
- High-value order from unknown buyer
- Coupon code used above threshold
- Address in high-risk zone
Handling "I want to order again" scenarios
Blacklisted customers sometimes contact support asking why their order is not processing. Your response options:
Require advance payment — Offer to process the order prepaid (JazzCash, Easypaisa, bank transfer). Many genuine customers with RTO history will accept this. Fraudsters usually will not.
Partial payment COD — Require 30–50% advance with the remainder as COD. Reduces your exposure if the order returns.
Permanent block — For verified fraud cases — no exceptions. Document the reason in the blacklist entry so your team knows why.
Key takeaways
What to implement first, and why it matters.
Confirming before dispatch cuts RTO by 60%+
The 60-second WhatsApp confirmation window is the single highest-impact lever. Most brands see 40–60% RTO reduction in month one from this change alone.
7 anomaly checks block 15–20 problem orders per week on average
At Rs 850 per avoided return, that is Rs 12,750–17,000 in direct savings weekly — from automated checks that run in 0.4 seconds per order.
Blacklisting high-RTO customers saves Rs 2,500+ per blocked buyer
Factor in the full cost: return logistics fee, restocking, working capital, and support time. The blacklist is not punitive — it is financial hygiene.
RTO is worse in Karachi and interior Sindh — review city-level data weekly
City-level RTO reports reveal where to apply tighter pre-dispatch checks. Route high-risk city orders through stricter confirmation rules.
The 6 triage rules handle repeat offenders automatically
Undelivered Hold, Double Pending, LO Return — these rules run before confirmation is even sent. Configure them once and they work on every order forever.
Related resources
Apply this playbook
Ready to get your RTO under 10%?
Set up COD confirmation, anomaly detection, and auto-triage in Kliovo Shop. No coding required. Most brands have their first confirmation flow live within the day.