Returnly’s Collapse Is Forcing DTC Brands to Rebuild Returns Infrastructure Fast

When Returnly quietly began notifying merchant partners in late April 2026 that it was sunsetting its standalone returns platform by July 31, the ripple effect landed harder than most expected. The company, which PayPal acquired in 2021 for a reported $300 million and later spun off as an independent entity in 2024, had retained a loyal base of mid-market Shopify brands — many of whom had embedded Returnly’s instant exchange and store credit logic deep into their post-purchase flows. Now, with roughly 90 days to migrate, those brands are facing one of the most operationally intensive platform switches of the year.

The timing is brutal. Q3 is when most DTC operators finalize their tech stack ahead of Q4 peak. A forced migration in June and July — with implementation cycles that routinely run four to eight weeks — is compressing decision windows to nearly nothing. Returns management, once considered a back-office afterthought, is suddenly a boardroom conversation.

Which Returns Platforms Are Gaining the Most Ground After Returnly?

Loop Returns is the most frequently cited beneficiary. The Columbus, Ohio-based platform, which counts Allbirds, CUTS Clothing, and Chubbies among its reference accounts, has seen inbound inquiry volume spike more than 40% since Returnly’s wind-down announcement, according to people familiar with the company’s sales pipeline. Loop’s “Instant Exchanges” feature — which holds a card authorization rather than processing a refund until the return is received — closely mirrors the mechanic Returnly merchants relied on most.

“We’ve onboarded more net-new merchants in the last six weeks than in any equivalent period in our history. The Returnly displacement is real, and operators are not waiting around,” said Jonathan Poma, CEO of Loop Returns, in a statement to Ecommerce Times.

Happy Returns, now operating as a UPS-owned network following its 2022 acquisition, is also fielding aggressive inbound interest — particularly from brands that ship more than 500 returns per month and can leverage Happy Returns’ 10,000-plus drop-off location network to cut reverse logistics costs. The box-free, label-free return experience has become a meaningful differentiator as consumers increasingly expect friction-free returns.

Narvar, which has historically skewed toward enterprise retailers like Sephora and Gap, is reportedly in conversations with several Returnly refugees in the $10M–$50M GMV range — a segment that was historically below Narvar’s focus. And AfterShip Returns, part of the broader AfterShip suite used widely across Shopify and Amazon seller bases, is positioning on price, offering aggressive migration incentives including free implementation support through August 2026.

What Does a Returnly Migration Actually Cost Operators?

The sticker price of the new platform is rarely the biggest line item. Implementation, workflow reconstruction, and customer communication updates tend to dominate the true migration cost. Operators who spoke to Ecommerce Times on background described total migration costs ranging from $8,000 to $45,000 depending on the complexity of their existing Returnly configuration.

• Shopify Flow rebuilds: Merchants who used Returnly’s webhook triggers to fire post-return loyalty credits, reorder nudges, or suppression lists inside Klaviyo need to rebuild those automations from scratch in the new platform or in Shopify Flow.
• ERP and WMS sync: Brands running NetSuite, Brightpearl, or Linnworks need to revalidate data pipelines that Returnly maintained for inventory restocking signals — a step that’s routinely underestimated in migration scoping.
• Customer-facing UX: Branded returns portals embedded in post-purchase email sequences (typically Klaviyo or Attentive flows) need updated URLs, logic trees, and in some cases full redesigns.
• Gift card and store credit ledgers: Returnly held store credit balances for many merchants. Migrating those ledgers cleanly — without creating liability gaps or customer-facing errors — is the single most operationally risky step in the transition.

“The store credit migration is where brands are getting hurt. We’ve seen three clients come to us mid-transition with mismatched balances in the thousands of dollars because they didn’t map the Returnly export schema correctly before importing into Loop,” said Kara Nortman, head of ecommerce operations at fulfillment consultancy Streamline Commerce Group.

How Are 3PLs Responding to the Surge in Returns Complexity?

Third-party logistics providers are feeling the downstream effects. As brands reconfigure their returns tech stacks, many are simultaneously auditing whether their 3PL’s returns receiving workflow is compatible with the new platform’s disposition logic. ShipBob, Whiplash, and Fulfillment by Merchants (FBM)-heavy operators on Amazon are all seeing merchants request updated SLA language around returns processing time — particularly for the “returnless refund” threshold decisions that some platforms now automate based on SKU-level margin data.

ShipBob has been quietly building out a returns optimization module inside its merchant dashboard that integrates directly with Loop and AfterShip Returns, surfacing per-SKU restocking costs alongside platform-recommended disposition rules. The feature, currently in beta with roughly 200 merchants, is expected to GA in Q3 2026.

For brands using regional 3PLs without formal platform integrations, the migration is more manual — and more error-prone. Several operators noted that their 3PL’s receiving team was still logging Returnly RMA numbers as of late May, unaware the platform was sunsetting. That kind of operational lag is where returns backlogs develop heading into peak.

Is Building In-House Returns Infrastructure a Viable Alternative?

For brands above $20M in annual revenue with dedicated engineering resources, the Returnly collapse has accelerated conversations about owning the returns layer internally. The argument is straightforward: third-party returns platforms take a per-return fee (typically $0.50–$2.50 per return depending on volume tier), and at scale, that math starts to favor a custom build on top of Shopify’s native returns API — which has improved substantially since Shopify’s 2025 platform update extended returns management to the Storefront API.

But most operators who’ve attempted an in-house build caution against underestimating the ongoing maintenance burden. Fraud logic, carrier label generation, exchange inventory holds, and refund timing rules all require continuous updates as carrier rates and consumer behavior shift.

“We built our own returns flow in 2024 and spent six months thinking we were done. Then holiday hit, the fraud patterns changed, and we were patching logic at 2am in December. There’s a reason Loop and Happy Returns exist,” said Marcus Thiel, VP of Operations at outdoor apparel brand Ridge & Trail, which does approximately $35M in annual DTC revenue.

What Should Operators Prioritize in the Next 60 Days?

For brands still on Returnly, the operational checklist is unforgiving. Industry consultants and platform vendors interviewed for this piece coalesced around a consistent set of immediate priorities:

• Export all Returnly data now: Customer return histories, store credit balances, RMA logs, and disposition records should be pulled immediately — Returnly’s data export tooling has reportedly been deprioritized as the company winds down engineering resources.
• Map your automation dependencies: Audit every Shopify Flow, Klaviyo, or Attentive workflow that touches a Returnly webhook or API call before selecting a replacement platform.
• Run a 3PL compatibility check: Confirm your fulfillment partner has live integrations — not just “supported” integrations — with your shortlisted returns platform. Ask for a test RMA end-to-end before signing.
• Negotiate migration incentives aggressively: Every major platform is offering discounted implementation through Q3. Loop, AfterShip, and Narvar have all confirmed flexibility on annual contract terms for Returnly migrations completed before September 1.
• Communicate proactively to customers: Brands that have embedded Returnly’s portal URL in packaging inserts, confirmation emails, and help center articles need an immediate audit and redirect strategy before the domain goes dark.

The broader lesson merchants are drawing from the Returnly collapse is one the ecommerce industry has learned repeatedly: post-purchase infrastructure that sits outside a merchant’s core commerce platform carries acquisition and wind-down risk that is rarely priced into vendor selection decisions. As the returns management category consolidates further — Loop, Happy Returns, and AfterShip now command the majority of mid-market Shopify volume — operators who haven’t built platform redundancy into their vendor contracts are exposed.

Peak season is 18 weeks away. The brands that move in June will have time to test. The ones that wait until August almost certainly won’t.