Apparel returns stay high in India mainly because of size and fit uncertainty, products that look different from the listing, quality gaps, COD-led order refusals and delivery delays. Fix them by tracking returns by SKU and reason, improving size charts and photos, tightening QC and packaging, screening risky COD orders, and checking every return against your settlement.
What counts as a high return rate?
There is no single safe number. Return rates differ widely between kurtas, jeans, innerwear, ethnic sets and footwear, and between marketplaces and your own site. Do not chase an industry average you cannot verify. Benchmark yourself instead:
- Compare each SKU against your own category average.
- Compare this month against the last three months.
- Compare sizes, colours and price bands within the same style.
A style with a return rate far above its siblings has a product or listing problem. A rate that is high across the board usually points to sizing standards, sourcing or fulfilment.
Separate customer returns from RTO first
Two different problems get mixed under one "return rate". Fixing the wrong one wastes effort.
- Customer returns: the buyer receives the item and sends it back. Causes are usually fit, look, quality or wrong item.
- RTO (return to origin): the parcel never reaches the buyer, or is refused at the door. Causes are usually address quality, COD refusal, failed delivery attempts or courier issues.
Report them as separate lines by SKU, city and payment mode. Your marketplace settlement and return reports normally give you the reason codes and status needed to do this.
Common reasons apparel returns run high
- Size and fit mismatch. Brand sizing differs from what buyers wear, and a generic size chart does not help. Buyers also order two sizes and return one.
- Product looks different. Colour shifts under studio lighting, fabric feels thinner, or the print scale looks different on a real body.
- Quality issues. Loose stitching, shrinkage, colour bleed or missing buttons.
- Wrong or incomplete item. Wrong size, colour or style dispatched, or a set sent with a piece missing.
- Delivery delays. Orders that arrive late are more likely to be refused or returned.
- COD and impulse orders. Easy refusal at the door, especially for new buyers or high-risk pin codes.
Your own return reason data will show which of these dominates. Do not assume.
Fixes that reduce avoidable returns
Listing and product side
- Add garment measurements (chest, waist, length in cm), not only S/M/L labels.
- Show model height and the size worn.
- Use photos in natural light, with a close-up of fabric and a note on stretch, lining and transparency.
- Update size guidance for any style where one size shows unusually high returns.
Operations side
- Run a pre-dispatch QC check on stitching, labels and size tags, and photograph packed orders for high-value styles.
- Use packaging that keeps garments clean and sealed.
- Review courier performance by pin code and avoid lanes with repeated failed deliveries.
Order risk side
- Check whether the marketplace lets you manage COD or flag risky pin codes. If not, review your own channels separately.
- Watch repeat patterns, such as the same pin code or the same size bracketed across many orders.
Where returns turn into recoverable money
Not every return is a loss you must absorb. Cases worth checking:
- Return marked delivered to you, but the parcel never reached your warehouse.
- Wrong, used or damaged item received instead of the one you shipped.
- Return fees or deductions that do not match your agreed terms.
- Commission or fees charged on an order that later became a return, where your terms say they should be reversed.
The exact rules, claim windows and fee treatment sit in your seller agreement, rate card and settlement reports, and they change. Confirm the latest terms with your marketplace account manager before raising a claim. Keep dispatch photos, return receipt evidence and ticket references for every case.
Build a monthly returns review
A simple review is enough to start. Tools such as MarketplaceMetrics by Fundle can reconcile sales and settlements and track return and recovery cases, but the habit matters more than the tool.
| Metric | Why it matters |
|---|---|
| Return % by SKU and size | Finds fit and listing issues |
| RTO % by pin code and payment mode | Finds courier and COD problems |
| Return reason split | Separates quality, fit and dispatch errors |
| Returns not received or disputed | Feeds your recovery list |
| Fees and deductions on returned orders | Checks charges against agreed terms |
Worked example
Illustrative example only. These figures are assumptions, not benchmarks or marketplace rates.
A brand ships 1,000 orders of a kurta at ₹1,200. Assume reverse shipping and handling cost ₹110 per return, and 15% of returned units cannot be resold, at a cost of ₹500 each.
- At 30% returns: 300 returns × ₹110 = ₹33,000. Unsellable: 45 units × ₹500 = ₹22,500. Total return cost: ₹55,500.
- At 20% returns after better size charts and QC: 200 returns × ₹110 = ₹22,000. Unsellable: 30 units × ₹500 = ₹15,000. Total return cost: ₹37,000.
The difference is ₹18,500 on one style in one cycle, before counting lost sales and any fees charged on returned orders. Use your own settlement data to replace these assumptions.
Questions and answers
What is the biggest reason for returns in Indian apparel ecommerce?
It depends on your catalogue, but size and fit mismatch is a common cause for apparel. Check your marketplace return reason reports by SKU and size before deciding. If fit dominates, fix size charts and measurements first.
Is RTO the same as a customer return?
No. RTO means the parcel goes back to you without being accepted or delivered, often due to refusal, address problems or failed attempts. A customer return happens after delivery. They need separate tracking because the causes and fixes differ.
Can I recover money on apparel returns?
Sometimes. Examples include returns not received, wrong or damaged items returned, or deductions that do not match your terms. Rules and claim windows vary, so check your seller agreement and settlement reports, and confirm current terms with the marketplace.
How often should I review return data?
Monthly is a practical minimum, with a quick weekly look at new launches and high-volume styles. Review by SKU, size, pin code, payment mode and reason, and match return cases against settlements so claims are raised within their windows.