The Returns Platform You Love Isn’t the Problem

Here's what is...

Ask an ecommerce operator what they think of their returns platform and you’ll probably get a good answer. In our latest research, Reveni scores 9.5 out of 10. Loop sits at 8.7. Swap at 8.3. These aren’t reluctant endorsements. Operators genuinely rate the tools they’re using.

So why does the returns process still feel, for so many teams, like a constant source of pain?

That’s the question our returns and cross-border research puts at the centre of its second chapter. And the answer is one of the more useful distinctions in the whole report: the gap between tool satisfaction and operational confidence.

Operators like their platforms. They do not necessarily trust their returns operation.

That gap, between “I like my returns platform” and “I trust my returns process end to end,” is where margin leaks. It’s where manual workarounds live. It’s where the spreadsheet that someone built eighteen months ago becomes quietly load-bearing infrastructure.

The pain, when you dig into it, isn’t in the platform itself. It’s in everything the platform has to connect to.

Integrations with WMS, ERP, and OMS systems that half-work or require constant maintenance. International routing logic that doesn’t flex cleanly across markets, carriers, and cost structures. Reporting that’s fragmented across three systems and reconciles in none of them.

As one operator put it during our research: “The returns portal is great. The returns process is a nightmare.”

That sentence captures something important. It tells you that the product problem in returns has largely been solved. The platforms are good. The interfaces are clean. The customer-facing experience has improved significantly. What hasn’t improved at the same rate is the operational infrastructure those platforms sit inside.

Our research surfaces a consistent set of operational failures that show up not as edge cases but as default behaviour across brands. Returns being routed to the wrong warehouse because the logic doesn’t reflect actual cost or inventory. Duties being paid twice, or not reclaimed at all, on international returns. Exchanges requiring manual intervention despite available stock. Customer service teams overriding policies to unblock customers, creating inconsistency and margin leakage downstream. Finance teams reconciling returns and refunds weeks later, outside the core systems.

None of those are platform failures in isolation. They’re symptoms of systems that weren’t built to work together at this level of complexity.

The other area the research flags is recovered revenue. Almost every brand we spoke to is capturing some value through exchanges and store credit. Very few feel confident they’re maximising it. The mechanics exist in most modern platforms. The strategic clarity doesn’t. Teams aren’t sure what good looks like, how much they’re actually retaining, or where the biggest opportunities sit.

What this means practically is that if you’re evaluating your returns setup and the platform scores well, you’re asking the right question in the wrong place. The platform isn’t the bottleneck. The bottleneck is the system around it: the integrations, the routing logic, the reporting, and the manual workarounds that have quietly become part of how the business operates.

Good tools don’t fix broken systems. That’s the takeaway from this part of the research, and it’s a useful frame for any team that’s wondering why their returns operation still feels harder than it should.