Open-source Ecommerce

October 27, 2026

Announcing Spree Commerce 6: Open Source Marketplace and B2B Wholesale With AI Agents

AI agentsB2B wholesaleHeadless Commercemulti-vendor marketplaceopen source eCommercespree commerce

Spree Commerce lets you run a multi-vendor marketplace, B2B wholesale and cross-border omni-channel selling from one platform. Every feature is built in, and AI agents work in the store with your team’s permissions. You own the code and the data, host it anywhere and pay zero platform fees.

Key Takeaways

Last verified: October 2026

Why it matters: One platform runs your marketplace, B2B wholesale and cross-border omni-channel selling.

What it does: Every feature is built in, with no plugins to add.

What you get: AI agents plus REST APIs, a TypeScript SDK and a Next.js storefront.

Also included: A React dashboard you extend with your own screens.

The win: Your code and data stay yours, on any host you choose.

What’s different with Spree: Zero platform fees and no vendor lock-in.

Spree Commerce capability: Spree Commerce includes an open source marketplace, B2B wholesale and AI agent tools.

What’s in Spree Commerce, the open source marketplace and B2B platform

Every capability below is open source and built in. Each name opens its documentation.

The marketplace, B2B wholesale and AI agents lead the list.

What’s in it	What it does	Who it serves
Multi-vendor marketplace	Invited sellers list products and earn after your commission	Marketplace operators
Seller panel	Each seller runs products, orders and returns in their own app	Marketplace sellers
B2B company accounts	Companies with divisions, buyers and emailed invitations	B2B and wholesale brands
Catalogs and price lists	Decide what a company or customer group can see and pay	B2B and wholesale brands
Volume pricing	The price falls as the quantity rises	Wholesale sellers
Wholesale portal	A signed-in shop and quick order form for approved buyers	B2B and wholesale brands
AI agents	Claude, ChatGPT or any MCP assistant works with a person’s permissions	Store and operations teams
Agent skills	Coding assistants get Spree’s conventions and documentation	Developers
Markets	Currency, languages and tax treatment per region	Cross-border sellers
Taxes, customs and duties	Tax-inclusive prices, VAT numbers, tariff codes and duty lines	Cross-border sellers
Sales channels	Storefront, counter and wholesale portal, each with its own rules	Omni-channel retailers
Inventory and purchasing	Stock per location, purchase orders, suppliers and transfers	Operations teams
Delivery profiles	Delivery rules, live carrier rates and click and collect	Fulfillment teams
Payments	Charge at checkout, on dispatch or when staff decide	Finance teams
Returns, exchanges and claims	Each after-sale case follows its own steps	Customer service
Product catalog	Product types, custom fields, a media library and CSV import	Merchandisers
Promotions and gift cards	Rule-based offers, batch coupon codes and store credit	Marketing teams
Customers	Customer groups, tags and store credit balances	Sales and marketing
Reports	A report builder and saved reports on the home screen	Managers
Data privacy	Data copies, erasure, price history and cooling-off periods	Compliance teams
Staff roles	Permissions per role, starting from a ready-made set	Store admins
REST APIs	Store, Admin and Seller APIs with published specifications	Developers
TypeScript SDK	Typed clients for the Store, Admin and Seller APIs	Developers
Next.js storefront	An open-source Next.js shop you host and change	Developers
React dashboard	The admin app, extended with your own screens and cards	Developers
Webhooks and tracing	Signed event deliveries and OpenTelemetry tracing	Developers

The full changelog is in the release notes on GitHub. The sections that follow explain why each part matters.

An open source multi-vendor marketplace with seller onboarding, commission and payouts

You can launch a multi-vendor marketplace where invited sellers list their products, shoppers buy from several sellers in one checkout, and each seller is paid after your commission.

A marketplace grows when good sellers join quickly and stay because they are paid correctly. Each seller works in a seller panel of their own, with its own web address and sign-in. Sellers list products, pack orders, add tracking and start returns there.

Your team does not have to do that work for them.

What you control from the dashboard:

• Onboarding: marketplace seller onboarding invites a seller, gives them a checklist of requirements and approves them once they clear it.
• Product review: sellers submit products for review, and you approve or reject each one.
• Commission: charge different sellers and categories different marketplace commission rates, applied in the order you set.
• One checkout: a shopper buys from several sellers at once, and the purchase becomes one order per seller.
• Payouts: earnings are recorded after your commission, and scheduled seller payouts settle what you owe through your own books, above a minimum you choose.

Larger sellers connect their own systems through the marketplace Seller API, which has its own credentials. Developers can follow the guide to build a multi-vendor marketplace from an empty store.

Wholesale buyers get company accounts, catalogs and price lists on one B2B ecommerce platform

Your business customers buy as companies, each with its own range, prices and rules, on an open source B2B ecommerce platform.

A business customer is an organization, not a person. You set each one up as one of your B2B company accounts, and its orders, prices and addresses belong to the company.

They stay with the company when its buyers change.

• Companies and divisions: hold a business as a tree of the legal entity, its branches and buying offices.
• Buyers: existing shoppers join a company at once, and anyone else gets an emailed invitation.
• Catalogs: B2B catalogs per company decide what a company or customer group can see and the prices it pays.
• Volume pricing: wholesale volume pricing lowers the price as the quantity rises, per variant on a price list.
• PO numbers: require a purchase order number at checkout, and keep the buyer’s PO document on the order.
• Tax exemption: record VAT and business numbers, and review an exemption certificate before it applies.

Sales reps prepare draft orders at prices agreed line by line, and the buyer only confirms. On the storefront, a Next.js wholesale ecommerce portal gives approved buyers their own signed-in shop with a quick order form for large baskets.

A gated storefront lets you choose what visitors who have not signed in can see: everything, everything but prices, or nothing. Developers can follow the guide to build a B2B ecommerce store.

AI agents work in your store through an MCP server, within your team’s permissions

Your team describes a job in plain words, and an AI agent carries it out in the store. Much of a store team’s week goes on repeated tasks, such as retyping a supplier’s spreadsheet into products and adding new products to the right collections.

You connect AI agents for your ecommerce store on the AI agents page in Settings. Paste the store’s address into Claude, ChatGPT or any other assistant that speaks MCP, the open standard assistants use to work with other software. Then sign in and approve what it may do through the ecommerce MCP server.

Once connected, an agent uses the MCP tools for store operations to:

• Merchandise: add products to collections, catalogs and price lists, publish or archive products, and add images.
• Import and export: take a CSV file you give it, propose how its columns map, run the import and export records.
• Cancel orders: cancel an order, which voids its payment and puts the stock back.
• Manage stock: set stock levels and move stock transfers and purchase orders to their next stage.
• Review accounts: verify a tax exemption certificate, or reject or suspend a seller.
• Answer questions: report net sales, orders and units sold for the dates you give it.

One message can combine several of these jobs: import the supplier’s CSV file, add the new products to the autumn collection and the wholesale price list, then publish them.

An agent never gets more than the person who approved it.

It sees only the tools that person’s rights allow. Every change runs through the same step the dashboard runs, so the same checks apply. The MCP server permissions and consent page explains how access is taken back, and paying sellers or erasing personal data are never offered to an agent.

Cross-border ecommerce runs from one store, with markets, taxes and duties per country

Entering a new country means adding a market, not opening a new store, on a cross-border ecommerce platform. You group countries into markets with their own currency, language and tax, and shoppers whose country you cannot tell go to the market you choose.

• Tax-inclusive prices: show prices with tax inside them where shoppers expect it, and add tax at checkout elsewhere.
• Tax by address: choose whether tax follows the shipping or the billing address in your ecommerce tax settings.
• VAT numbers: record a business buyer’s VAT number so invoices carry it.
• Customs details: add a tariff code, a country of origin and a plain description to each product variant.
• Duties: add customs duties on cross-border orders as their own line, and decide who pays duties on arrival.

