What Is Spree Commerce?
Spree Commerce is an open-source, headless eCommerce platform for building B2B, marketplace, and enterprise storefronts. It gives you a REST API, a TypeScript SDK, and a Next.js storefront as a starting point, and it does not charge platform fees. It fits teams that want to own their commerce stack and customize it in code, rather than configure a hosted SaaS store.
What "headless" means here
In a headless setup, the commerce engine and the customer-facing storefront are separate. Spree handles the backend concerns — products, orders, pricing, and the API that exposes them — while the frontend is whatever you build on top. Spree ships a Next.js storefront you can use as-is or replace.
This matters if you want a custom buying experience, multiple frontends (web, mobile, in-app), or a storefront that changes independently of the backend.
What it's built for
The platform positions itself around three scenarios:
- B2B — business buyers with account-specific catalogs and pricing. Spree documents price lists for this, so different customers or groups can see different prices.
- Marketplace — multiple sellers or tenants on one system. The site cites GoDaddy building a multi-tenant eCommerce solution on Spree.
- Enterprise / cross-border — larger operations that need to compose their own stack rather than accept a fixed feature set.
If your use case is a single small store with standard retail pricing, a hosted platform may get you live faster. Spree's value shows up when you need control, custom logic, or multi-tenant structure.
The building blocks
| Piece | What it does |
|---|---|
| REST API | The interface your frontend and integrations talk to |
| TypeScript SDK | Typed client for working with the API from JS/TS code |
| Next.js storefront | A ready frontend you can extend or swap out |
Because the API is the contract, you can connect other services — ERPs, CRMs, custom admin tools — without touching the storefront.
Why teams pick it
- No platform fees. The software is open source, so you aren't paying a percentage of sales to the platform. You still pay for your own hosting, development, and any third-party services.
- Composable. You assemble the stack layer by layer instead of accepting one vendor's bundle.
- Code-first customization. Changes happen in your codebase, which suits teams with developers.
What to check before committing
- Hosting and ops are yours. Open source means you run and maintain it. Budget for infrastructure and upgrades.
- Pricing and plan details. The site references a free trial, pricing, and upgrade paths, plus price-list documentation. Confirm current terms on the site rather than assuming a free tier covers production.
- Fit with your team. If you don't have developers who can work with a REST API and a JS/TS frontend, the flexibility becomes overhead.
A practical next step: clone the Next.js storefront, point it at a Spree instance, and place a test order end to end. That tells you faster than any feature list whether the headless model matches how your team works.