Open-source Ecommerce

June 12, 2026

Announcing Spree Commerce 5.5: Admin API, AI Agent Skills, and Sales Channels

Admin APIAI agentsHeadless Commerceopen source eCommercesales channelsSpree Commerce 5.5

Spree Commerce 5.5 makes building on the platform faster for humans and AI agents. A new Admin API with a fully-typed TypeScript SDK opens every back office operation to integrations. Sales Channels and smarter order routing help multi-channel sellers run everything from one backend.

Key Takeaways

Last verified: June 2026

Why it matters: Building on Spree Commerce gets faster and cheaper, whether the builder is human or an AI agent.

What you get: A new Admin API with a fully-typed TypeScript SDK for programmatic, headless store management.

The win: Agent skills turn coding agents into Spree Commerce experts delivering quality code at a fraction of the token cost.

Spree Commerce capability: Sales Channels plus Stock Reservations and rules-based Order Routing unlock omnichannel & multi-warehouse commerce.

Spree Commerce 5.5 Is About Speed for Your Team and Your AI Agents

Spree Commerce 5.5 arrives with 470+ commits on top of Spree Commerce 5.4, and almost every one of them serves the same goal: less friction between an idea and working commerce software. The 5.4 release rebuilt the customer-facing layer with the Store API and the Next.js storefront. This release turns to everything behind it.

Half of Spree Commerce 5.5 is for people. The other half is for the AI agents working alongside them.

What’s new	What it does	Who it serves
Admin API	Read and write every back office resource	Integrations, custom admin tools
Agent skills	Teach coding agents platform conventions	AI-assisted teams
CLI 2.1 with generators	Scaffold models and APIs in one command	Developers and agents
Upgrade tool	Walks version upgrades end to end	Existing stores
Sales Channels	Per-channel catalogs and order attribution	Multi-channel sellers
Stock Reservations	Hold checkout stock for a limited time	High-volume sellers
Order Routing	Rules decide which warehouse fulfills	Multi-warehouse sellers

The full changelog lives in the 5.5 release notes on GitHub. Here is why each piece exists and what it changes for you.

What Does the New Admin API Change for Your Back Office?

The new Admin API opens the other half of Spree Commerce to your code. Storefronts already had a modern REST surface in the Store API; the Admin API covers everything behind the counter: catalog, orders, customers, promotions, gift cards, webhooks, and settings.

It was one of the most requested additions of the past year, and the requests came from recognizable places:

• A wholesale seller syncing orders into a warehouse system
• A product team feeding catalog data from an ERP
• A SaaS company embedding commerce into its own dashboard, wanting a custom admin experience instead of a second login

The Admin API serves all three.

Permissions are explicit. When you create a secret key, you choose which resources it can read or write, so a fulfillment integration touches shipment data and nothing else. The authentication and scopes guide covers both secret keys for app-to-app integrations and token-based sessions for custom dashboards.

The heavy operations are covered too. Bulk updates (changing product status, assigning products to channels or categories, editing customers in groups) run as single database queries, so they stay fast on large catalogs. Draft Orders let your code compose a complete order with line items, addresses, and promotions.

One more thing: the same API powers the React admin dashboard in development for the next major release. Every endpoint you integrate against is already exercised by a real application, built by the core team with the same fully-typed TypeScript SDK you get.

Your Coding Agent Becomes a Spree Commerce Expert

Spree Commerce 5.5 introduces 25 installable agent skills that teach AI coding agents the platform’s conventions before they write a line of code. They work with Claude Code, Cursor, Copilot, Codex, and 60+ other agent tools, in new and existing projects alike.

The timing is no accident. The Stack Overflow 2025 Developer Survey found that 84% of developers use or plan to use AI tools in their work, up from 76% a year earlier. The same survey named their biggest frustration, cited by 66% of respondents: “AI solutions that are almost right, but not quite.”

That frustration is exactly what skills fix.

Most production stores use Spree Commerce as a library, so a coding agent never sees the platform source and guesses at internals, producing almost-right code. The skills close that gap with the core team’s know-how written down: how to extend models safely, how the APIs are shaped, how checkout and pricing work, how to upgrade without breaking customizations.

Skills activate automatically when your prompt touches their topic. They cut token usage by roughly 90% compared to letting an agent scan source code, because the answer is already written down. And since they live in your repository, every developer on the project gets them without any setup.

There is also a Claude Code plugin with a platform expert subagent and safety hooks that block destructive database commands before they run. The agentic development overview shows the whole toolbox, including a documentation MCP server for questions the skills don’t cover.

The bigger picture: McKinsey projects $3 to $5 trillion in global agentic commerce by 2030. Platforms that agents can learn and operate have the head start.

A Command Line That Does the Boring Work

The new CLI turns repetitive platform work into single commands. The earlier version was built for installing and evaluating the platform; CLI 2.1 makes it a daily driver for local development, with code changes picked up automatically inside the Docker stack.

Code generators are the centerpiece.

One command produces a new database model, a complete API resource with both Store and Admin endpoints, or an event subscriber wired to platform events for connecting external systems. The command line quickstart lists every command.

Generators matter twice as much in AI-assisted work. With 51% of professional developers now using AI tools daily (Stack Overflow 2025 Developer Survey), boilerplate is increasingly written by agents at token cost. A generator produces the same code instantly, on convention, and for free. The agent runs one command instead of writing two hundred lines.

The upgrade tool closes the loop. A single upgrade command walks a version upgrade end to end: it updates dependencies, runs pending migrations, then applies the version-specific data backfills from an upgrade manifest. What used to be an afternoon with a checklist becomes one command and a code review.

