ReturnRight: turning a fashion brand's returns from a cost centre into a second chance to sell
An online fashion brand saw a large share of orders come back, each return handled through emails, courier pickups and manual refunds. We built ReturnRight: a self-service returns portal, exchange-first flows with size guidance, instant store credit, warehouse grading and restocking, and returns analytics that show why products come back.
Every return cost twice
ReturnRight's founder calculated that each return cost the brand shipping both ways, handling, a refund and often a product that could no longer be sold at full price. Customers emailed to start returns, waited for pickups, and chased refunds. Most returns were for size, and many customers would have happily exchanged — if exchanging had been easy.
“A customer returning a kurta for the wrong size still wants the kurta.”
Reading six months of returns
We analysed six months of returns. Size was the leading reason, concentrated in specific products and size charts. Refunds took days because warehouse checks were manual. Returned items waited in bags before being inspected and restocked, missing the season they were bought for.
- Most returns were for size or fit
- A few products drove a large share of returns
- Refunds delayed by manual warehouse checks
- Returned stock restocked too late to sell
Exchange first
ReturnRight's portal asks why, then offers the best option: an exchange in another size with stock reserved immediately, instant store credit with a small bonus, or a refund. Pickups are booked automatically. In the warehouse, items are graded on arrival with photos and restocked or routed to outlet channels the same day.
Returns analytics feed back to the product team: which size charts are wrong and which products need better descriptions.
The team
A small team integrating closely with the brand's commerce platform and courier partners.
Returns analysis and launch.
Exchange-first portal and grading app.
Portal, integrations and operations console.
Returns analytics.
5 people in total, working as one team.
Decisions we made
Agreed with the founder and operations head.
Refund-first or exchange-first?
- Default to refunds
- Offer exchange and store credit first, refund always available
Our call: Offer exchange and store credit first, refund always available. Most customers returned for size and still wanted the product.
When to refund?
- After warehouse inspection
- Instant for trusted customers, after inspection otherwise
Our call: Instant for trusted customers, after inspection otherwise. Trusted customers got instant refunds; risk was managed with simple rules.
Grade returns when?
- Weekly batches
- On arrival with photos
Our call: On arrival with photos. Same-day grading got stock back on sale while it was still in season.
Every feature, module by module
Everything that shipped for customers, the warehouse and the brand.
- 01Self-service returns portal
Start a return in seconds.
- 02Exchange-first suggestions
Other sizes with stock reserved.
- 03Instant store credit
Credit with a small bonus.
- 04Automatic pickup booking
Reverse pickup scheduled instantly.
- 05Refund tracking
Status to UPI or original payment method.
- 06Arrival scanning
Returns received against orders.
- 07Photo grading
Condition graded with photos.
- 08Restock or reroute
Restock, outlet or repair decisions.
- 09Quality issue flags
Defects reported to product teams.
- 10Return policies
Windows and rules by category.
- 11Fraud rules
Serial returners and abuse patterns flagged.
- 12Courier integration
Reverse pickups with multiple couriers.
- 13Commerce platform sync
Orders, stock and refunds synced.
- 14Return reasons analytics
Reasons by product and size.
- 15Size chart feedback
Products that run small or large.
- 16Revenue retained
Exchanges and credits versus refunds.
- 17Role-based access
Operations, warehouse and product teams.
- 18Audit trail
Every refund and decision recorded.
Launch
ReturnRight replaced the email process in one step for all new returns. Size charts for the most-returned products were corrected within weeks of the first analytics report.
- Weeks 1–2Analysis
Six months of returns analysed.
- Weeks 3–4Design
Exchange-first portal prototyped.
- Weeks 5–11Build
Portal, grading, integrations and analytics.
- Weeks 12–13Testing
End-to-end returns with couriers.
- Week 14Launch
All new returns on ReturnRight.
What we learned
Offer what the customer actually wants. Easy exchanges kept revenue that refunds would have lost.
Returns data is product feedback. Fixing size charts reduced returns at the source.
- Next.js
- React Native
- NestJS
- PostgreSQL
- Commerce platform integration
- Courier reverse-pickup APIs
- UPI refunds
- AWS Mumbai
