Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
E-commerce & Commerce 5 min read

Ecommerce returns and refund workflow cost in Bangladesh

A cost-per-return model for Bangladesh ecommerce: courier, inspection, restock, refund fees, fraud, COD and the process that stops margin leaking.

E
EncryptTechBD · 0 comments
Clothing on racks in a retail store
Photo: Hannah Morgan / StockSnap

Returns are often treated as a customer-service cost. In reality, they are an inventory, courier and fraud cost that arrives after the sale. A return can consume the margin on the original order and, in cash-on-delivery markets, create a second loss when the parcel comes back damaged or never reaches the warehouse.

This guide gives you a cost-per-return model for Bangladesh ecommerce, including the COD and courier realities that generic return guides miss.

The return lifecycle

  1. Request: the customer asks to return, exchange or refund.
  2. Eligibility: check the policy, the product category and the condition.
  3. Pickup or drop-off: book the courier and give the customer a reference.
  4. Inspection: confirm the item, condition and accessories.
  5. Restock, refurbish or write off: decide the next state of the item.
  6. Refund or exchange: process the payment and notify the customer.
  7. Reconcile: match the courier, payment and inventory entries.

Each step has a cost. The mistake is counting only the refund amount.

The cost-per-return model

  • Outbound courier: the original delivery cost, which is not recovered.
  • Return courier: the pickup or drop-off cost.
  • Inspection labour: the time to receive, check and grade the item.
  • Restock or refurbish: cleaning, repacking, replacement parts or a markdown.
  • Refund fee: payment gateway or MFS fee where applicable.
  • Support: the messages and calls per return.
  • Fraud or abuse: empty boxes, used items, wrong-item returns and COD refusal.
  • Working capital: cash and stock tied up while the return is processed.

Divide by completed returns, not by return requests. The requests that never arrive are a separate operational problem.

Bangladesh-specific costs

Cash on delivery changes the economics. A refused COD parcel is not a normal return: the business pays the outbound and return courier, the item may be damaged and the cash was never collected. A return from a prepaid order is different from a COD refusal, and the workflow should distinguish them.

Courier performance matters. A weak address check, a missed call or a wrong phone number can create a failed delivery that looks like a customer return. Fix the address and phone validation before adding more return automation.

Research on Bangladesh ecommerce returns has found that slow refunds weaken trust and increase dissatisfaction. The customer experience is part of the cost: a slow refund creates support contacts and reduces repeat purchase.

A worked return

A customer orders a ৳2,500 item by cash on delivery. The courier attempts delivery twice, the customer refuses the parcel and it returns to the warehouse. The business pays outbound and return courier, the item is opened and must be inspected, and the cash was never collected. If the item is damaged, it is written off or sold at a markdown. The return cost is several times the support cost of a normal order.

The fix is not "no returns". It is better address and phone validation, a clear delivery promise, a confirmation step for high-value COD orders and a return reason code that separates refusal, damage and buyer's remorse. Each reason has a different owner and a different fix.

Questions to ask a vendor

  • Can the workflow distinguish COD refusal, prepaid return, exchange and damaged item?
  • Does it integrate with the courier for pickup and tracking?
  • Can it enforce the return window and category rules?
  • Does it update inventory automatically after inspection?
  • How are partial refunds and payment fees handled?
  • Can we flag repeat returners without punishing legitimate customers?
  • What reporting is available by product, courier and reason?

A 90-day plan

  1. Calculate the cost per completed return for the last 90 days.
  2. Separate COD refusals, prepaid returns and exchanges.
  3. Rank the top five reasons and the top five SKUs by return cost.
  4. Fix one root cause: sizing content, address validation, packaging or courier choice.
  5. Add a return reason code and a restock decision to every case.
  6. Review refund time, return rate and recovered margin at day 90.

What to measure

  • Return rate: completed returns divided by delivered orders, by product and reason.
  • Cost per return: courier, inspection, restock, refund fee and support.
  • Refund time: from pickup to customer refund.
  • Recovery rate: returned items restocked or resold instead of written off.
  • COD refusal rate: refused parcels divided by COD orders.

A 30-day return audit

Take the last 30 days of returns and tag each one with a reason, a courier, a product and a cost. Separate COD refusals from prepaid returns. Look for one product with a sizing problem, one courier with a delivery problem and one process step that adds days. Fix the largest repeatable cause first; a policy change without a process change usually moves the cost rather than reducing it.

Where this fits in our work

If you want help designing the returns workflow, start with Commerce Systems. The pricing page explains scope. For the support side, read the ecommerce support automation plan.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes