Flipkart: the return that costs twice
A slow refund is annoying. A silent one is what actually breaks trust.
Reframes 'reduce returns' into 'make refund progress visible', and proposes a North Star built around trust, not speed.
What it is
The wait is worse than the delay.
You hit return on Flipkart, and then you wait in a void: no ETA, no pickup notice, no one to call. This teardown's finding is that returns break trust through silence, not speed — and the fix that matters most is the cheapest one. A team teardown; I led problem discovery and the Amazon competitor analysis.
Returns are not an edge case in India
Where trust breaks
The same return, two experiences
The return button hides — users land in Help before they've even started.
Pickup happens unannounced, with no contact and no slot.
The refund goes silent: no progress, nothing to watch.
The user assumes the worst and contacts support.
Honest policy up front, no surprise exclusions.
The user picks the pickup slot.
Refund status goes live the moment pickup completes.
Findable support, with a call-me-back option.
Tradeoffs
Where I'd spend, and where I wouldn't
Ship refund-status visibility first
Visibility lives in the UI and policy layer, needs no new logistics spend, and directly attacks the trust gap. Instant returns feel impressive but cost real money at 20 to 65% of item value per return; they come later, once the cheap fix is proven.
Hold sellers accountable for 'not as described' returns
These returns are caused by the supply side. Routing the cost and the fix to the seller corrects the actual source; punishing buyers corrects nothing and erodes the trust you're trying to protect.
“The metric that matters: returns completed without the user ever asking where their refund is.”