Spree 5.6: the release where Spree goes B2B
Spree Commerce has always been the open-source choice for teams who want to own their stack. Version 5.6 points that stack squarely at wholesale: storefronts that require an account to enter or a login to see prices, customer-specific price lists, and an approval workflow for new buyers — plus pre-orders, a 50-language admin, and a deployment story that just dropped Redis from the requirements list.
The five changes that matter
Gated B2B storefronts
Sales channels can now require signup to access the storefront, or require login before prices are shown. Customer-specific pricing comes via Price Lists, and a wholesale portal app handles buyer applications with approval workflows. This is the whole B2B starter kit — gate, price, approve — without custom development.
Native pre-orders
Pre-order support with expected ship dates, configured at the variant level, including limited sales and drops. Stores selling upcoming or scarce inventory no longer need an extension for the basics.
Deployment without Redis
Background jobs can run on the primary database, so Redis and a dedicated worker instance are no longer required. Spree also reports Docker images roughly 40% smaller than 5.5. Fewer moving parts, cheaper small deployments.
An admin your whole team can read
The admin panel is fully localized in over 50 languages with RTL support, and each team member picks their own language. Transactional emails were redesigned and localized on both the operator and customer side.
Metafields that filter and sort
Metafields are now searchable and sortable in both the Store API and Admin API — custom product data can drive filtering and merchandising without touching core models.
Full details are in the Spree 5.6.0 release notes, along with the 5.5-to-5.6 upgrade guide.
The B2B detail everyone underestimates
A gated storefront changes the visitor's first question. On a retail store, people ask about sizes and shipping. In front of a login wall, a wholesale buyer asks harder things before committing: What are the minimum order quantities? How long is approval? Do you price-break at 500 units? Who do I talk to?
The gate that protects your prices is also the wall your next buyer bounces off — unless something on that page answers their questions.
That something is what Asyntai's AI chatbot for Spree does: one script in the storefront layout, answers generated from your own content — catalog, policies, wholesale terms, uploaded documents — in the visitor's language, around the clock. On a 5.6 gated channel it earns its keep at the exact moment of highest intent: the buyer deciding whether requesting an account is worth it. And because it is a front-end script, it upgrades with none of your Spree versions.
Frequently asked questions
When was Spree 5.6 released?
July 23, 2026, with 5.6.1 following on July 28. The matching JavaScript SDK releases (@spree/sdk 1.2.x) require a 5.6 backend for the new features.
Is the B2B functionality built in or an extension?
Built in at the sales-channel level: signup-gated access, login-to-see-prices, Price Lists for customer-specific pricing, and a wholesale portal app with approval workflows.
Do I still need Redis to run Spree?
Not as of 5.6 — background jobs can use the primary database, and a dedicated worker instance is optional. Larger stores can of course keep a separate queue if they prefer.
Does Asyntai work behind the login gate?
Yes. The widget is a script in your storefront layout, so it renders wherever your pages render — public, gated, or logged-in. Wholesale buyers can get answers before and after approval.
Opening a wholesale channel on 5.6?
Put an assistant in front of the gate. Asyntai answers buyer questions from your own wholesale terms and catalog — the difference between an account request and a closed tab.
Get Started Free See the Spree integration