Spree Commerce vs Wheelhouse
Side-by-side trajectory, velocity, and editorial themes.
Spree doubles down on agent-native, multi-channel commerce on an owned open-source stack
Spree's recent feed is a wave of feature deep-dives following its 5.5 release rather than new releases themselves. The capability surface behind them is real: a typed Admin API with a TypeScript SDK, 25 installable AI-agent skills, sales channels with per-channel catalogs, CLI code generators, one-command upgrades, and stock reservations with order routing — all in code teams own and self-host.
Spree is positioning open-source commerce as agent-native: giving both coding agents and non-technical staff safe, programmatic control of the store, while multi-channel and warehouse routing target operationally complex merchants. The bet is that ownership plus AI-agent tooling beats hosted SaaS for teams that want to automate their own back office.
The next release line will likely extend the Admin API surface and expand the agent-skills library, with more vertical marketplace framing (medical, dental B2B). Timing isn't specified in these posts.
Wheelhouse is making its whole revenue-management stack promptable
Wheelhouse is opening its revenue-management platform to programmatic and AI-driven use. It shipped an MCP server exposing 58 tools at claimed 1:1 parity with the UI, backed by a new set of RM API endpoints (history, sync, segments, teams) — and is running an API hackathon to seed usage. In parallel it keeps deepening pricing intelligence: neighborhood occupancy benchmarking, AI-detected local events on the calendar, and more precise historical anchoring for price floors.
Two reinforcing bets: an API-first surface that lets operators (and their AI assistants) drive pricing from code instead of clicks, and richer market-relative signal so those decisions are better informed. The MCP move is the directional one — it turns Wheelhouse from an app you log into a set of levers an agent can pull. The pricing-intelligence releases (neighborhood metrics, event detection, anchoring sources) suggest the differentiation is shifting toward data quality and market context.
Expect the RM API and MCP surface to keep expanding toward full write parity and more operators building automation on top; the pricing-intelligence cadence points to more neighborhood and demand-signal metrics next.
See more alternatives to Spree Commerce →
See more alternatives to Wheelhouse →