SECTION 01
Measure the problem before changing the process
Start with orders dispatched, parcels delivered, parcels returned and the total cost of returns for a recent period. Separate a customer refusal from an undeliverable address, an unreachable phone, courier damage or a service-area problem. A single return percentage hides these different fixes.
Use dispatched orders as the denominator for a parcel return rate. Example: 12 returns from 120 dispatched parcels is 10%. Track the amount of cash eventually collected separately, because a placed COD order is not cash received. Look at at least several weeks, and compare the same period after you change your workflow.
WORKED EXAMPLE
A simple weekly scorecard
- Orders dispatched
- 120
- Returned parcels
- 12
- Return rate
- 10%
- Return cost
- Your actual invoice
Record a reason beside every return. The total rate shows scale; reasons tell you what to change.
SECTION 02
Confirm the order while it can still be corrected
A buyer may have typed the wrong phone number, chosen an old address or changed their mind. Ask for a clear confirmation before you pay to dispatch. The message should show the item, quantity, cash due and delivery address, then make it easy to confirm or cancel. Do not treat silence as proof that a person will accept a parcel.
Eekaam's optional WhatsApp order confirmation app can ask in English or Urdu, send one reminder, and place unanswered orders on a call list. A written reply or address question belongs with a human before booking. Review the app's sending costs and template status before turning it on.
Check the amount and address, then release the order for packing.
Update the order before a courier receives it.
Call or hold according to your written policy, especially for high-value orders.
SECTION 03
Make the delivery handoff predictable
Your product page and checkout should state the likely delivery window, delivery charge and return policy before the order is placed. After booking, send the tracking number and cash amount due. Customers who know what is arriving and when have a better chance of being available, but no message can guarantee acceptance.
Check the phone number and landmark for addresses that repeatedly fail. For a fragile or size-sensitive product, confirm the exact variant before packing. Ask the courier how many delivery attempts it makes and when a parcel becomes return-to-origin; those rules come from your own contract, not from the store platform.
SECTION 04
Review each return without blaming the customer
When a parcel returns, keep a short incident record: order date, confirmation state, promised window, courier, first-attempt date, customer response, return reason and total fee. If several returns share a reason, fix that point in the process. Wrong-size returns suggest a product-page issue; unreachable buyers suggest a phone or address verification issue.
Compare return rate and margin after the change. A confirmation step has its own cost and may slow dispatch, so the relevant result is net profit per dispatched order, not just fewer returned parcels. Do not publish a claimed reduction percentage until your store's data supports it.
Select the reason that accounts for the most avoidable cost.
Change a message, form field, product detail or courier route.
Recheck the next cohort of dispatched orders against the baseline.