Virto Commerce
Three maintained branches, one credential bug, and very little else moving.
A side-by-side editorial comparison of Cody and SAP Commerce Cloud — 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.
SAP is retiring its storefront UIs and rebuilding the surface as APIs.
The dated window is platform housekeeping from March — configurable JWT signing, token granter extensions, custom login redirect placeholders, a B2B customer search API. The undated rows carry a much larger June release: the Accelerator storefront UIs and AddOn-based OCC V2 extensions are deprecated in favour of headless commerce, the open payment framework gains gift cards, tokenization and split-payment extension points, and a run of OCC endpoints appears for wishlists, B2B units and access control.
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.
The dated window is platform housekeeping from March — configurable JWT signing, token granter extensions, custom login redirect placeholders, a B2B customer search API. The undated rows carry a much larger June release: the Accelerator storefront UIs and AddOn-based OCC V2 extensions are deprecated in favour of headless commerce, the open payment framework gains gift cards, tokenization and split-payment extension points, and a run of OCC endpoints appears for wishlists, B2B units and access control.
Two threads run in parallel and they are the same thread. Legacy front-end layers are being deprecated, and the functionality they carried is reappearing as OCC APIs — which is how SAP decouples its upgrade cycle from every customer's storefront customisations. The payment framework work points the other way, toward commerce models the platform could not previously express, with split payments opening marketplace scenarios. Security and identity plumbing — PKCS12 keystores, audit log accuracy, endpoint-level access control — continues underneath at a steady rate.
Expect the deprecation list to keep growing on the same argument, with more accelerator functionality re-exposed through OCC ahead of a removal date; the split-payment extension points are the piece most likely to become a supported marketplace capability rather than partner plumbing.
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 SAP Commerce Cloud.
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 SAP Commerce Cloud alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Cody 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. Cody 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 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 SAP Commerce Cloud alternatives in E-comm are ranked by recent ship velocity. Browse the "SAP Commerce Cloud alternatives" section above for the current picks, or visit /alternatives/sap-commerce for the full list with editorial commentary on each.