Guide

RTO Reduction Guide: 4 Levers to Reduce Pakistan Ecommerce Returns

What you will learn: How to measure your true RTO rate, which of the 4 operational levers has the highest impact, and how to configure Kliovo Shop to reduce Pakistan ecommerce returns from 30% to under 8% — without changing your courier or adding headcount.

11 min read
By Kliovo TeamUpdated May 2026
Start free with Kliovo ShopBook a demo

Inside this guide

What this guide covers

01

Measuring your current RTO rate

The formula, what counts, and your baseline vs. what is possible

02

Lever 1: Pre-dispatch confirmation

The single highest-impact action — 25–35% RTO reduction from this alone

03

Lever 2: Address and data validation

Catching bad data before the box ships — with real Pakistan examples

04

Levers 3 and 4: Customer risk scoring and courier selection

Pattern detection and city-level courier optimization

Cost of 30% RTO at 500 orders/month

Rs 127,500

150 returns × Rs 850 courier return fee — monthly

Rs 34,000

At under 8% RTO — savings of Rs 93,500/month

Section 1

Measuring your current RTO rate

Before you can reduce RTO, you need to know your actual rate — not your courier's reported delivery rate, which is often inflated. Your true RTO rate is:

RTO Rate Formula

RTO Rate = (Returned Orders / Total Dispatched Orders) × 100

Measure over 30-day windows to smooth out courier batch processing delays

The key nuance: count returned orders as those marked "Returned" or "Undelivered + Returned" by the courier — not just orders that came back to your warehouse. Some returned orders sit in courier warehouses for days before being sent back. Use a 45-day window for each month's calculation to capture delayed returns.

RTO benchmarks — what is achievable

Industry average (Pakistan)28–32%
With COD confirmation only15–20%
With confirmation + anomaly detection10–14%
With all 4 levers active5–9%
Best-in-class Pakistan brandsUnder 5%

The 4 root causes of RTO

Every returned order falls into one of four categories. Understanding which category drives your RTO tells you which lever to prioritize:

1

Customer never genuinely confirmed

Placed on impulse, no follow-up acknowledgment. Accounts for 40–50% of RTO.

Fix: Lever 1: Pre-dispatch confirmation

2

Fake or fraudulent order

Competitor testing, prank, or deliberate fraud. Accounts for 15–20% of RTO.

Fix: Lever 3: Customer risk scoring

3

Bad address data

Wrong city, incomplete address, unreachable customer. Accounts for 20–25% of RTO.

Fix: Lever 2: Address and data validation

4

Courier issues

Delivery area not served, misrouted, poor service in specific zones. Accounts for 10–15% of RTO.

Fix: Lever 4: Courier selection by city

Most brands attribute too much RTO to cause 4 (courier issues) because it is the most visible. The courier is the last thing that touches the order, so it gets the blame. But in most cases, causes 1 and 3 together account for 60–75% of RTO — and both are preventable before dispatch.
1

Lever 1 — Highest Impact

Pre-dispatch confirmation via WhatsApp

The single highest-impact lever in RTO reduction. The mechanism is simple: every COD order receives a WhatsApp message within 60 seconds of placement. The message asks the customer to confirm or cancel. The box does not ship until the customer responds.

The outcome is also simple: customers who did not actually want the order cancel it. You save the Rs 850+ in return logistics costs, the working capital, and the restocking time. Orders that do ship have a customer on the other end who is expecting them — dramatically reducing door refusals.

92%

Confirmation rate within 60 seconds of order

25–35%

RTO reduction from this lever alone

60 sec

Time from order to WhatsApp message

How to configure Lever 1 in Kliovo Shop

1

Connect your WhatsApp Business number

Link via Meta Cloud API (direct), OnCloud, or Kliovo Chat. The number needs to be a verified WhatsApp Business account.

2

Create and submit your COD confirmation template

Template must include customer name, product or order summary, COD amount, and two buttons: Confirm and Cancel. Submit to Meta for approval (24–48 hours).

3

Set up the automation trigger

In Automation Flows: Trigger = Order Created, Condition = Payment Method is COD, Action = Send COD Confirmation Template, Delay = Immediate (0 minutes).

4

Configure button reply logic

Button reply 'Confirm Order' updates status to Confirmed. Button reply 'Cancel Order' updates status to Cancelled and removes from dispatch queue.

5

Set 24-hour anomaly flag

Any COD order unconfirmed after 24 hours should trigger the Unconfirmed 24h anomaly flag. Your team reviews before dispatching.

Most brands see 25–35% RTO reduction in the first 30 days from Lever 1 alone. This is the starting point, not the end state. Implement Lever 1 before anything else. It is the fastest return on configuration time in this playbook.
2

Lever 2

Address and data validation before dispatch

A significant portion of RTO — 20–25% — is caused by address and data issues that make delivery impossible: missing city, address too short, wrong phone format, or a phone number that belongs to a different region than the delivery city. None of these issues require the customer to be a fraudster. They are data quality problems, and they are fixable before dispatch.

Lever 2 uses anomaly detection and auto-triage rules to catch these before the CN is printed. One call to fix an address before dispatch saves one return logistics fee after delivery fails.

Data checks at order intake

Invalid phone number format

Pakistani mobile numbers start with 03xx and are 11 digits long. An order with a 10-digit number or a landline format cannot receive WhatsApp confirmation or a courier call.

Real scenario

Order from "03312345" — 8 digits. Confirmation never delivers. Box ships, nobody receives.

Auto-flag any phone that fails format check. Hold for manual verification.

Missing city

Courier APIs require a city field to route the shipment. An order with no city — or a city name that does not match the courier's serviceable zone list — will be rejected at sorting.

Real scenario

Address: "House 14-A, Street 5, near Mehboob sb ka ghar." No city. TCS sorts to Karachi by default. Customer is in Faisalabad.

Incomplete Address triage rule + Missing City anomaly check. Both flag together for address verification.

Incomplete address (too short)

An address field under 20 characters almost certainly lacks enough information for a courier to deliver. "Green Town" is not a deliverable address. "House 12, Street 4, Green Town, Lahore" is.

Real scenario

Address: "gulshan Karachi near masjid." Courier attempts delivery, cannot locate building, marks as undelivered.

Incomplete Address auto-triage rule flags any address under your configured minimum character count.

City-phone mismatch

A Lahore phone number (0303) with a Karachi delivery address is not automatically fraud — but it is worth a verification call for high-value orders. The customer may be sending a gift.

Real scenario

Rs 18,000 wedding dress order. Lahore phone, Karachi address. One verification call confirms it is a gift for family. Dispatched safely.

Flag high-value orders with city-phone mismatches for manual review. Do not auto-hold low-value orders.

Address issues are the easiest category of RTO to fix because they happen before dispatch. One well-placed verification call — triggered by an auto-triage rule — costs your team 2 minutes and saves Rs 850 in courier return fees. At 20 orders per week with address issues, that is Rs 68,000/month in savings from Lever 2 alone.
34

Levers 3 and 4

Customer risk scoring and courier selection

Lever 3: Customer risk scoring

Every order carries a risk score based on the customer's order history. Kliovo Shop builds this score automatically from three signals: undelivered history, return history, and pending order count. The auto-triage rules act on this score without manual review:

Undelivered Hold

High Risk

Phone number has 3+ undelivered orders in history

Auto-hold. No confirmation sent. Team reviews before dispatch.

Repeat undelivered customers return at 60%+ rate. The hold is almost always the right call.

Double Pending

Medium Risk

Same phone has another active pending order

Flag as potential duplicate. Hold second order. Team merges or cancels.

Duplicate orders from confused customers — easy to merge and save one dispatch cost.

LO Return Flag

Very High Risk

Phone has undelivered + returned orders in history

Immediate hold. Require advance payment or escalate for manual decision.

LO-return pattern is the strongest predictor of future RTO. Require prepayment.

Blacklist

Maximum Risk

Phone number is on your blocked list

Order flagged on arrival. No processing. Team notified.

Permanent block for confirmed fraudsters. Review quarterly to ensure accuracy.

Lever 4: Courier selection by city and order type

Not all couriers perform equally in all cities. Pakistani couriers have different delivery rate profiles by geography. Routing orders to the wrong courier for a city adds avoidable RTO. Smart routing rules in Kliovo Shop handle this automatically:

Recommended routing — Pakistani D2C brands

COD order, KarachiBlueEx or Trax
COD order, LahoreTCS or Leopards
Interior Sindh / ruralTrax (CallCourier)
Prepaid order, any cityPostEx
Order over 2 kgLeopards
High-value COD (Rs 15,000+)TCS

These routing rules require active courier connections in Kliovo Shop. See the Courier Setup Guide for step-by-step API connection instructions for all 7 couriers.

Lever 4 has a lower individual impact than Levers 1–3, but it matters for scaling. As your order volume grows, routing 10% of orders to a better city-matched courier recovers meaningful RTO percentage points. Set routing rules once; they apply to every future order automatically.

Key takeaways

What each lever delivers — and what to implement first.

1

Lever 1 (COD confirmation) delivers 25–35% RTO reduction on its own

This is the one to implement first, this week. WhatsApp confirmation within 60 seconds of order creation. Configure the automation in Kliovo Shop — it takes under an hour.

2

Lever 2 (address validation) catches 20–25% of RTO before it leaves your warehouse

The Incomplete Address triage rule and Missing City anomaly check together flag the most common address-related returns. One verification call per flagged order prevents one return.

3

Lever 3 (customer risk scoring) accumulates value over time

In month one, you have limited history. In month six, your undelivered history data is catching repeat offenders automatically. Start building it from day one.

4

Lever 4 (courier selection) reduces the residual RTO that the other levers don't catch

If 8% of orders still return after Levers 1–3, roughly half of that is courier-related. Smart routing rules shift high-risk city orders to better-performing couriers for those zones.

5

Under 8% RTO is achievable within 90 days with all 4 levers active

Track your RTO rate in 30-day windows. Lever 1 shows results immediately. Lever 2 shows results in week two. Lever 3 strengthens over months. Lever 4 maintains the baseline.

Related resources

COD PlaybookDeep dive into confirmation flows, 7 anomaly checks, and blacklistingAnomaly DetectionHow all 7 automated checks work and how to configure their thresholdsCourier Setup GuideConnect TCS, Leopards, Trax and 4 more couriers with smart routing rules

Apply this guide

All 4 levers are built into Kliovo Shop

COD confirmation, anomaly detection, customer risk scoring, and smart courier routing — configured from a single dashboard with no coding required.

Start free with Kliovo ShopBook a demo