OroCommerce vs Spryker
Side-by-side trajectory, velocity, and editorial themes.
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.
Spryker's changelog feed is currently capturing documentation pages rather than discrete releases.
The recent feed is dominated by feature-overview and integration-guide pages — Customer Account Management, Merchant users, Marketplace Merchant Portal, IAM, MFA, PunchOut Gateway — rather than dated release announcements. What's being surfaced reflects Spryker's B2B and marketplace footprint: Back Office for operators, Merchant Portal for sellers, MFA and IAM for the security layer, PunchOut for procurement integration. None of these entries describe a fresh capability — they describe what already exists.
Without dated release content, trajectory has to be read from what Spryker is documenting rather than what it's shipping. The doc emphasis on Marketplace, PunchOut, and MFA suggests B2B procurement and merchant onboarding remain the center of gravity. For any move to look directional, this feed would need to start surfacing changelogs rather than evergreen reference pages.
Until the source switches from doc-page captures to release-note entries, classifications will stay trivial regardless of what Spryker actually ships. Once the changelog surface clears up, expect commentary to focus on Marketplace operator features and the PunchOut integration matrix.
See more alternatives to OroCommerce →
See more alternatives to Spryker →