The Vendure Technical Roadmap 2026: What's Coming and Where We're Headed

In this post I want to get into the specifics of what we're building: Vendure, the enterprise commerce platform, and how Vendure Core, the open source foundation it's built on, continues to grow alongside it.

So let's get into it. What are we actually building?

Vendure: The Enterprise Commerce Platform

What we have in the past been referring to as "Vendure Enterprise" will be known as simply "Vendure".

Vendure is the enterprise commerce platform without the trade-offs — built as one coherent, extensible backend. It is purpose-made for the complexity of enterprise and B2B commerce, with an architecture your developers actually want to build on.

Vendure's new capabilities are already available in early access. Our full public launch is coming later this year, but here's what early access customers are already building with. This is just the beginning — we have an extensive roadmap of enterprise capabilities beyond what's listed here.

SSO & Advanced Auth

Enterprise authentication is table-stakes, and getting it right matters. Vendure ships with full OIDC and SAML support out of the box, with complete integration between your identity provider and Vendure's user management.

We're also introducing powerful extensions to the Vendure Core permissions system that cover the more complex and stringent access control requirements that enterprises demand.

B2B Pricing

We've spent a lot of time working with enterprises to understand what B2B pricing actually looks like in the real world. Spoiler: it's messy. Every business has their own special way of handling it, and any solution that assumes a single model is going to fall short.

That's why we've built a flexible pricing engine that adapts to how your business actually works: price tiers, company-specific pricing, date-based price changes, price list import & export, and more.

Content Versioning

If you've ever worked on a large catalogue with multiple teams making changes, you know the anxiety of someone pushing something live that shouldn't be live yet. Content versioning fixes that.

With a complete draft & publish workflow, you can view the entire history of changes, see visual diffs between versions, and restore previous versions.

Organisational Hierarchy

B2B commerce doesn't happen between individuals — it happens between organisations with complex internal structures. Vendure models this natively: companies, divisions, buying groups, and the relationships between them.

This is the foundation that powers the features below — when a buyer submits a quote or an order needs approval, the system already understands who they are, what organisation they belong to, and what rules apply to them.

Quote Management

In B2B, the price on the page is sometimes more of a suggestion. A buyer with a big order wants to negotiate. That's just how procurement works. And right now, that negotiation happens over email, or in a spreadsheet that someone's sales rep maintains on the side. It's a mess. So we're building a proper RFQ flow — buyer submits their cart for a quote, sales rep adjusts the pricing, and there's a back-and-forth until both sides are happy. Accepted quote turns into an order. The whole thing is versioned so you can actually see what changed between rounds.

Approval Workflows

The other thing about B2B that's completely different to selling directly to consumers: a buyer wanting to place an order might not actually be authorised to. Spend over a certain amount and it needs sign-off from a manager. Or a VP. Depends on the company, the product, the business unit — every organisation has their own rules.

We're building approval workflows that handle all of that, including escalation when someone's ignoring their inbox. This plugs directly into quote management too, so a sales rep's custom pricing can require internal approval before it goes out the door.

How it all fits together

A question we've been getting a lot: how does Vendure relate to Vendure Core technically?

Vendure Core is the open source foundation: the framework, the APIs, the plugin architecture. Vendure builds directly on top of it. The enterprise capabilities ship as a set of proprietary modules that integrate seamlessly with Core through the same plugin and extension mechanisms that the community already knows.

This means two things: First, your existing knowledge and customizations carry over completely. Second, adopting our new enterprise capabilities is not a migration; it's an upgrade. You add enterprise capabilities to your existing Core installation through a commercial license.

As the enterprise platform evolves, improvements flow back into Core. Better APIs, performance optimizations, architectural refinements — the open source foundation gets stronger because the enterprise product demands it. That's how we have built Vendure Core over that past years to what is today.

Vendure Core: The Open Source Foundation

What you've known as "Vendure" — the open source commerce framework — will be referred to as Vendure Core. That's because it better reflects the low-level, building-block nature of what the project provides.

This does not imply any change to the project itself beyond the terminology that we'll use to refer to it.

The open source project is the foundation of everything. It's where we've built trust with the community, and it's where we'll continue to invest. Our contributor numbers keep climbing, and our past few releases have seen record numbers of both first-time and returning contributors.

Vendure Core continues to power real businesses at scale. And as the enterprise platform evolves, improvements flow back into Core — better APIs, performance work, and architectural refinements that benefit the entire ecosystem.

Our regular release cadence will continue: patches every month, minor releases every quarter.

As illustration of our commitment to Vendure Core, the upcoming v3.6 release will see several major and long-awaited features released, including API key support, multi-currency search results, and numerous improvements to our Dashboard.

How we prioritise open source work

I'd like to provide some transparency around how we will decide what features and fixes we will be giving priority to on the open source core.

Firstly, we've introduced a change to the issue system where feature requests will direct you to start a GitHub discussion thread. This cleanly separates bugs (issues) from new feature requests (discussions).

Once the discussion of a feature request has been created, we'll monitor the activity to decide how much weight to give it. So if you see a feature request that you want, make sure to upvote it!

In reviewing where the core team will spend its time, we'll balance community feature requests against the needs of the Vendure platform as a whole. Our primary focus is on pushing the platform forward, but popular community requests that align with that direction will naturally get prioritized. Features that benefit both Core and the broader Vendure ecosystem will always rise to the top.

For regular bug reports and fixes, we're always open for community contributions of course.

Community Plugins Ecosystem

To bring further clarity to what really constitutes Vendure Core, we've reviewed the current set of open source packages and identified that some of them have been misplaced. I'm talking about the third-party integrations covering things like payments, infrastructure services and cloud platform integrations.

Yes — these are important for the ecosystem, but they don't represent the actual core framework itself.

Therefore we are in the process of moving them over to a dedicated community-plugins repo, and from v3.6 they'll be published under the new @vendure-community npm org, and they will be decoupled from the Vendure Core version scheme.

Nothing else changes — still open source, still available as always, and we'll continue to support them. Day-to-day maintenance will be driven by the community, and we're actively looking for contributors to help steward individual plugins.

One exciting opportunity this opens up is that now we'll be better positioned to accept officially-backed community plugins that have external maintainers. For example, if your service can integrate with Vendure then we'd love to hear from you. With your expertise and our guidance, we can put in place trusted, well-maintained community plugin integrations that benefit the entire Vendure ecosystem.

What This Means For You

If you're building on Vendure Core today — everything you rely on is staying put. And as you grow, the enterprise features we're shipping are designed to slot right in when you need them.

If you're evaluating Vendure for an enterprise or B2B project — get in touch to find out more about what we're shipping very soon.

If you have a technology or service that would complement Vendure's growing ecosystem in the form of a community plugin, open an issue on the community-plugins repo and let's chat!