Selling across borders is often selling across channels too.

Ecommerce sales channels let one installation serve a storefront, a counter and a wholesale portal. Each channel has its own catalog, its own access rules and its own fulfillment locations.

Ecommerce inventory management covers purchase orders, suppliers and stock transfers

Running out of stock loses sales, and paying for goods that never arrived loses money.

Ecommerce inventory management in Spree Commerce shows what you hold at each location: on the shelf, promised to orders, held in checkout, still sellable and on its way.

• Purchase orders: purchase orders for restocking carry the supplier’s promised date and a cut-off date, and stock is received against the order.
• Suppliers: a supplier directory shows who you buy from, with a count of what has been ordered from each.
• Stock transfers: stock transfers between locations are received in batches, with damaged units refused and a reason recorded.
• Stock history: every movement that changed a count is listed with what happened and why.
• Held stock: a unit is held while a shopper checks out, so the last one is not sold twice.

If a warehouse or ERP system is your record of stock, it can answer availability for the store instead. Developers can read the inventory model for developers before connecting one.

Shipping, payments and returns each follow their own rules per order

Delivery costs vary by product, place and basket, so delivery rules sit with the products they apply to. Ecommerce delivery profiles group products that are delivered the same way, with their own dispatch locations, delivery areas and methods.

• Conditions: offer a delivery method only within an order value, weight or volume range, on chosen sales channels or for company orders.
• Live carrier rates: show real carrier prices at checkout through your own carrier account, including contracts you negotiated.
• Click and collect: let shoppers pick up in person from the locations you choose.

You set payment methods and capture timing: take the money at checkout, on dispatch or when staff decide.

Charging on dispatch avoids refunds for goods you could not send.

After the sale, ecommerce returns and refunds each follow their own steps. A return is counted line by line and refunded to the card or as store credit. Order exchanges show the price difference, and a claim for a damaged, missing or wrong item is settled with money back, a replacement or both.

Prepaid return labels are bought on your carrier account and credited back if the return is called off. Watch returns, from request to refund to see it end to end.

Product catalog management, promotions and customer data sit in one dashboard

Merchandisers, marketers and sales teams work from the same records in product catalog management.

• Product types: product types and custom fields give new products the right fields, options and categories.
• Collections: pick products by hand, or keep rule-based product collections up to date automatically.
• Media library: upload pictures and video once and reuse them across products.
• Import and export: product CSV import and export matches your own column names and lists failed rows to retry.

Promotions are built from conditions and outcomes: a percentage or an amount off, free delivery, or an item added to the basket. Ecommerce promotions with coupon codes can generate a batch of single-use codes with your own prefix, and gift cards carry their balance over.

Your customer data management brings customer groups, tags and store credit together on each customer page.

Customer groups then decide which prices and promotions each segment sees.

A React admin dashboard with reports, staff roles and data privacy tools

The React admin dashboard opens on store performance: sales, orders, average order value, units and customers for any period, with the previous period beside it.

A command palette reaches any screen or record from one box.

• Reports: build ecommerce sales reports from sales, product and customer measures, save them and open them from the home screen.
• Staff roles: decide what each role can see and change with staff roles and permissions, starting from a ready-made set.
• Data requests: answer a request for a copy of someone’s data in one click.
• Erasure: remove someone’s personal details while orders, payments and balances stay intact.

The GDPR data privacy tools also keep price history, so the store can show the lowest price of the last 30 days beside a reduction. Each region holds its own statutory cooling-off period, separate from your own returns policy.

Developers get a headless ecommerce platform: REST APIs, a TypeScript SDK and a Next.js storefront

Your engineering team builds the customer experience it wants on a headless ecommerce platform, instead of working around someone else’s templates. Every part of the store is reachable through three REST APIs, each with a machine-readable specification generated from the code.

