Announcing Spree Commerce 5.4: A Complete Open Source eCommerce Stack for Any Developer

Spree Commerce 5.4 ships a complete open source eCommerce stack any developer can use: a production-grade REST API with a TypeScript SDK, a Next.js storefront ready to deploy, cross-border eCommerce in a composable headless architecture for any team. The entire customer-facing layer is TypeScript.

Key Takeaways

Last verified: April 2026

The developer story: A production-grade REST API with a TypeScript SDK and a Next.js eCommerce storefront ship as a single, deployable stack. Any developer who can make an HTTP call can build on Spree Commerce, regardless of their backend language.

The business story: Launch cross-border eCommerce, multi-vendor marketplaces, and B2B commerce with a smaller team, shorter time to market, and a fraction of the upfront investment that custom builds demanded a few years ago.

Why it matters: What once required well-funded teams and months of custom engineering is now a one-command install and some composable configuration. Spree Commerce 5.4 is not an incremental update. It is a composable foundation.

Quick Links:

Spree Commerce 5.4 Changes What You Can Build & How Fast You Ship It

Spree Commerce 5.4 ships a complete open source eCommerce stack: a typed TypeScript SDK over a REST API any language can call, a production-ready Next.js ecommerce storefront, and everything a team needs to launch cross-border eCommerce, multi-vendor marketplaces, or B2B wholesale portals. These are not separate pieces assembled from different releases. They were designed together, as a single experience, from API contract to checkout flow.

Postman’s 2024 State of the API report found that 86% of developers consider REST APIs easier to integrate than GraphQL alternatives, citing simpler tooling and broader language support. Spree Commerce 5.4 leans into that reality. The headless ecommerce platform is accessible to any team that can make an HTTP call or use a TypeScript SDK. Run one command and you have a working store.

That shift matters at three levels, and each one speaks to both the technical team building the project and the business team funding it.

Developer Experience: From Zero to Running in Minutes

According to the 2025 Stack Overflow Developer Survey, 82% of developers say they evaluate new tools based on how quickly they can get a working prototype running. Three additions in Spree Commerce 5.4 lower that barrier to near zero.

One-command scaffolding. A single CLI command sets up a configured project with the storefront, backend, and optional Docker deployment. The wizard asks what you need and generates the right setup. Optionally, start with sample data that includes products, multiple markets, and multi-currency pricing so you can see a working multi-market store from the first run.

Agents-native development. When you scaffold a new project, Spree Commerce generates AI agent documentation (AGENTS.md) and bundles complete offline documentation in markdown format. Open the project in your AI coding assistant and it understands the API-first architecture immediately. This is about developer productivity: your AI pair programmer knows the codebase before you write a single line.

Deploy anywhere. Multi-architecture container images (ARM and x86) published via GitHub Container Registry mean your development environment matches your production servers without configuration. Any cloud, any Kubernetes cluster, any local machine with Docker.

What that means for the business: your team evaluates the platform in an afternoon, not a quarter. The time between “should we look at this?” and “here is a working prototype” collapses to hours.

Any Developer Can Build on Spree Commerce Now

The TypeScript SDK wraps the entire Store API surface in a typed client with autocomplete and schema validation. For JavaScript and TypeScript developers, it feels native. For everyone else, the REST API itself is the interface. Any language that can make an HTTP call works without an SDK.

The Store API is designed to be simple, fast, and built on best practices. Idempotent requests, structured error and validation reporting, rate limiting, and multi-language and multi-currency support ship out of the box. OpenAPI 3.0 specs generate automatically with every release, so your API documentation is always current.

What that means for the business: your frontend team, your in-house engineers, your agency partners all work in the language they already know. Time to first working prototype drops from weeks to hours.

Spree Commerce is now a backend option for the React shops, the Vue agencies, the in-house product teams, and the developers who never considered open-source commerce because the learning curve was too steep.

The Next.js Storefront Ships Everything You Need to Go Live

The API alone would be useful. Paired with the TypeScript SDK and an open-source Next.js ecommerce storefront, it becomes something you can ship to production. The storefront is free, open source, and built with Next.js 16, React 19, Tailwind CSS 4, and TypeScript. Fork it, customize it, deploy it to Vercel with a single push.

This is not a demo. It is a production-grade application you can try right now. Here is what ships out of the box:

Maisonette, a curated childrenswear marketplace serving hundreds of brands across the United States, already runs on this exact combination in production: Spree Commerce backend powering a Next.js storefront with 65,000+ products.

How Does Spree Commerce 5.4 Handle Cross-Border eCommerce?

When Forrester reports that 67% of online shoppers have purchased from a foreign retailer, cross-border eCommerce is no longer an edge case. It is the baseline expectation.

Markets in Spree Commerce 5.4 bundle geography, currency, locale, and payment rules into a single configurable entity. Create a market for Germany with EUR, local payment methods, and German-language product content. Create another for the UK with GBP and different shipping rules. Your multi-region ecommerce runs from one instance with one admin panel.

