By Vendure

Vendure

What it does

Vendure is a headless ecommerce backend. It manages catalog, pricing, accounts, carts, checkout and orders while a separate storefront connects through its APIs. This makes it an option for a team building tailored B2B or B2C buying experiences with its own development capacity.

Free, open-source Vendure Core provides the commerce fundamentals. Paid Starter, Growth and Scale plans add increasingly complex B2B buying rules, with Enterprise on contract. Vendure Cloud is currently a closed beta for paid plans, so hosting and feature rights need separate decisions.

Category
Ecommerce
Last updated
Oct 20, 2026
Vendure · Editorial illustration
Conceptual editorial illustration of a product catalog branching to storefront channels, cart and fulfilled parcel.

Work at Vendure?

Help customers find accurate information about your software.

Manage this listing →

Find your fit

Who it is for

Vendure fits a merchant or implementation team that needs one backend for multiple storefronts, brands or markets and is prepared to design the storefront and integrations. Channels can organize those experiences while keeping a common commerce foundation.

A standard catalog and card-checkout operation may find enough in Core. If buyers need company-wide accounts, quote requests, packaging units, contract prices or procurement approvals, the paid tiers add those capabilities in stages. Choose by the actual buying workflow rather than by platform size alone.

Back to sections

The work it supports

Core capabilities

Core models products and variants, inventory, customers, orders, payments, shipping, promotions and tax. The admin dashboard lets staff maintain catalog and order data. Pilot a complete order with a small test catalog before committing a migration.

The Shop API serves storefront interactions while the Admin API supports back-office work. Teams can build a storefront or connect another frontend. Test authentication, checkout, price display and order handoff end to end.

Channels let a business serve several storefronts, brands or markets from one backend and configure currencies, languages, tax zones and shipping regions. Verify channel-specific catalog visibility, prices and admin permissions with test users; the vendor places finer brand or region record rules in Enterprise.

Developers can extend Vendure through plugins and custom fields, including changes to commerce logic and APIs. That flexibility also means the buyer needs ownership of code, deployment tests and upgrades; an extension is not a ready-made feature until configured.

Vendure Core can run on infrastructure the buyer controls with Node.js and a SQL database. Decide who operates uptime, backups, database migration and security updates.

Back to sections

Understand the offer

Pricing and getting started

Vendure Core is free under GPLv3 and has community support. Paid plans add direct vendor support and selected B2B capabilities. Review the open-source license and plugin exception with the team responsible for distribution and custom code.

The October 20, 2026 pricing page displays Starter at €199, Growth at €599 and Scale at €2,499 per month, with prices excluding VAT. It offers EUR/USD and annual/monthly controls; confirm the chosen billing period, currency, commitment and taxes in a written quote. The vendor says Starter has no percentage-of-sales, per-order or per-user fee.

Starter adds company accounts, quote requests, quick order, personal lists, store credit and catalog search. Growth adds hierarchy, managed lists, gift cards and packaging units. Scale adds contract pricing, order approvals, audit log, OIDC SSO and a B2B storefront. Enterprise adds further procurement and configuration capabilities by contract.

Vendure Cloud is described as a closed beta for paid plans, with general availability planned for Q1 2027. Paid plans include a base Cloud allowance, with possible usage charges beyond it. The paid-plan trial requires a card and lasts 14 days before charges can begin; verify cancellation timing and Cloud access before signing up.

Back to sections

Look a little closer

Before you choose

Use a synthetic catalog and customer to test product variants, a storefront cart, payment handoff, shipping/tax settings and an order in the dashboard. Then repeat on each intended channel to catch differences in catalog, currency and permissions.

Map the real B2B requirements first: company account, quote, packaging unit, contract price and approval. Match each to Starter, Growth, Scale or Enterprise and confirm whether the included storefront is needed. Avoid assuming a marketing page about the wider platform describes free Core.

For hosting, decide whether the team will self-host now or seek access to the Cloud beta. Confirm operational ownership, included Cloud resources, overage rates, support commitments and a migration path before budgeting. The planned Q1 2027 Cloud date is a vendor target, not current general availability.

Back to sections

4 distinct sources behind this profile. Research observed Oct 20, 2026. Features and offers can change.
View sources and research →

Help keep this profile useful

Spotted an outdated detail? Send the correction with a supporting source. A verified account is needed to submit.

Suggest a correction ↗