How Do Sales Channels Help You Sell Everywhere From One Backend?

Sales Channels let one Spree Commerce store run several distinct selling surfaces, each with its own product catalog, publication schedule, and order attribution. This has been one of the most requested capabilities for years.

A channel is wherever an order comes from:

• Online store plus point of sale. Keep retail and in-person orders separate for reporting and fulfillment.
• Retail plus wholesale portal. Show different catalogs and pricing to consumers and B2B buyers from one backend.
• Mobile app. Attribute mobile orders separately and track their conversion independently.
• Seasonal microsite. Run a limited-time catalog without touching your main storefront.

Every order is tagged with its channel automatically, so you can filter, report, and route fulfillment by channel. Products appear only on the channels you assign them to.

Each assignment carries an optional publication window. A product can go live at the point of sale today and in the online store next month, scheduled once and forgotten.

Channels complete a picture that started with Markets in Spree Commerce 5.4. Markets decide where you sell and in which currency; channels decide through which surface. Together they give multi-store sellers the control that used to require separate store instances.

Why Do Stock Reservations Matter During Peak Season?

Because the worst moment for a shopper to lose an item is at the end of checkout. Stock Reservations place a time-limited hold on cart items the moment a shopper enters checkout, so availability counts update for everyone else immediately.

Picture a limited drop with one unit left. Before 5.5, two shoppers could both pass the availability check, and one of them would fail at order completion after typing a shipping address and a card number.

That shopper rarely comes back.

With reservations, the second shopper sees the item as unavailable right away. No dead-end checkout, no support ticket, no refund.

The reservation window is configurable, and holds release automatically when a shopper abandons checkout. Reservations also play cleanly with Order Routing below: reservations protect a product’s total availability, routing picks the warehouse that fulfills it.

High-volume sellers asked for this for flash sales, seasonal peaks, and limited drops, and it now comes built into the open source core. Nothing to install, nothing extra to pay for.

Order Routing Sends Each Order to the Right Warehouse

Order Routing decides which stock location fulfills each order, driven by rules you can reorder, deactivate, or extend without touching platform code.

Three rules come built in:

• Preferred location ranks a staff-selected warehouse first
• Minimize splits prefers the location that covers the most of the cart on its own
• Default location breaks ties

The rules walk in priority order and produce a ranked list of locations; the top location packs what it can, and the rest spills over to the next.

Routing is scoped per channel.

Your wholesale channel can fulfill completely differently than your online store, which pairs naturally with the new Sales Channels.

For multi-warehouse sellers, this used to be custom-build territory. Expressing fulfillment preferences meant overriding core platform behavior and re-testing it on every upgrade. Now you write a small custom rule (proximity, refrigerated goods, customer tier), or replace the strategy entirely and delegate the decision to an external warehouse system. The custom order routing guide covers both paths with working examples.

What Has the Spree Commerce 5 Line Delivered So Far?

A steady expansion of what the open source core can do, release by release. Each capability below landed in the version noted and remains part of every release since:

• A rebuilt admin dashboard (Spree Commerce 5.0) and a rule-based promotions engine (5.1)
• Customer segmentation (5.2) and Price Lists for wholesale and contract pricing (5.3)
• The Store API, TypeScript SDK, Next.js storefront, Payment Sessions, and Markets for cross-border selling (5.4)
• The Admin API, AI agent skills, CLI generators, Sales Channels, Stock Reservations, and Order Routing (5.5)

The pattern is deliberate: complex capabilities arrive as native features of a headless eCommerce platform, not as plugins.

And it runs in production at scale. GoDaddy built a platform that powers 10,000+ stores on Spree Commerce. Maisonette runs a multi-vendor childrenswear marketplace with a Next.js storefront serving 65,000+ products. Vero connected the REST API to its mobile app to bring a full marketplace checkout to its users, with multiple vendors flowing into a single order. The 5 line is also the base the next major release builds on.

Enterprise Edition: When Commerce Is Mission-Critical

Everything announced above is part of the free, open source core. The Enterprise Edition adds the modules and guarantees that mission-critical operations need:

• B2B eCommerce: buyer organizations, approval workflows, and customer-specific pricing
• Multi-tenant eCommerce: hundreds of white-label storefronts on one infrastructure
• Multi-vendor marketplace automations: automated vendor onboarding and two-way store sync

All of it runs on the same platform you start with for free.

Around the modules sits the operational layer enterprises ask about first: enterprise security aligned with SOC 2 Type 2 and ISO/IEC 27001 standards, single sign-on, and audit logging. Add SLA-backed support from the team that builds the platform, a dedicated success manager, and long-term support for predictable upgrade cycles. The new Admin API makes the Enterprise Edition more connectable than ever: every back office workflow your ERP or warehouse system needs is now an authenticated API call away.

If your roadmap includes wholesale ordering, hundreds of storefronts, or a marketplace at scale, talk to the team about the Enterprise Edition.

Get Started With Spree Commerce 5.5

Spree Commerce 5.5 is free and open source, and the fastest way to form an opinion is to run it. Install it with a single command, then point your coding agent at the project and watch the skills load.

This release was shaped by what builders kept asking for: an API for the back office, agents that understand the platform, and selling surfaces that match how modern retail runs. If something feels off, open an issue. If something feels right, the core repository appreciates a star.

Quick links:

• Read the release notes on GitHub for the full changelog
• Add the agent skills for AI-assisted development to any project
• Already running the platform? The upgrade tooling walks you through
• Try the live demo storefront before installing anything
• Follow the public roadmap milestone to see what comes next

For enterprise requirements, wholesale ordering, or marketplace projects, get in touch with the team.

Frequently Asked Questions