← Back to home
Comparison · E-comm

Spree Commerce vs Virto Commerce

A side-by-side editorial comparison of Spree Commerce and Virto Commerce — release velocity, themes, recent moves, and the top alternatives to consider.

Spree Commerce vs Virto Commerce: at a glance

FeatureSpree CommerceVirto Commerce
SectorE-commE-comm
Velocity score5.06.3
Sparks · 30d00
Top themesheadless-commerce, typescript-sdk, react-dashboard, gated-pricingecommerce, caching, patch-releases, multi-branch-maintenance
Last editorial update22d ago1h ago
WebsiteVisit →Visit →

What is Spree Commerce?

Spree's centre of gravity has moved to the TypeScript SDK and a React admin.

Spree's release feed is now dominated by @spree/sdk, which went stable in April and has shipped three minors since, each pinned to a matching backend version. The 5.6 candidates carry the server-side counterpart: a React Dashboard developer preview shipping as the spree_dashboard host gem alongside the existing Rails gems, and single-node Docker as the default deployment path. The Ruby monolith is still the backend, but the surfaces developers touch are increasingly npm packages.

Read the full Spree Commerce trajectory →

What is Virto Commerce?

Three maintained branches, one credential bug, and very little else moving.

The feed is a patch stream across three concurrently maintained branches — 3.1007.x, 3.1039.x, and the 3.105x/3.1060 head — with the same defect frequently released to all three within minutes or backported days later. Entries are single-line bug references with issue numbers and no narrative. The null credential fields fix (#3100) is the current example: it shipped on the head branch on 14 August and reached both older branches on 18 August with byte-identical notes. Only 3.1060.0 carries anything distinct — a fix making the production error page reachable and renderable, and a PR description guide for contributors.

Read the full Virto Commerce trajectory →

Spree Commerce vs Virto Commerce: editorial side-by-side

S5.0

Spree's centre of gravity has moved to the TypeScript SDK and a React admin.

◆ Current state

Spree's release feed is now dominated by @spree/sdk, which went stable in April and has shipped three minors since, each pinned to a matching backend version. The 5.6 candidates carry the server-side counterpart: a React Dashboard developer preview shipping as the spree_dashboard host gem alongside the existing Rails gems, and single-node Docker as the default deployment path. The Ruby monolith is still the backend, but the surfaces developers touch are increasingly npm packages.

◆ Where it's heading

Two arcs run in parallel. The SDK is absorbing flows that used to require custom backend work — provider-dispatched login against a server-side strategy registry, double opt-in newsletter subscription and token-based unsubscribe, payment sessions across gateways. Meanwhile the API is being made safe for gated commerce: money fields are now typed string or null everywhere, because a prices_hidden channel returns null for every monetary amount including nested records. That is the SDK contract for the wholesale and gated-storefront work landing in 5.6.

◆ Prediction

Expect 5.6.0 to go stable with the React dashboard still labelled developer preview, and the SDK to keep its lockstep versioning — each minor stating the exact backend release it requires.

V6.3

Three maintained branches, one credential bug, and very little else moving.

◆ Current state

The feed is a patch stream across three concurrently maintained branches — 3.1007.x, 3.1039.x, and the 3.105x/3.1060 head — with the same defect frequently released to all three within minutes or backported days later. Entries are single-line bug references with issue numbers and no narrative. The null credential fields fix (#3100) is the current example: it shipped on the head branch on 14 August and reached both older branches on 18 August with byte-identical notes. Only 3.1060.0 carries anything distinct — a fix making the production error page reachable and renderable, and a PR description guide for contributors.

◆ Where it's heading

Engineering attention is concentrated on the caching and credential layers, not on new commerce capability. The parallel-branch release pattern indicates a customer base pinned across several versions, which constrains how much can change in any one release and explains a feed made almost entirely of backported fixes. The one non-patch item in this window is contributor documentation, which suggests the team is trying to standardize how changes are described rather than change what they ship.

◆ Prediction

Expect continued triplicate patch releases as fixes are backported across the three branches. Nothing in the entries indicates feature work on the head branch.

Alternatives to Spree Commerce and Virto Commerce

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 Spree Commerce or Virto Commerce.

See all Spree Commerce alternatives → · See all Virto Commerce alternatives →

Recent activity from Spree Commerce and Virto Commerce

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoVirto CommerceBackports the null credential fields fix (3.1007.25)
  2. 1d agoVirto CommerceBackports the null credential fields fix (3.1039.10)
  3. 1d agoVirto CommerceProduction error page fixed; PR description guide added
  4. 5d agoVirto CommerceFixes null credential fields (3.1059.0)
  5. 11d agoVirto CommerceFixes user cache corruption on update (3.1007.24)
  6. 11d agoVirto CommerceFixes user cache corruption on update (3.1039.9)
  7. 22d agoSpree CommerceSpree SDK 1.2.1: wishlist product data, sort labels
  8. 23d agoSpree CommerceSpree SDK 1.2.0: unsubscribe endpoints, nullable money fields
  9. 1mo agoSpree CommerceSpree 5.6.0.rc3: single-node Docker deploy by default
  10. 1mo agoSpree CommerceSpree 5.6.0.rc1: React Dashboard developer preview
  11. 2mo agoSpree CommerceSpree SDK 1.1.0: provider login and newsletter opt-in
  12. 4mo agoSpree CommerceSpree SDK 1.0.1: extensibility hooks and missing totals

Frequently asked questions

What is the difference between Spree Commerce and Virto Commerce?

They serve adjacent needs but don't currently overlap on shipped themes. Virto Commerce is currently shipping more aggressively (velocity 6.3 vs 5.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.

Is Spree Commerce better than Virto Commerce?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Virto Commerce is currently shipping more aggressively (velocity 6.3 vs 5.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.

What are the best alternatives to Spree Commerce?

Top Spree Commerce alternatives in E-comm are ranked by recent ship velocity. Browse the "Spree Commerce alternatives" section above for the current picks, or visit /alternatives/spree for the full list with editorial commentary on each.

What are the best alternatives to Virto Commerce?

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.