Vendure

Vendure is an open-source e-commerce framework aimed at developers who want to build a custom online store or commerce backend rather than use a fully hosted product. It is headless, meaning it provides the commerce engine, catalog, orders, customers, promotions, tax, shipping, payments, stock, and channels, and exposes it through an API, leaving the storefront, the customer-facing site or app, entirely up to you. That API is GraphQL, a query language that lets a front end ask for exactly the data it needs. Under the hood, Vendure is built in TypeScript on Node.js using the NestJS framework, and it works with standard SQL databases such as PostgreSQL, MySQL, MariaDB, or SQLite. Because it is a framework rather than a turnkey store, Vendure is chosen by teams with development capacity who value control and customization over out-of-the-box simplicity.

The point of a headless framework like Vendure is flexibility. When commerce logic is separated from presentation and offered through an API, you can build any front end you like, a website, a mobile app, a kiosk, a marketplace, and change or replace it without touching the commerce engine. Vendure's GraphQL API and plugin architecture are designed to be extended, so teams can model unusual catalogs, custom pricing, complex B2B rules, or bespoke workflows that a rigid hosted platform might not allow. Being open source, it can be self-hosted and inspected, and the company also offers a managed cloud option for teams that prefer not to run it themselves. The trade-off is inherent: Vendure hands you power and control, and in return expects you to bring the engineering to design, build, host, and maintain the storefront and the surrounding stack.

The sharpest contrast is with a hosted platform like Shopify. Shopify is a software-as-a-service product: you sign up, and it gives you a working store, hosting, themes, checkout, an admin, an app marketplace, largely without writing code. It is fast to launch and low-maintenance, but you work within its structure and its limits. Vendure is the opposite trade. It is a framework you assemble and run yourself, or on its managed cloud, giving you deep control over data models, logic, and the front end, at the cost of needing developers to build and operate it. Shopify can be used headless too, but its core promise is the hosted, all-in-one experience, whereas Vendure is headless and developer-first from the ground up. The choice is the classic one: buy a hosted platform for speed and simplicity, or adopt a framework for control and customization.

Which side wins depends entirely on the situation, not on which is better in the abstract. A small merchant who wants to sell quickly, with no engineering team, is usually far better served by a hosted platform; fighting a framework to reinvent what Shopify offers out of the box would be wasted effort. A business with genuine engineering capacity and requirements that hosted platforms handle awkwardly, complex B2B catalogs and pricing, unusual workflows, tight integration with other systems, a need to own the stack, is exactly where a framework like Vendure earns its keep. The honest way to frame it: Vendure is not a Shopify replacement for everyone, it is a different tool for teams that need control and are equipped to wield it. Picking a headless framework because it sounds modern, without the engineering to support it, is how projects stall.

Vendure fits best when a team has real development capacity and requirements that a hosted platform cannot meet cleanly: sophisticated B2B commerce, unusual catalog or pricing models, multi-channel selling from one backend, deep integration with existing systems, or a strategic need to own and control the commerce stack. Using it well means treating it as a foundation to build on, leaning on its GraphQL API and plugin system to extend rather than fight it, and pairing it with the front-end, hosting, and operational work a headless architecture requires. It also means being clear-eyed about total effort: a framework shifts responsibility for building and maintaining the storefront onto your team, so the flexibility is only worth it if the requirements genuinely justify the engineering, and if the people to sustain it are actually in place.

The most common misuse of Vendure, and of headless frameworks generally, is choosing one when a hosted platform would serve better. A small store with no engineering team that adopts a framework often ends up slowly, expensively rebuilding features a turnkey product includes for free. Underestimating the ongoing work is another trap: headless means you own the storefront, the hosting, the upgrades, and the integrations, which is real, continuing engineering, not a one-time build. Teams also sometimes fight the framework, bending it against its architecture instead of using its plugin and GraphQL extension points as intended. And picking a technology for fashion rather than fit, headless because it is trendy, leads to over-engineering. The discipline is to adopt Vendure when the requirements and the engineering capacity genuinely call for a customizable, developer-first commerce backend, and to reach for a hosted platform when they do not.

Vendure's name evokes the French vendre, to sell, and the platform is an open-source, GraphQL-first headless commerce framework built on Node.js.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where vendure is a core concern: