Virto Commerce
Three maintained branches, one credential bug, and very little else moving.
A side-by-side editorial comparison of Cody and VTEX — release velocity, themes, recent moves, and the top alternatives to consider.
Cody is still paying down its pricing trust debt, one discrepancy a merchant would have caught by hand.
Cody Store shipped six items in a single batch, and four of them exist because a shopper or a back-office system was told the wrong number. Sale prices differed between listing and product pages, spend-and-save offers were rendered as per-item discounts, BOGO rounding sent paid orders to OnTempo looking unpaid, and a countdown timer had quietly become dependent on an unrelated field. The two additions — per-promotion caption colours and undo in Page Builder — are small controls handed to merchants who previously filed a request.
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.
Cody Store shipped six items in a single batch, and four of them exist because a shopper or a back-office system was told the wrong number. Sale prices differed between listing and product pages, spend-and-save offers were rendered as per-item discounts, BOGO rounding sent paid orders to OnTempo looking unpaid, and a countdown timer had quietly become dependent on an unrelated field. The two additions — per-promotion caption colours and undo in Page Builder — are small controls handed to merchants who previously filed a request.
The promotions pipeline is being made honest end to end: what the shopper sees on a listing tile, what the cart charges, and what lands in OnTempo are converging on the same figure. The self-serve thread continues in parallel, with each release moving one more thing out of a support ticket and into a toggle or a colour picker. Nothing here builds new merchandising capability; it is the correctness work that has to precede it.
With display and export both reconciled, the next surfaces are likely to keep extending Promotions v2 controls that were previously site-wide defaults — the caption colour picker is the template for that pattern.
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.
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 Cody or VTEX.
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.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. 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 Cody alternatives in E-comm are ranked by recent ship velocity. Browse the "Cody alternatives" section above for the current picks, or visit /alternatives/cody-store for the full list with editorial commentary on each.
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.