Cody
Cody batches nine ecommerce UX and analytics improvements into a single September release
A side-by-side editorial comparison of Shopsys Platform and Virto Commerce — release velocity, themes, recent moves, and the top alternatives to consider.
An open-source PHP commerce framework quietly rebuilding itself around B2B buyers.
Shopsys Platform ships as a Symfony-based commerce framework that merchants fork and extend rather than configure. Four major lines are alive at once — 14.x as the long-lived branch, plus 17.x, 18.x and 19.x — with patch releases backporting infrastructure and dependency work to older lines months after the fact. Recent majors lean heavily on the GraphQL Frontend API, role-based access control, and storefront component cleanup.
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.
Shopsys Platform ships as a Symfony-based commerce framework that merchants fork and extend rather than configure. Four major lines are alive at once — 14.x as the long-lived branch, plus 17.x, 18.x and 19.x — with patch releases backporting infrastructure and dependency work to older lines months after the fact. Recent majors lean heavily on the GraphQL Frontend API, role-based access control, and storefront component cleanup.
The centre of gravity has moved from storefront features to B2B mechanics: customer-user roles that gate cart manipulation and company-wide order visibility, time-limited price lists with per-product special pricing, and CSV import/export for those lists. Alongside that, 19.0.0 spends most of its changelog deleting things — components, utils, hooks, unused dependencies — which reads as a deliberate narrowing of the framework's surface before the next major. Infrastructure releases are batched separately, keeping runtime upgrades out of feature majors.
Expect the B2B role and price-list work to keep extending into the Frontend API, and the component-removal pass in 19.0.0 to continue as a 20.x cleanup. The pace of 14.x backports suggests that branch stays supported for some time yet.
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 Shopsys Platform 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 Shopsys Platform 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. Virto Commerce is currently shipping more aggressively (velocity 5.0 vs 0.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. Virto Commerce is currently shipping more aggressively (velocity 5.0 vs 0.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 Shopsys Platform alternatives in E-comm are ranked by recent ship velocity. Browse the "Shopsys Platform alternatives" section above for the current picks, or visit /alternatives/shopsys 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.