nopCommerce
Six 4.90 point releases in nine months, every one promising plugins won't break
A side-by-side editorial comparison of Wheelhouse and Saleor — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Wheelhouse | Saleor |
|---|---|---|
| Sector | E-comm | E-comm |
| Velocity score | 6.3 | 2.5 |
| Sparks · 30d | 1 | 0 |
| Top themes | revenue-management, api-first, mcp, partner-ecosystem | release-candidate, webhooks, pagination, traffic-control |
| Last editorial update | 3d ago | 12h ago |
| Website | — | Visit → |
Wheelhouse finished its API and stopped assuming a human is the one setting prices.
Wheelhouse prices short-term rentals, and the last two months have been spent making every part of that reachable without the app. The RM API now covers dynamic comp sets, segments, teams, sync, base-price and calendar history, and notification settings — the July 14 release states every known gap between the app and the API is closed — while an MCP server exposes 58 tools with 1:1 UI parity. The pricing engine itself keeps advancing separately: Historical Anchoring gained a second anchor source and 18-month coverage, and market events are detected and surfaced on listing calendars.
Two release rows is all Saleor has here, and both are maintenance on the 3.23 line.
Only two Saleor entries have been captured, both on the 3.23 maintenance line rather than any new minor. The recent one is a release candidate carrying four changes: an identifier field on the Webhook model, a unique tie-breaker added to default cursor pagination ordering, and a setting to block customer and anonymous traffic. The other is a refresh rebuild of 3.23.11 with no described content.
Wheelhouse prices short-term rentals, and the last two months have been spent making every part of that reachable without the app. The RM API now covers dynamic comp sets, segments, teams, sync, base-price and calendar history, and notification settings — the July 14 release states every known gap between the app and the API is closed — while an MCP server exposes 58 tools with 1:1 UI parity. The pricing engine itself keeps advancing separately: Historical Anchoring gained a second anchor source and 18-month coverage, and market events are detected and surfaced on listing calendars.
The API is being treated as the product surface and the app as one client of it. The IntelliHost integration shows the intended shape — a partner reading the portfolio each morning, flagging underpriced dates, and pushing approved changes back through the API — which moves Wheelhouse from a tool a manager opens toward a pricing service other software drives. Recent posts lean increasingly on partner and co-marketing announcements rather than in-app features.
With parity closed, the next moves should be partner-side: more integrations built on the RM API, and rate limits or tiering that reflect programmatic use. Whether Wheelhouse ships its own agent on top of the MCP surface, or leaves that to partners, is the choice the entries leave open.
Only two Saleor entries have been captured, both on the 3.23 maintenance line rather than any new minor. The recent one is a release candidate carrying four changes: an identifier field on the Webhook model, a unique tie-breaker added to default cursor pagination ordering, and a setting to block customer and anonymous traffic. The other is a refresh rebuild of 3.23.11 with no described content.
What is visible points at operational hardening of a stable branch rather than product direction. A pagination tie-breaker fixes result ordering that can silently duplicate or skip rows at scale, webhook identifiers make integrations addressable, and a switch to block customer and anonymous traffic is the kind of control a storefront operator reaches for under load or abuse. All three serve people running Saleor in production, not people evaluating it.
With only two entries captured and both on a patch line, there is not enough here to call Saleor's next move; the release candidate would normally be followed by the final 3.23.22.
Other E-comm products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Wheelhouse or Saleor.
Six 4.90 point releases in nine months, every one promising plugins won't break
An inventory and shipping tool publishing seller newsletters where releases should be
A loyalty platform publishing marketing research where a changelog should be
Shiprocket's feed is Indian seller SEO — logistics guides and marketplace explainers, no releases.
LoyaltyLion is arguing loyalty should run everywhere a brand does — in posts, not releases.
LitCommerce is running a migration land-grab on inkFrog's shutdown, entirely through blog posts.
See all Wheelhouse alternatives → · See all Saleor alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Wheelhouse is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Wheelhouse is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other E-comm products to evaluate alongside.
Top Wheelhouse alternatives in E-comm are ranked by recent ship velocity. Browse the "Wheelhouse alternatives" section above for the current picks, or visit /alternatives/wheelhouse for the full list with editorial commentary on each.
Top Saleor alternatives in E-comm are ranked by recent ship velocity. Browse the "Saleor alternatives" section above for the current picks, or visit /alternatives/saleor for the full list with editorial commentary on each.