Shopify
Shopify overhauled its admin shell and pulled Meta into its AI commerce channel layer.
A side-by-side editorial comparison of Cody and Spree Commerce — release velocity, themes, recent moves, and the top alternatives to consider.
Cody batches nine ecommerce UX and analytics improvements into a single September release
Cody is an ecommerce platform handling checkout, loyalty programs, search merchandising, promotions, and analytics for online retailers. The September 16 batch release is the product's visible rhythm: a cluster of UX refinements and analytics extensions shipped together rather than continuously. GA4 tracking is getting more granular (list attribution, navigation banner events), the insights dashboard is adding conversion-rate and impressions data, and checkout messaging is becoming more precise—loyalty reward changes now surface a clear notification.
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 is an ecommerce platform handling checkout, loyalty programs, search merchandising, promotions, and analytics for online retailers. The September 16 batch release is the product's visible rhythm: a cluster of UX refinements and analytics extensions shipped together rather than continuously. GA4 tracking is getting more granular (list attribution, navigation banner events), the insights dashboard is adding conversion-rate and impressions data, and checkout messaging is becoming more precise—loyalty reward changes now surface a clear notification.
The pattern across these entries is steady conversion-critical polishing rather than new surface area. Existing features are being made measurable (GA4 enrichment), existing data is being surfaced to merchants (insights dashboard expansions), and friction points at checkout and sign-up flows are being removed one by one. This is a platform that has its core functionality established and is iterating on the details that move conversion rate at the margin.
The sustained GA4 investment suggests the next push is toward attribution clarity for merchants—likely a built-in attribution or first-touch/last-touch report in the Cody dashboard, reducing dependence on GA4 for purchase source analysis.
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.
Shopify overhauled its admin shell and pulled Meta into its AI commerce channel layer.
Virto Commerce backports a blade widget UI freeze fix across three active release trains while tightening module auth hooks
Foxy is steadily expanding its payment and shipping provider integrations via API, with FedEx OAuth and PayPal improvements leading recent work.
Snipcart's changelog is documentation pages—an MCP server and robust API suggest active developer-focused platform work, but no release timeline is visible.
CS-Cart ships one major version per quarter on a steady, predictable cycle with minimal public changelog detail.
Antavo's changelog is all thought leadership — the product roadmap is not visible in these entries.
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.