A new Translations Center gives your team an admin overview of which products are translated in which languages, with bulk CSV import and export. Translate hundreds of product descriptions externally or with AI, then re-import in one step. Multi-currency CSV imports work the same way: set up prices for multiple currencies in a single file upload.

Orders now record which market and language they were placed in, so transactional emails arrive in the right language automatically. Combined with customer-specific price lists and per-market currency settings, Markets enable scenarios that previously required multiple store instances: region-specific promotions, local tax compliance, market-specific product availability.

An ecommerce operation running across 20+ EU countries can manage every market from the same admin panel. No separate deployments. No duplicated product catalogs. One backend, as many markets as the business requires.

EU Omnibus Directive compliance arrives with automatic 30-day price history tracking. When a product goes on sale, Spree Commerce records and surfaces the lowest price from the prior 30 days. Every promotion in every EU market meets the Directive’s requirements without manual tracking. Checkout consent management with translatable policy pages, multiple sitemap support for catalogs exceeding 50,000 URLs, and per-storefront robots.txt configuration round out the compliance package.

What that means for the business: you launch in new countries by configuring a Market, not by deploying a new backend. Your operations team manages dozens of countries from the same admin panel they use for one.

What Makes Spree Commerce 5.4 a Composable eCommerce Platform?

The platforms most teams chose five or ten years ago were not built for what payment providers, search engines, and CMS tools can do today. Spree Commerce 5.4 takes a different approach: the commerce layer handles products, pricing, cart, checkout, and orders, while purpose-built tools handle everything else. When a better option appears for any layer, you swap it without rebuilding.

Payment Sessions make this real for payments. One API surface handles Stripe, Adyen, and PayPal. 3D Secure, PCI compliance, and webhooks work the same regardless of provider. Start with Stripe for developer speed. Add Adyen for European volume. Layer in PayPal for buyer preference. Your storefront checkout code does not change when you swap providers. That is what composable means in practice: the freedom to change any layer without a platform migration.

As the European Central Bank noted in its 2024 report on payment innovation, “merchants increasingly demand the ability to integrate multiple payment service providers to reduce concentration risk and optimize transaction costs.” Payment Sessions are the answer.

MeiliSearch ships as the built-in search engine: typo-tolerant, faceted product filtering in single-digit milliseconds. The same experience that enterprise search vendors charge thousands per month to deliver, running on your own infrastructure. Need Algolia or Elasticsearch instead? Swap the search layer through a clean adapter without touching the rest of your stack.

A 2024 FIS Global report found that merchants lose an average of 2.1% of revenue to payment processing inefficiencies when locked into a single provider. Composable architecture is how you stop that leak.

What that means for the business: no vendor lock-in on any layer. Your finance team routes payments to the cheapest processor per region. Your product team upgrades search without a platform migration. Every integration is a choice you can revisit, not a commitment you are stuck with.

What the Spree Commerce 5 Line Has Delivered

Spree Commerce 5.4 caps a release series that has systematically expanded native capabilities across every layer of the commerce stack.

5.4 crowns the series with the production-grade REST API, TypeScript SDK, Next.js storefront, Payment Sessions, Markets, Translations Center, MeiliSearch, storefront-rendered transactional emails, and EU Omnibus compliance. The entire customer-facing layer is now TypeScript.

The cumulative picture is an open-source ecommerce platform that ships native support for B2B pricing, multi-currency commerce, provider-agnostic payments, and headless storefronts. Not through plugins, not through third-party extensions, but as part of the core product. Each release builds on the same codebase, the same API contracts, and the same upgrade path.

From Custom Builds to Out-of-the-Box: The Maisonette Story

When Maisonette launched in 2018, building a custom multi-vendor marketplace at their scale required a $15 million investment in engineering, infrastructure, and platform assembly. It was a path available only to well-funded marketplace businesses willing to commit months of development before serving their first customer.

Spree Commerce 5.4 changes the economics of that equation. The same eCommerce backend that Maisonette is using is now paired with a production-ready Next.js storefront, an official TypeScript SDK, and a REST API that any developer can call.

An ecommerce business with a small in-house team can go live with a curated multi-vendor marketplace in weeks, at a fraction of the upfront investment that building from scratch demanded even a few years ago.

Today, Maisonette serves 65,000+ products from hundreds of independent brands to customers across the United States. It is a real-world validation that Spree Commerce can power high-volume marketplace operations. Now any marketplace business can emulate that success at a fraction of the upfront and recurring annual cost.

The architecture that powers a $15 million marketplace build is no longer a $15 million build.

What Can You Build With the Full Spree Commerce 5 Platform?

Multi-Vendor Marketplaces

The Community Edition ships a marketplace starter module so you can evaluate the multi-vendor model before upgrading. Out of the box, it includes:

The Enterprise Edition adds the automations that make marketplace operations hands-off at scale:

B2B and Wholesale Commerce

Price Lists assign custom pricing by buyer organization, geography, or customer segment. Combine them for volume pricing, wholesale tiers, or region-specific rates. A wholesale ecommerce portal can run alongside your DTC storefront on the same backend, with completely separate catalogs, pricing, and checkout flows.

