Wheelhouse vs OroCommerce
Side-by-side trajectory, velocity, and editorial themes.
Vacation rental pricing platform broadens analytical surfaces and tightens the calendar workflow.
Wheelhouse is a dynamic pricing platform for short-term rentals. The recent six weeks layered in three things: Pricing Engine 9.0 leaving beta with far-future event recalibration, new neighborhood-context data series (Median, percentiles, Expected vs Observed Bookings) inside the pricing chart, and a wave of calendar UX improvements — multi-range non-adjacent cell selection, chart-to-calendar click sync, an Adjacencies (formerly One-Sided Gaps) overhaul, and a Theme Editor for the pricing chart with a color-blind-friendly preset.
Two parallel tracks: model improvements (9.0 GA, 9.1 in research) and surface refinements that make the existing pricing model more legible and actionable. The Adjacencies overhaul and chart-calendar sync both target the everyday hosting workflow rather than the pricing model itself. Wheelhouse is balancing model investment against the operational tooling around it.
Expect Pricing Engine 9.1 in the next quarter, more contextual data series in the pricing chart (likely competitor-set or channel-mix data), and the Theme Editor pattern to extend to other visualizations.
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 Wheelhouse →
See more alternatives to OroCommerce →