What the interviews show. These two are not evidenced the same way, and that is the first thing to hold onto. Loop Returns is discussed by a much larger group who have generally run it longer, and its commentary concentrates on the returns experience itself; where it turns negative, the reasons cluster tightly on cost and on limits buyers run into — one calls it way overpriced, another too limited, and several describe shopping for something else. Redo's buyers describe a more recent experience, several having switched in from another tool, with individual buyers naming price or support as the reason, and their commentary concentrates on cost and value rather than on the returns flow. The caveats on Redo come from its own buyers rather than from Loop's: two say directly that they cannot yet tell whether it is saving them money, one describes a pricing restructure that lowered their rating, and one wants the products that exist to go deeper instead of new ones arriving.
| Strongest contrast in these interviews | Commentary emphasizes the returns experience itself, across a longer-running base | Commentary emphasizes cost and value, across a base describing a recent start |
|---|---|---|
| Buyer pattern in these interviews | Shopify brands with returns running at volume, several reviewing the contract | Shopify brands that switched in recently, often from another returns or support tool |
| Most-discussed job | Returns and exchanges | Returns and exchanges |
| Also does | Configuration buyers describe as extensive enough to be hard to unwind | Order tracking, customer support and other tools buyers describe arriving quickly |
| Praised most | The returns and exchange flow, which is the bulk of what its buyers discuss | Support and onboarding — every buyer who raises the team does so positively |
| Top complaint | Limits buyers run into, described as things they cannot do | Value not yet proved — two buyers say they cannot tell what it is saving them |
| Relative cost | Raised as too high by its lower raters, including one calling it overpriced | Named by some buyers as a reason for switching in, though one describes a pricing restructure |
| Where buyers say it fits | Brands running returns at volume, where the flow itself is what buyers describe | Brands that switched in recently, where price and the vendor team are what buyers describe |
What buyers say about each platform
Every buyer interview spends its minutes somewhere — praising the thing that won the deal, or flagging the thing that still stings. Map where those minutes go for Loop Returns and Redo, and the two conversations turn out to be about different subjects:
Relative share of buyer commentary by theme in Alium's verified interviews, praise vs. complaint, through September 2026. Widths compare themes within this pair — they are relative, not counts. Valence is read against each platform's own mix of praise and complaints.
In their own words
The phrases buyers reach for, verbatim, when they describe each platform:
Loop Returns
“doing what it needs to do” customer returns
“improved some of our customer experience” the returns side
“just way overpriced” for what they are
“it's just too limited” what you cannot do
“so many hooks and so many different processes” to unwind
Redo
“better support as far as client support” than the previous tool
“really self-service” the CS workload
“a no-brainer” on price
“I don't know if it actually does anything or saves us money” the ROI
“restructuring their pricing model” mid-relationship
Where Loop Returns buyers concentrate their praise
Loop Returns' standing rests on the returns flow itself. It is by far the largest share of what its buyers discuss, and most of that commentary is positive: buyers describe it doing what it needs to do for customer returns and giving a decent customer experience, with integration into the store among the things they raise favourably. That everyday returns-flow commentary sits alongside a buyer base that has generally been running the platform longer than Redo's buyers here. The cautions are where the page gets specific, because Loop's lower raters do not scatter — they cluster. Cost is the most common: one calls the platform way overpriced for what it is, another pairs a high cost with support they do not rate, and a third describes trying to cut their contract short. The second cluster is limits, described as too many things you cannot do; one buyer found the customer-facing language hard to set up, and another describes a configuration with so many hooks and processes that changing it became cumbersome. Several of these buyers say plainly that they are shopping, and they do not all name the same destination.
Where Redo buyers concentrate their praise
Redo's standing rests on price, support and a fast-moving team — reported by buyers who are new to it. Cost and value is the largest share of its commentary, and most of it is favourable: buyers describe switching in because the pricing made the move a no-brainer, and one describes it as better support than the tool they left. Every buyer who raises the team does so positively, describing smooth onboarding, responsiveness and a platform self-service enough to take work off a customer-service team. Buyers also describe it reaching past returns into order tracking, customer support and newer tools. The cautions come from inside that same group, which is what makes them worth reading: two buyers say directly that they cannot yet tell whether it is saving them money, and one of those describes returns rising since adopting it. One describes a pricing restructure that pulled their rating down, and one asks for the products that exist to go deeper rather than new ones to keep arriving. Buyers repeatedly note that their experience is still recent.
Loop Returns vs. Redo on cost
Cost is the one place buyers put the two on the same axis, because some name it comparatively when they explain a move:
How switching buyers describe relative price within this pair. Positions reflect buyer commentary, not published pricing or a like-for-like total-cost comparison, and they say nothing about a third platform.
The placement rests on buyers describing the move rather than on any published price. One switching away from Loop calls Redo the cheaper and better solution; another describes Redo's pricing as aggressive enough to make a migration a no-brainer. What the axis cannot show is that Redo's position may not hold still — one of its own buyers describes the company restructuring its pricing model mid-relationship, and lowered their rating because of it. And two Redo buyers raise the separate question of whether the price is buying a result, which is not the same as whether it is low.
What buyers wish they'd known
Before picking Loop Returns
Ask what unwinding it looks like. Buyers describe configuration extensive enough that changing it became cumbersome, and customer-facing language that was hard to set up. Its lower raters cluster on cost and on limits they hit rather than on the returns flow, and several describe reviewing the contract rather than the product.
Before picking Redo
Separate the price from the result. Two buyers say they cannot tell whether it is saving them money, and one describes returns rising since adopting it. One describes the pricing model being restructured mid-relationship. Buyers also repeatedly note their experience is recent, so the longer-run picture is not in these interviews yet.
Four questions the interviews raise
Its buyers mostly describe the returns flow favourably; where they turn negative it is cost and limits, not the experience.
Some buyers name price as a reason for switching in, and cost and value is the largest share of Redo commentary.
The larger, longer-running base here, with the everyday description that comes with it.
Every buyer who raises the team does so positively — onboarding, responsiveness, and concerns acted on.
Its buyers raise price as too high rather than questioning whether the platform is working.
Two buyers say they cannot tell what it is saving them, and one describes returns rising since adopting it.
Buyers describe configuration depth in returns, and one found it extensive enough to be hard to unwind.
Buyers describe tools arriving quickly across tracking and support; one asks for depth in those instead.
Don't see your exact situation?
Get the read for your brand →How the operating conditions differ
Recurring situations in the corpus, and where the evidence concentrates in each:
Pressures visible in these interviews
The complaints these interviews carry sit on both sides: Loop Returns' are cost its lower raters call too high, limits described as things buyers cannot do, and configuration one buyer found hard to unwind; Redo's are value its own buyers cannot yet measure, a pricing model one describes being restructured mid-relationship, and a preference for depth over the pace of new products. The asymmetry worth naming is in the evidence rather than the platforms: Loop's buyers have generally run it longer, and Redo's repeatedly describe an experience that is still recent, so the two bodies of commentary are at different stages as well as different sizes. The implication — ours, not a buyer's — is that the comparison is currently asymmetric: Loop has the longer-running evidence base here, while Redo's newer buyers provide stronger early evidence on price, onboarding and support than on longer-run financial outcomes. The question Redo's own buyers are asking — what is it actually saving us — is the one to answer before the second contract rather than the first. For the wider market, see our Loop Returns vs. Narvar comparison and what returns and post-purchase buyers wish they'd known.
Common questions
Loop Returns vs. Redo: which is better?
These two are not evidenced the same way, which is the first thing to know. Loop Returns is discussed by a much larger group of buyers who have run it for longer, and Redo's buyers repeatedly describe their experience as recent. Within that, the commentary points in different directions: Loop's buyers talk mostly about the returns experience itself, and its lower raters concentrate on cost and on limits they run into. Redo's buyers talk mostly about cost and value, and several describe switching to it from another tool, with individual buyers naming price or support as the reason. Longer-run financial outcomes are less established in this interview base: two Redo buyers explicitly say they cannot yet tell what the platform is saving them.
Why are buyers switching from Loop Returns?
Among Loop's lower raters the reasons cluster. Cost is the most common: one calls the platform way overpriced for what it is, another says the cost is high and the support is not good, and a third describes trying to cut their contract short. The second cluster is limits — buyers describe it as too limited, with many things they cannot do, and one describes a configuration with so many hooks and processes that it became cumbersome to change. The destinations they name are not all the same: one names Redo, another names a different provider's return portal.
Is Redo a good Loop Returns alternative?
Buyers who moved to Redo report positive experiences with support, onboarding and day-to-day use, while its financial result remains less established in these interviews. One switched from Loop and describes Redo providing better support while handling returns and exchanges effectively; others describe migrating from other tools and call the pricing a cost-saving no-brainer, the onboarding smooth, and the platform self-service enough to relieve their customer-service team. The caveats come from Redo's own buyers rather than from Loop's: two question whether it is actually saving them money, one describes a pricing restructure lowering their rating, and one wants existing products to go deeper rather than new ones to keep arriving.
What is the difference between Loop Returns and Redo?
Buyers describe both handling returns and exchanges on Shopify, and the differences they raise are about scope and stage rather than the core job. Redo's buyers describe it reaching past returns into order tracking, customer support and other tools, and some value that breadth while one asks for depth in what already exists instead. Loop's buyers describe returns configuration in greater depth, including one account where extensive hooks and processes made changes cumbersome. The evidence bases differ too: Loop's buyers have generally run it longer, and Redo's describe an experience that is still new.
See which one fits your exact stack
Weighing Loop Returns against Redo, or shopping your returns stack? Do a 15-minute interview about your setup and get this personalized — what peers your size say each one costs once it is running, what the switch actually took, and what the newer option has not been running long enough to prove.
Get my personalized read — 15-min interviewNo password · your interview is anonymized before it ever informs a page like this one.