Shoplazza
Shoplazza's changelog is an API reference in disguise — one endpoint per entry.
A side-by-side editorial comparison of SAP Commerce Cloud and GrandNode — release velocity, themes, recent moves, and the top alternatives to consider.
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.
GrandNode rebuilt itself into modules — then the release feed went quiet for a year.
GrandNode ships one substantial beta per .NET major version, and the last one, 2.3.0, was the most structural: the monolith split into installable modules for installation, migration, API and scheduled tasks, each toggleable from appsettings, and the API layer dropped OData and Swagger for OpenAPI and Scalar. Nothing has appeared in the feed since that release in early 2025.
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.
GrandNode ships one substantial beta per .NET major version, and the last one, 2.3.0, was the most structural: the monolith split into installable modules for installation, migration, API and scheduled tasks, each toggleable from appsettings, and the API layer dropped OData and Swagger for OpenAPI and Scalar. Nothing has appeared in the feed since that release in early 2025.
The arc across these four betas is consistent decomposition. Each cycle pulls something out of the core — database providers, the vendor portal, template handling, then the installation and API subsystems themselves — and re-lands it as a separable piece. Payments moved the same way, with Stripe Checkout replacing the bundled PayPal plugin. The direction is clear; the cadence is not, and roughly a year of silence in the feed is the more significant fact right now.
The entries establish a rhythm of one beta per ASP.NET Core major, which would point at a .NET 10 cycle next, but nothing in this changelog indicates whether that work is underway — the gap since 2.3.0 is unexplained here.
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 SAP Commerce Cloud or GrandNode.
Shoplazza's changelog is an API reference in disguise — one endpoint per entry.
The logistics platform is invisible behind a daily run of small-business explainers.
Virto ships several times a week, but the same fix lands three times under three version numbers.
SendOwl opened its store data to AI assistants, and gave sellers a customer record at last.
Wix is letting agencies describe an automation in chat and get a working endpoint back.
An eCommerce content blog crawled as a changelog; no product releases in the feed.
See all SAP Commerce Cloud alternatives → · See all GrandNode alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. SAP Commerce Cloud and GrandNode are shipping at a similar cadence (velocity 0.0 vs 0.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. SAP Commerce Cloud and GrandNode are shipping at a similar cadence (velocity 0.0 vs 0.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 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.
Top GrandNode alternatives in E-comm are ranked by recent ship velocity. Browse the "GrandNode alternatives" section above for the current picks, or visit /alternatives/grandnode for the full list with editorial commentary on each.