Virto Commerce
Three maintained branches, one credential bug, and very little else moving.
A side-by-side editorial comparison of VTEX and Wheelhouse — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | VTEX | Wheelhouse |
|---|---|---|
| Sector | E-comm | E-comm |
| Velocity score | 7.5 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | mcp, ai-skills, delivery-promise, headless-commerce | revenue-management, api-first, mcp, webhooks |
| Last editorial update | 3mo ago | 1d ago |
| Website | Visit → | — |
Going MCP-native across developer tooling and customer-support analytics in the same week.
VTEX is shipping AI-native surfaces across two distinct directions at once: a Developer MCP plus 42 AI Skills for platform development, and a CX Platform MCP server that lets AI assistants query customer-support analytics. Underneath, the Delivery Promise stack is being componentized for headless storefronts and Store Framework themes, with breaking dependency changes for migrators. Routine infra hygiene continues — Node.js version selection in WebOps, GitHub Enterprise support, VTEX IO Builder lifecycle statuses with retirements of Node 3.x/4.x and Dotnet 0.x/1.x.
Wheelhouse is closing the last gaps between its app and the API other companies build on.
Wheelhouse ships API surface faster than app features. The current release rolls segment performance metrics up across every listing a saved segment matches, works across owned and shared or managed listings, and converts monetary metrics into whichever currency the caller asks for. It reaches the same MCP server that already exposes the platform to AI assistants, so the aggregate is available from a prompt as well as an endpoint.
VTEX is shipping AI-native surfaces across two distinct directions at once: a Developer MCP plus 42 AI Skills for platform development, and a CX Platform MCP server that lets AI assistants query customer-support analytics. Underneath, the Delivery Promise stack is being componentized for headless storefronts and Store Framework themes, with breaking dependency changes for migrators. Routine infra hygiene continues — Node.js version selection in WebOps, GitHub Enterprise support, VTEX IO Builder lifecycle statuses with retirements of Node 3.x/4.x and Dotnet 0.x/1.x.
The platform is positioning itself as the ecommerce surface AI agents use rather than just operate around. Two MCPs shipped within days establish that pattern on both the build side (developer tooling) and the run side (CX analytics). In parallel, the storefront stack is consolidating around Delivery Promise as the canonical delivery/pickup primitive, with the older shipping-option components being retired.
Expect more MCP servers covering additional VTEX domains — likely Catalog, Orders, and Logistics — and for the Skills catalog to broaden beyond developer use cases into merchandising and operations. Delivery Promise components will graduate from beta and become the default expected primitive in storefront documentation.
Wheelhouse ships API surface faster than app features. The current release rolls segment performance metrics up across every listing a saved segment matches, works across owned and shared or managed listings, and converts monetary metrics into whichever currency the caller asks for. It reaches the same MCP server that already exposes the platform to AI assistants, so the aggregate is available from a prompt as well as an endpoint.
The sequencing is deliberate: expose everything through an API, make it reachable from AI clients, then let it push events out so partners can build without polling. This release is the follow-through on a promise made in July — the aggregated metrics endpoint was announced then, and now covers shared and managed inventory and multi-currency portfolios, which is what property managers running someone else's listings actually need. IntelliHost remains the proof of the model, a third party closing the full pricing loop on Wheelhouse rails.
With webhooks, scoreboards and segment aggregates in place, the remaining gap is write-side automation at portfolio scale rather than per-listing. Expect the partner roster to grow before the app does — the entries consistently describe the API as the product's leading edge.
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 VTEX or Wheelhouse.
Three maintained branches, one credential bug, and very little else moving.
Canix is turning cannabis compliance paperwork into something its AI fills in for you.
ShipHawk's feed is fulfillment thought leadership with no product releases
Shopify pulls retail setup and store analytics onto one Point of Sale page
Shopaccino's tracked feed is a marketing page scrape with no release data in it
Antavo publishes loyalty-program teardowns, not release notes.
See all VTEX alternatives → · See all Wheelhouse alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — mcp — within E-comm. VTEX is currently shipping more aggressively (velocity 7.5 vs 5.0), with 0 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. VTEX is currently shipping more aggressively (velocity 7.5 vs 5.0), with 0 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 VTEX alternatives in E-comm are ranked by recent ship velocity. Browse the "VTEX alternatives" section above for the current picks, or visit /alternatives/vtex for the full list with editorial commentary on each.
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.