Something is brewing inside ShipHero’s engineering org, and the 3PL and warehouse management software community is paying close attention. Multiple sources close to the matter — including two agency operators who manage fulfillment infrastructure for mid-market Shopify brands — say that ShipHero has been running a behind-the-scenes rewrite of its core Warehouse OS for the better part of eight months, with a rumored hard cutover window targeting Q4 2026. The problem, according to insiders, is that merchants haven’t been told much — and the silence is creating anxiety that’s already pushing some accounts to quietly evaluate alternatives.
“We heard about this from a ShipHero implementation partner, not from ShipHero directly,” said one DTC operations lead who asked not to be named, overseeing fulfillment for a seven-figure home goods brand running roughly 800 orders per day through ShipHero’s self-managed WMS tier. “When your entire pick-and-pack workflow depends on a platform, ‘we’re rebuilding it’ with zero migration timeline documentation is not a comfortable thing to hear through the grapevine.”
ShipHero declined to comment on the record. A spokesperson said only that the company is “continuously investing in platform infrastructure to serve its growing operator base.”
What Is ShipHero Allegedly Rebuilding — and Why?
Sources familiar with the internal roadmap describe the rewrite as an attempt to decouple ShipHero’s 3PL-facing tools from its self-managed WMS product — two segments that have reportedly shared legacy architecture since the company’s early growth years. The alleged goal is a modular, API-first warehouse OS that would allow ShipHero to sell each layer independently: receiving workflows, wave picking, carrier rate shopping, and returns processing as distinct modules rather than a bundled monolith.
One source, reportedly a former ShipHero integration engineer who left the company in early 2026, described the existing codebase as “held together with a lot of custom patches from five years of feature requests.” This person said the rewrite has been internally codenamed “Horizon” and involves a small but dedicated engineering pod separate from the main product team.
If accurate, the modular approach would position ShipHero more directly against players like Deposco, Extensiv (formerly 3PL Central), and the warehouse layer of Körber Supply Chain — all of which have been aggressively courting mid-market 3PLs and brand-operated warehouses in 2025 and 2026.
“ShipHero’s self-managed WMS has always been its quiet competitive advantage with Shopify-native brands. If they’re rebuilding the foundation without communicating it clearly, they’re creating an opening for Extensiv and Deposco to walk right in.” — a 3PL consultant who works with brands doing $5M–$50M in annual revenue
Which Merchants Are Most Exposed?
The accounts most nervous about the unconfirmed rewrite are reportedly brands running hybrid fulfillment models — using ShipHero’s WMS for their own warehouse while also routing overflow to ShipHero’s 3PL network. Those operators have dual dependencies: their warehouse logic and their outsourced fulfillment SLAs both live inside the same platform.
- Brands processing 500–2,000 orders per day through ShipHero’s self-managed WMS tier are reportedly the most vocal internally about wanting a formal communication from the company.
- Several Shopify Plus brands in the apparel and supplements verticals are said to be running parallel evaluations of ShipHero vs. Extensiv 3PL Warehouse Manager and ShipHero vs. Logiwa WMS.
- At least one 3PL operator — running three warehouse nodes in the Southeast U.S. — has reportedly begun a formal RFP process, citing “platform uncertainty” as the primary trigger.
- Agency partners who built custom Shopify-to-ShipHero integrations via API are said to be watching the rewrite news closely, worried that endpoint deprecations could break automations they’ve sold as managed services.
“We have three clients on ShipHero and we’ve built fairly deep Shopify Flow integrations that trigger warehouse events,” said Derek Osman, a fulfillment operations consultant at a Shopify Plus agency in Austin. “If they deprecate the v2 API endpoints without a proper migration window, we’re looking at a lot of billable remediation hours — and some very unhappy clients.” Osman said his firm has not received any official communication from ShipHero about a platform transition timeline.
Is ShipHero CEO Aaron Rubin Aware of the Merchant Anxiety?
Aaron Rubin, ShipHero’s co-founder and CEO, has historically been one of the more communicative executives in the 3PL software space — active on LinkedIn, willing to engage publicly on operational topics, and known for posting detailed threads about warehouse economics. Which is part of why the current silence is striking observers as unusual.
Rubin has not posted publicly about any platform rewrite, and sources say internal Slack messages shared in a private ShipHero merchant community group have gone without official response. One message, reportedly posted by a merchant in late April 2026 and shared with Ecommerce Times, asked directly whether the “Horizon project” would affect existing API integrations. It allegedly received a response from a ShipHero support agent saying the question had been “escalated to product” — with no follow-up in the three weeks since.
“Aaron is usually very visible when ShipHero is doing something interesting. The quiet is loud right now. That tells me either the rewrite is messier than expected, or they haven’t figured out how to message it yet.” — a logistics technology investor familiar with the WMS market
Rubin did not respond to a request for comment by publication time.
Who Stands to Benefit If Merchants Start Shopping Around?
The rumored instability — unconfirmed as it is — has reportedly activated business development teams at several competing platforms. Sources say Extensiv has been running targeted outreach to ShipHero accounts in the $2M–$20M GMV range, specifically leaning on its established API documentation and multi-node inventory capabilities as stability differentiators. Logiwa, which repositioned as a fulfillment cloud platform in 2024, is also said to be active in the conversation.
Separately, at least one source mentioned that Körber Supply Chain’s SMB-facing team — which has been building downmarket from its traditional enterprise positioning — has been mentioned in at least two RFP processes triggered by ShipHero merchant anxiety this spring.
- Extensiv (3PL Warehouse Manager): Reportedly running outreach targeting ShipHero self-managed WMS accounts, emphasizing migration tooling and API stability.
- Logiwa WMS: Said to be positioning its fulfillment cloud architecture as a lower-disruption alternative for brands that need warehouse flexibility without a full platform overhaul.
- Deposco: Quietly gaining traction with mid-market omnichannel brands that have outgrown entry-level WMS tools.
- Hopstack: Emerging as a dark horse — sources mention it coming up in at least one evaluation driven by a ShipHero concern, citing its Shopify-native API design.
“Every time a dominant WMS player has a platform transition that gets communicated poorly, we see a 90-day window where the alternatives can close deals they couldn’t close before. That window may be opening right now.” — a supply chain software sales leader who asked not to be identified
What Should Merchants on ShipHero Do Right Now?
Regardless of whether the Horizon rewrite is as disruptive as sources suggest, operators running material order volume through ShipHero should be taking a few precautionary steps, according to logistics consultants Ecommerce Times spoke with.
- Document every custom API integration and webhook dependency you’ve built on top of ShipHero — including any Shopify Flow automations that touch warehouse triggers.
- Request a formal platform roadmap briefing from your ShipHero account manager. If you’re on a self-managed WMS contract, escalate to a senior account contact if the standard CSM can’t provide answers.
- Run a lightweight parallel evaluation — not necessarily to switch, but to understand your migration cost and timeline if you needed to move in 90 days.
- Audit your SLA documentation. If your fulfillment SLAs are contractually tied to specific ShipHero platform features, get clarity on whether those commitments survive a platform architecture change.
“The merchants who get hurt in platform transitions are always the ones who assumed their vendor would tell them before anything changed,” said Osman. “In ecommerce operations, you have to assume change is always 60 days away and build accordingly.”
How Does This Fit Into the Broader 2026 WMS Market Shakeout?
The ShipHero situation, confirmed or not, is playing out against a broader backdrop of consolidation and platform pressure in the warehouse management software market. Extensiv has been aggressive post its rebranding. Deposco closed a significant growth round in late 2025. And the rise of AI-driven slotting and dynamic wave picking — which companies like Exotec and 6 River Systems are pushing into mid-market — is raising merchant expectations for what a modern WMS should do.
ShipHero built its brand by being the Shopify-native WMS that independent brands and scrappy 3PLs could actually afford and implement. If the Horizon rewrite delivers what insiders describe — a modular, API-first architecture with cleaner separation between its 3PL and self-managed products — it could cement that positioning for the next five years. But the path from legacy monolith to modern platform has claimed plenty of logistics software casualties, and merchants have long memories.
Sources say they expect ShipHero to make a formal announcement about platform changes before the end of Q2 2026. Ecommerce Times will continue to monitor developments. If you’re a merchant or operator with direct knowledge of the ShipHero platform transition, reach out via our secure tip line.
