A customer returns a sweater. A support agent handles the request, a warehouse team inspects the item, someone decides whether it gets restocked or written off, and finance books the refund. Each of those steps sits in a different department's budget, which is exactly why almost no retailer can say what a single return actually costs them. The support contact is the visible part. It is rarely the expensive part.
The contact is cheap. What it triggers is not.
Fielding a return request is a relatively small support cost on its own: a status question, an eligibility check, a request to exchange instead of refund. What follows that contact, transportation back to a warehouse, inspection, restocking or write-off, is where the real expense accumulates, and it almost never gets attributed back to the interaction that started it. That disconnect is why returns are easy for a retailer to underprice. The conversation looks routine. The chain behind it is not.
Volume makes the gap worse
Online return rates run well above in-store purchases, commonly cited in the 20 to 30 percent range and higher still for categories like apparel and electronics, where fit and expectation mismatches drive most of it. Every one of those returns starts with a support contact, and that volume compounds during peak shopping periods, landing right when support teams are already stretched thin. A cost that is easy to miss at low volume becomes hard to ignore at scale.
Disposition decisions carry more weight now
For retailers selling into the EU, what happens to a returned item after support hands it off is getting more scrutiny. Under the EU's Ecodesign for Sustainable Products Regulation, large companies are prohibited, starting July 19, 2026, from destroying unsold apparel, clothing accessories, and footwear, and the regulation's definition of "unsold" explicitly includes items a customer has returned, not just inventory that never sold in the first place. This is EU-specific and does not apply to every retailer, but it signals a direction: the information support captures at the first contact, condition, reason for return, is doing more work downstream than it used to.
Where support actually earns its keep here
None of this is a reason to slow down the customer-facing side of a return. It is a reason to make that first contact count. Capturing an accurate reason for return and condition detail at the point of contact feeds every downstream decision, restock, resale, refurbish, or write-off, and getting it right the first time avoids a second contact later to fix a bad disposition. Routing exchanges over refunds where the customer is open to it keeps revenue in the business instead of sending it back through the return chain entirely. Spotting return patterns that look like abuse protects margin without slowing down the legitimate majority of customers. None of it requires slower service. It requires a support operation built to capture the right information the first time, at the volume returns actually arrive in.
Frequently asked questions
Why do returns cost more than they look like they do?
The support contact itself is a small part of the cost. The larger expense sits in what happens after: transportation, inspection, and the decision to restock, refurbish, or write off the item, none of which typically gets attributed back to the original support interaction.
Does the EU's unsold goods rule apply to customer returns?
Yes, for large companies selling into the EU. The regulation's definition of an unsold consumer product explicitly includes items returned by a customer, not only inventory that never sold, and the destruction ban applies from July 19, 2026.
How can support reduce return costs without slowing down service?
By capturing accurate return reason and condition information at the first contact, so downstream restock or write-off decisions are correct the first time, and by offering exchanges where customers are open to them instead of defaulting every return to a refund.