Nuherbs, a wholesale botanicals distributor, uses this exact setup. B2B wholesale and B2C consumer brands run under one roof, each with its own buying flows, price lists, and customer segmentation, all drawing from the same unified product catalog and inventory. The wholesale portal serves bulk buyers with negotiated pricing. The B2C storefronts target retail customers with a completely different checkout experience, all from one backend with zero duplication.

Multi-Tenant and White-Label Platforms

GoDaddy built a custom platform on Spree Commerce that powers over 10,000 stores with per-tenant isolation, custom domain mapping, branded admin experiences, and independent configuration, all from a single codebase.

Now you can build the same kind of platform with the Enterprise Edition’s multi-tenant module, without the custom engineering GoDaddy invested in. Less development, faster time to market, composable from day one, and low maintenance because every tenant shares one upgrade cycle. Whether it is a franchise network, a merchant SaaS, or a brand portfolio, that scale is now available out of the box.

Multi-Store Commerce

Operate multiple storefronts from one backend. Each store gets its own catalog, pricing, payment methods, and shipping configuration. Nuherbs runs exactly this way: a B2B wholesale portal and multiple B2C consumer brands, each with distinct buying flows and customer segmentation, all drawing from one shared catalog.

Combined with Markets for per-region localization, multi-store provides the infrastructure for brands expanding into new geographies or new business models without multiplying their operational complexity.

Spree Commerce Enterprise Edition

The Enterprise Edition adds the infrastructure, support, and security that mission-critical commerce operations require.

Enterprise Platform

Built on battle-tested open-source foundations with the operational capabilities enterprise teams expect:

Enterprise Support Services

Your success is backed by the team that builds Spree Commerce. Expert support, proactive monitoring, and direct access to engineers who know your platform inside out.

Enterprise Security by Default

Engineered to pass your security review. Built with security practices aligned with SOC 2 Type 2 and ISO/IEC 27001 standards so you can focus on growth, not compliance gaps.

If your use case requires enterprise infrastructure, dedicated support, or security compliance out of the box, talk to the Spree Commerce team about the Enterprise Edition.

Get Started With Spree Commerce 5.4

Spree Commerce 5.4 ships a complete open source eCommerce stack: the commerce engine, the REST API, the TypeScript SDK, and the Next.js storefront.

Every component is free, open source, and designed to work together. Install Spree Commerce with a single command, fork the storefront, and you will have a working commerce application in minutes. For enterprise requirements, reach out to the Spree Commerce team.

Quick Links:

Frequently Asked Questions

What does “complete open source eCommerce stack” mean?

A complete open source eCommerce stack includes the commerce engine, REST API, SDK, and a production-ready storefront in one coordinated package. Spree Commerce 5.4 ships all four layers together: the backend, a REST API any language can call, a TypeScript SDK, and a Next.js storefront ready to deploy. You install once and get a working store.

Can any developer use Spree Commerce without learning a specific backend language?

Yes. Spree Commerce 5.4’s REST API accepts standard HTTP calls from Python, Go, PHP, Java, or any language with an HTTP client. Postman’s 2024 State of the API report found 86% of developers consider REST APIs easier to integrate than GraphQL alternatives. The TypeScript SDK adds autocomplete for JavaScript teams, but the API itself is language-agnostic.

How does Spree Commerce compare to headless commerce SaaS?

Spree Commerce is self-hosted open source ecommerce with zero platform fees and zero transaction fees on any payment volume. SaaS headless platforms charge monthly subscriptions, take a percentage of GMV, and lock you into their payment stack. With Spree Commerce you own the code, choose your payment providers, and deploy on any infrastructure.

Is the Spree Commerce Next.js storefront production-ready?

Yes. The Next.js storefront ships with a full shopping experience: product catalog, faceted search via MeiliSearch, one-page checkout, Apple Pay, Google Pay, Klarna, customer accounts, multi-region URL routing, and SEO built in. Maisonette runs this architecture in production with 65,000+ products across hundreds of brands.

How does Spree Commerce’s REST API compare to GraphQL ecommerce alternatives?

The REST API returns flat JSON responses with selective field expansion, inspired by the patterns that made Stripe’s API a developer experience standard. No query complexity, no schema stitching, no over-fetching. OpenAPI 3.0 specs generate automatically with every release, so documentation stays current without manual effort.

Can I sell in multiple countries with one open source ecommerce platform?

Markets in Spree Commerce 5.4 bundle currency, language, payment methods, and shipping rules per country into one configurable entity. Forrester reports 67% of online shoppers have purchased from a foreign retailer. One admin panel manages every market with built-in EU Omnibus Directive compliance and a Translations Center for bulk product localization.

What does Spree Commerce 5.4 add to the Spree 5 release line?

Spree Commerce 5.4 adds the production-grade REST API, TypeScript SDK, Next.js storefront, Payment Sessions for provider-agnostic payments, Markets for cross-border eCommerce, MeiliSearch integration, storefront-rendered transactional emails, and EU Omnibus compliance. The entire customer-facing layer is now TypeScript.

Let's use Spree to build exactly what your business needs

Let's use Spree to build exactly what your business needs

facebook