• Store API: the Store REST API for headless commerce serves storefronts, mobile apps and any other client.
• Admin API: the Admin REST API does everything the dashboard does, for your ERP, PIM and back-end jobs.
• Seller API: marketplace sellers connect their own systems with their own credentials.

The TypeScript ecommerce SDK gives typed clients for all three, so integration mistakes surface at build time rather than in production.

The open source Next.js eCommerce storefront is a production starting point you host and change, built on that SDK. The Next.js eCommerce storefront quickstart covers setup and deployment.

The admin is a React dashboard your team extends with its own screens, navigation entries, table columns and cards, from a package of your own. Ecommerce webhooks tell your other systems the moment something happens, with signed deliveries you can read and re-send. An OpenTelemetry package traces every request, job and webhook delivery once it points at your collector.

AI coding assistants start with Spree’s conventions too.

A new project can install AI agent skills for ecommerce developers and connect the assistant to the Spree documentation.

Enterprise Edition adds governance features and three modules: marketplace, B2B and multi-tenant

Enterprise Edition adds features for larger teams and three modules, each licensed separately: Multi-vendor Marketplace, B2B eCommerce and Multi-tenant eCommerce.

Enterprise Edition features:

• Company roles: a customer’s own administrator decides what each of its buyers can see and do.
• Order approvals: an order waits for a manager’s approval before it is placed.
• Spending limits: a cap per buyer or per company, above which an order needs approval.
• Approval history: a record of who approved what inside the buying company.
• Buyer access rules: the company directory, address book, member list and order history follow each buyer’s permissions.
• Admin audit trail: a record of who changed what in the store, and when.
• Encryption: data is encrypted in transit and at rest.
• Data privacy process: the steps and records a business needs to show how it handled each data request.
• Support: help from the team that builds Spree Commerce.

The Multi-vendor Marketplace module adds automation for large marketplaces:

• Refund recovery: when a refund comes after a seller was paid, the amount is taken back from the seller automatically.
• Payout reconciliation: what your ledger says each seller earned is checked against what the payment provider paid.
• Seller checks: seller identity checks and account health reviews.
• Payout reporting: seller earnings reports, including DAC7 reports for EU tax authorities.
• Marketplace tax: tax is collected and paid where the law makes the marketplace responsible for it.
• Seller store sync: sellers keep working in the store platform they already use, with products, orders and tracking synced both ways.
• Category mapping: imported seller products land in your own categories automatically.

The B2B eCommerce module adds the tools for buying on account:

• Payment terms and invoicing: net terms, credit limits, numbered invoices, outstanding balances and payment reminders.
• Formal offers: a buyer requests a price, you send a formal offer, and the accepted offer becomes an order.
• Buyer portal: members and roles, an approvals inbox, spending reports, addresses, orders and invoices in one place.
• Company registration review: a company that registers itself waits for your review before it can buy.

The Multi-tenant eCommerce module runs separate tenants, each with its own data, dashboard and storefront, on one installation.

To discuss which modules you need, talk to our team about Enterprise Edition.

Try it in the sandbox or install it with one command

To see it first, open the free open source ecommerce sandbox: a ready store in the cloud, with nothing to install.

When you are ready to build, run the one-command ecommerce install. It sets up the server, the dashboard and the Next.js storefront in one project, and you host it wherever you choose. The installer also offers to set up AI coding agents with Spree’s conventions. There is no trial period and no platform fee.

Already running Spree Commerce? The upgrade guide lists the steps.

Quick links to go further:

• The release on GitHub, with every change listed.
• The Spree Commerce changelog, updated with each release.
• Build a multi-vendor marketplace step by step, from an empty store to the first seller.
• Connect an AI agent to your store in a few minutes.
• Free cloud test stores for ecommerce, explained.

Planning a large marketplace or B2B rollout? Contact our ecommerce team.

Frequently Asked Questions