Cody
Cody batches nine ecommerce UX and analytics improvements into a single September release
A side-by-side editorial comparison of Saleor and Virto Commerce — release velocity, themes, recent moves, and the top alternatives to consider.
Saleor's public feed shows release tags, not what's in them.
The 3.23 line moves through release candidates — 3.23.26-rc.0 and rc.1 landed hours apart on August 6 — but only one entry in the window carries an actual change list. That entry, 3.23.22-rc.0, shows the shape of the work: an identifier field on the Webhook model, a unique tie-breaker for default cursor pagination, and a setting to block customer and anonymous traffic. The other tags publish with nothing but the release commit reference.
Virto Commerce backports a blade widget UI freeze fix across three active release trains while tightening module auth hooks
Virto Commerce is simultaneously maintaining multiple release trains (3.1007, 3.1039, 3.1060, 3.1068-3.1070), applying the same fixes as backports across the board. The current batch addresses a UI freeze in blade widget containers triggered by repeated sign-in, pipeline hooks for routing and authentication lifecycle events, and a security fix ensuring user deletion targets only by ID. The multi-branch model reflects an enterprise customer base spread across versions.
The 3.23 line moves through release candidates — 3.23.26-rc.0 and rc.1 landed hours apart on August 6 — but only one entry in the window carries an actual change list. That entry, 3.23.22-rc.0, shows the shape of the work: an identifier field on the Webhook model, a unique tie-breaker for default cursor pagination, and a setting to block customer and anonymous traffic. The other tags publish with nothing but the release commit reference.
What is visible is maintenance-grade hardening of an established GraphQL commerce API: pagination determinism, webhook identity, traffic gating. The rc.0-then-rc.1 pattern within a single day suggests a candidate being corrected rather than a feature train, and the point release cadence within 3.23 indicates the branch is in stabilisation rather than expansion.
Expect the 3.23 line to keep issuing patch-level release candidates on this pattern. The feed itself is the limiting factor here — most tags publish without a change list, so feature direction is not derivable from what is being crawled.
Virto Commerce is simultaneously maintaining multiple release trains (3.1007, 3.1039, 3.1060, 3.1068-3.1070), applying the same fixes as backports across the board. The current batch addresses a UI freeze in blade widget containers triggered by repeated sign-in, pipeline hooks for routing and authentication lifecycle events, and a security fix ensuring user deletion targets only by ID. The multi-branch model reflects an enterprise customer base spread across versions.
Module pipeline hooks — firing after routing and after authentication — represent a meaningful extension to the developer API, giving module authors reliable lifecycle callbacks. The bounded API key lookup cache and dedup notifier hot-path optimizations point to ongoing performance work on the auth layer.
Pipeline hook coverage will likely expand to more module lifecycle events in coming releases; the security-focused user-deletion fix (by ID only) suggests a broader audit of identifier handling across the platform may be underway.
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 Saleor or Virto Commerce.
Cody batches nine ecommerce UX and analytics improvements into a single September release
Shopify overhauled its admin shell and pulled Meta into its AI commerce channel layer.
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 Saleor alternatives → · See all Virto Commerce alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Saleor and Virto 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. Saleor and Virto 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 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.
Top Virto Commerce alternatives in E-comm are ranked by recent ship velocity. Browse the "Virto Commerce alternatives" section above for the current picks, or visit /alternatives/virto-commerce for the full list with editorial commentary on each.