When e-commerce brands think about the cost of returns, they think about the refund. The product comes back, the customer gets their money, the inventory goes back on the shelf — or doesn't, depending on condition. That's the cost they measure.
They rarely measure the customer who doesn't come back. And almost nobody measures what that customer told their colleagues, their team, or their network about the experience of getting their money back.
The actual cost of a slow returns process
A slow refund — one that takes 10+ days from item receipt to confirmation — doesn't feel neutral to a customer. It feels actively bad. They have a mental model of how long this should take, shaped by their experience with larger retailers. When you take longer, you're not just slower — you're worse than expected.
The relationship dynamic matters here. Returns are the moment when a customer who had a problem is deciding whether to trust you again. How you handle that moment is a bigger signal about your brand than the original purchase experience.
For DTC brands specifically — where repeat purchase rate is the engine of profitability — this is a serious operational problem dressed up as a logistics admin task.
Where returns processes actually break
In the brands we audit, returns bottlenecks cluster in three places:
Receipt confirmation. The item arrives at the warehouse, but nobody triggers the refund process until someone checks a queue — which might be once a day, or might be less often depending on who's covering. The customer has no visibility into this step and no sense of when the refund will arrive.
Condition assessment. If a return requires inspection before a refund is approved, that step is often undocumented. Different people apply different standards. Some items get restocked and refunded quickly; others sit in a grey area for days while someone decides. The customer is waiting throughout and has no idea why.
3PL to payment system handoff. The physical return is processed at the warehouse level, but the instruction to issue the refund lives in your Shopify admin or payment processor. If those two systems don't talk to each other automatically, someone has to make the connection manually. When that step is missed, the customer has their item back but not their money.
None of these are complex problems. They're process gaps that are easy to close with documentation and clear ownership — but only if someone has actually mapped the returns flow end to end and assigned responsibility for each step.
What a working returns process looks like
The SLA is the foundation. If your returns SLA isn't written down and tracked, you don't actually have a returns process — you have a returns hope. Set a target from item receipt to refund confirmation (we work to a 48-hour standard for our clients) and track it against every return, not just the easy ones.
After the SLA, the most important thing is automated customer communication. A customer who knows their return was received, is being processed, and will be refunded by a specific date doesn't need to contact support. A customer with no visibility generates 3–4 support contacts per return and still feels worse about the experience.
The goal of a returns process isn't to minimise the refund — it's to minimise the reason for the customer to think about the brand negatively after the transaction is closed.
Returns are a cost of doing business in e-commerce. The variable you control is whether the customer who returns something comes back, or whether they don't — and tells people why.