Cody
Cody batches nine ecommerce UX and analytics improvements into a single September release
A side-by-side editorial comparison of Zen Cart and Virto Commerce — release velocity, themes, recent moves, and the top alternatives to consider.
A twenty-year-old PHP cart still shipping, entirely on admin polish and PHP 8 hygiene.
Zen Cart is a long-running community-maintained PHP shopping cart whose releases arrive as extended alpha and beta trains rather than finished versions — 2.0.0-rc2, three 2.1.0 pre-releases, and a 2.2.0 alpha are what the recent history consists of. Changelogs are dense lists of small contributor pull requests: admin form corrections, PHP 8 warning cleanups, template fixes, and dependency bumps. There is no roadmap visible in the releases, only accumulated maintenance.
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.
Zen Cart is a long-running community-maintained PHP shopping cart whose releases arrive as extended alpha and beta trains rather than finished versions — 2.0.0-rc2, three 2.1.0 pre-releases, and a 2.2.0 alpha are what the recent history consists of. Changelogs are dense lists of small contributor pull requests: admin form corrections, PHP 8 warning cleanups, template fixes, and dependency bumps. There is no roadmap visible in the releases, only accumulated maintenance.
Three threads run through every release. The first is PHP 8 compatibility — warnings fixed, deprecated calls removed, polyfills added. The second is retiring legacy code the project has carried for years: the Square module, Netscape and IE country-pulldown patches, the banners_on_ssl field, legacy language files for the plugin system. The third is input sanitisation and small accessibility additions like aria-labels on select blocks. Taken together this is a codebase being made supportable rather than extended.
Expect 2.2.0 to continue through further alpha and beta builds on the same slow cadence, with more legacy-module retirements and PHP 8 fixes. Nothing in these releases points to a new capability area.
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 Zen Cart 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 Zen Cart 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 Zen Cart alternatives in E-comm are ranked by recent ship velocity. Browse the "Zen Cart alternatives" section above for the current picks, or visit /alternatives/zen-cart 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.