ShipHero vs OroCommerce
Side-by-side trajectory, velocity, and editorial themes.
ShipHero's rebuilt Wholesale flow is the center of gravity — mobile redesigns, LPN pallet picks, tighter API governance.
ShipHero's April release cadence is almost entirely Wholesale-focused, layering features and polish onto the new Wholesale flow that replaced the legacy system on April 1. Mobile gets standardized redesigns (Cycle Count, Wholesale Dashboard); the workflow gains LPN pallet/carton picks, default-settings governance, and inline API label voiding. On the platform side, unhealthy webhooks get auto-disabled — a real reliability tightening for integration partners.
ShipHero is consolidating around a unified, mobile-first Wholesale experience for 3PLs running high-volume operations. The post-cutover work mostly closes capability gaps the legacy flow had (LPN handling, settings), suggesting confidence in the rebuild and budget freed for adjacent investment. Replenishment got a V2 UI alongside, hinting at a broader app-wide redesign cycle.
Expect similar treatment for Returns and Receiving — both still on older mobile patterns. The webhook-disable policy is a precedent that more API governance (rate limits, scope controls) will follow.
OroCommerce ships 7.0 LTS while quietly opening the back office to AI agents via MCP.
OroCommerce just cut 7.0 LTS, the first major LTS since 6.1 in mid-2025. The parallel 6.1.x stream is shipping substantive functional changes alongside the bug fixes — MCP tools for back-office order/customer management, storefront SSO enforcement, RabbitMQ 4 quorum-queue support, and absolute-URL storefront API options for headless setups. There is also an ongoing 'Smart Order' AI track refining purchase-order recognition via Langfuse-managed prompts.
Two threads are running in parallel. One is conventional B2B commerce platform maintenance — major LTS cuts, point releases full of fixes, infrastructure compatibility work. The other is a deliberate push into AI/agent surface area: MCP integration that lets external agents manipulate back-office records, Smart Order pipelines for inbound POs, OIDC/SCIM identity work that fits the same enterprise-automation arc. The MCP move is the most directional signal — it positions OroCommerce as a platform AI agents can plug into rather than just a back-office UI.
Expect the MCP tool surface to extend beyond orders and customers to products, prices, and content entities, and the Smart Order pipeline to graduate from email POs to a first-class agent-driven workflow in the 7.x line. The bug-fix cadence in 6.1.x will continue alongside while customers migrate to the new LTS.
See more alternatives to ShipHero →
See more alternatives to OroCommerce →