Starshipit vs OroCommerce
Side-by-side trajectory, velocity, and editorial themes.
Starshipit moves up the stack into warehouse management — picking, scanning, and stock alongside its shipping labels.
Starshipit is a multi-carrier shipping platform that has been quietly expanding outside of label generation. The headline move is a built-in warehouse management module covering products and locations, inbound receiving, stock adjustments, pick-pack-ship flows, and barcode scanning on mobile. Around it, the carrier surface keeps growing — UPS third-party duty billing, DHL Express proforma invoices, Asendia and OnSend integrations — and the platform absorbs operational shocks like the Sendle closure with automatic fallbacks rather than blocking fulfilment.
Two narratives are running in parallel. Carrier-side, Starshipit is deepening its cross-border story (importer-of-record settings, third-party duty billing, package-level commodity codes) and broadening its carrier roster, particularly in ANZ. Operations-side, the warehouse module signals a shift from 'we print your labels' to 'we run your fulfilment'. That's a meaningful re-positioning against pure-shipping competitors and against entry-level WMS vendors at once.
Expect the warehouse module to deepen toward features that historically gate WMS adoption — multi-warehouse routing, lot/serial tracking, returns processing — and continued cross-border carrier additions to back the shipping-side story.
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 Starshipit →
See more alternatives to OroCommerce →