A consumer storefront on a backend built for harder problems
The catalogue, search, checkout and payments that run business-to-business commerce also run a consumer store, without the company accounts and approval steps a shopper never needs.
What a consumer store needs, and where platforms usually run out
B2C ecommerce software has to do four things well: load a catalogue quickly, return the right product from a search, hold people through checkout, and take payment through whichever provider your market uses.
The trouble usually starts later. A promotion your marketing team wants needs logic the rule builder cannot express. A second market needs its own currency, language and tax treatment. A trade customer asks for an account and a price list. At that point most consumer platforms ask you to choose between a workaround and a replatform.
Products, variants, collections and assets in one model, with translations per market from one canonical record. Collections with filters let merchandising teams decide which products appear where, without filing a ticket.
Catalog search is included from the Starter plan, running on the Database search engine. Growth and above add the Typesense search engine, and Scale adds search analytics so you can see what shoppers looked for and what came back.
Take payment on one model through any provider that has a Vendure payment handler, or one you write, and charge at checkout or hold the authorisation and settle when you ship. Adding a second provider for a second market does not mean a second checkout.
Store credit from Starter, gift cards from Growth, both redeemable at checkout. Refunds and goodwill sit on the account as a balance rather than as a spreadsheet your support team keeps.
Currency, language, tax and fulfilment per market, on one deployment. Adding a country is a configuration, not a parallel stack. See brands and markets.
Built for volume, and for the team operating it
Volume it has already handled
Munch runs more than 10,000 payment transactions a day at peak on Vendure. The application layer is stateless and scales behind a load balancer, with job processing on separate worker processes you scale independently.
Search across the storefront and the back office
Shoppers search the catalogue; your team searches products, orders, customers, collections and assets from one entry point, on Growth and above. Read more on search and discovery.
One dashboard for the people running the store
Catalogue, orders, customers, promotions and content in the Vendure Dashboard, with access scoped to the brand or region each person runs. Details on operations and governance.
The systems around it, connected
Your team connects ERP, PIM, CMS, fulfilment and tax services through the GraphQL APIs and plugins, so stock and price changes reach the storefront without anyone re-keying them. See ERP and integrations.
A frontend your team owns
Vendure is headless. The storefront is a separate application talking to the GraphQL Shop API, which means your team chooses the framework, owns the codebase and ships a change without waiting on the commerce platform's release cycle.
There is no proprietary frontend runtime between you and what your customers see. A redesign is a frontend project, and it stays one.
Vendure will not make you pick between speed and control
70% faster rollout
SKYdeals
Replaced a rigid in-flight commerce stack and went live in a fraction of the time previous projects required.
20% more daily orders
Hans Kohler
Unified B2B and B2C onto Vendure and lifted daily order volume across both channels.
50% lower TCO
Flowtech
Moved off a legacy enterprise platform and cut total cost of ownership in half.
10K+ daily transactions
Munch
Runs thousands of payment transactions per day on Vendure at peak, reliably.
When a trade customer asks for an account
Most consumer businesses eventually take a business order. A retailer wants to stock you. A corporate buyer wants forty units on invoice. A wholesaler wants a price list and a purchasing manager who signs off.
On Vendure that is a configuration on the platform you already run: company accounts, agreed prices and approvals applied to those customers only, with one catalogue and one order record behind both audiences. You do not migrate, and you do not run a second system.
Shoppers keep a personal account, a card at checkout and their own order history. Nothing about the consumer experience changes when the business side is switched on.
Company accounts, several buyers under one account, contract prices and approval steps, applied only to the customers who need them. Contract pricing and approvals come with Scale. See B2B commerce.
Products live once. Each channel sets its own price and availability for the same canonical record. Prices per business customer come with contract pricing on Scale. See B2B and B2C together.
What consumer teams ask about Vendure
The customer model, and almost nothing else. B2C ecommerce treats the customer as one person with one basket and one card. B2B treats the customer as a company: several buyers, an agreed price, an internal sign-off step, and one order history for the whole business. Catalogue, checkout, payments and search are shared between the two, which is why one platform can run both. See B2B commerce for the business side.
Sometimes, and it is worth being straight about when it is not. If you sell a few dozen consumer products, will never need company accounts, and want to be live in a fortnight, a hosted store will cost you less and get you there faster. Vendure earns its place when you have outgrown what a themed template can express: custom promotion logic, several markets, an ERP that has to stay in the loop, or a business side arriving later.
Starter covers catalogue, checkout, payments, catalog search and store credit. Growth adds the Typesense search engine, gift cards and global search for your team. Most consumer businesses sit on one of those two. The pricing page lists what starts where.
Yes. Vendure exposes a GraphQL Shop API, so an existing frontend can be re-pointed at it rather than rebuilt. If you would rather start from something finished, the Vendure B2B Storefront ships a consumer experience on the same codebase from the Scale plan.
Each market has its own currency, language, tax rules and fulfilment, configured on one deployment. Products and content are translated from one canonical record, so you maintain the product once and each market reads it in its own language and price.
Plans are a flat monthly price with no charge on gross merchandise value, per order or per user, so the plan price does not rise when you sell more. Vendure Core is free under GPLv3 if you want to run the open-source framework yourself. See pricing and self-hosted commerce.
See your consumer store on Vendure
Try Vendure for 14 days with your own storefront and markets, or compare the plans to see which one also fits a business audience.
