Virto Commerce
Three maintained branches, one credential bug, and very little else moving.
A side-by-side editorial comparison of Cody and Spree Commerce — 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.
Spree's centre of gravity has moved to the TypeScript SDK and a React admin.
Spree's release feed is now dominated by @spree/sdk, which went stable in April and has shipped three minors since, each pinned to a matching backend version. The 5.6 candidates carry the server-side counterpart: a React Dashboard developer preview shipping as the spree_dashboard host gem alongside the existing Rails gems, and single-node Docker as the default deployment path. The Ruby monolith is still the backend, but the surfaces developers touch are increasingly npm packages.
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.
Spree's release feed is now dominated by @spree/sdk, which went stable in April and has shipped three minors since, each pinned to a matching backend version. The 5.6 candidates carry the server-side counterpart: a React Dashboard developer preview shipping as the spree_dashboard host gem alongside the existing Rails gems, and single-node Docker as the default deployment path. The Ruby monolith is still the backend, but the surfaces developers touch are increasingly npm packages.
Two arcs run in parallel. The SDK is absorbing flows that used to require custom backend work — provider-dispatched login against a server-side strategy registry, double opt-in newsletter subscription and token-based unsubscribe, payment sessions across gateways. Meanwhile the API is being made safe for gated commerce: money fields are now typed string or null everywhere, because a prices_hidden channel returns null for every monetary amount including nested records. That is the SDK contract for the wholesale and gated-storefront work landing in 5.6.
Expect 5.6.0 to go stable with the React dashboard still labelled developer preview, and the SDK to keep its lockstep versioning — each minor stating the exact backend release it requires.
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 Spree Commerce.
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 Cody alternatives → · See all Spree Commerce alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Cody and Spree Commerce are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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. Cody and Spree Commerce are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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 Spree Commerce alternatives in E-comm are ranked by recent ship velocity. Browse the "Spree Commerce alternatives" section above for the current picks, or visit /alternatives/spree for the full list with editorial commentary on each.