Fork it, theme it, or lift only what you need
Most enterprise B2B teams hit the same wall. Headless backends hand you primitives and a 12-month roadmap. All-in-one suites hand you a templated storefront with no control over flows, checkout logic, or branding.
The storefront ships as a production-ready Next.js app with every B2B flow already wired to a customer-facing surface. A buyer-ready storefront in weeks, on a codebase your team owns.
The full B2B procurement surface, in a customer-facing app
The Shop API and a Next.js starter give you the foundation. The storefront cards below are the production-grade B2B surface built on top of it: every procurement flow wired to a customer-facing app, ready to fork.
Shop API and a Next.js starter
The headless Shop API covers cart, checkout, accounts, and sessions. A public Next.js starter gives you the foundation to build from. The cards in this section are the production-grade storefront built on top of it.
Company accounts and permissions
Customer companies with hierarchical units, users, and company-scoped roles. Permission gates on every storefront action: request a quote, place an order above a spending limit.
Quote-to-order
Buyers request quotes from the catalogue. Sales negotiates over a multi-version thread. The accepted quote becomes an order with the negotiated prices locked in.
Approval workflows
Spending limits, named approvers, multi-level chains, timeouts. Buyers see pending approvals in their account. Approvers act from email or the storefront.
Quick-order and CSV upload
Paste a SKU list or drop a CSV. The storefront validates against the catalogue, resolves contract pricing, flags out-of-stock lines, and adds the rest to the cart.
One codebase, multiple business models
The storefront ships reference scenarios on one codebase (a B2C default, a B2B wholesale variant, and specialised verticals), configured rather than maintained as separate forks.
A production-grade stack your team can own
It is your codebase to fork, theme, and restructure. Treat it as your day-one storefront, or lift only the patterns you want into one you already run. No proprietary frontend runtime between you and the UI.
The underlying stack is a modern one your team can hire for:
- Next.js 16 + React 19: the supported reference application shell.
- TypeScript: end-to-end, across components, data, and route handlers.
- GraphQL via
gql.tada: type-safe queries generated against your Vendure schema. - Shadcn + Radix: accessible, themeable UI primitives you own in-tree.
- Tailwind: styling without a bespoke design-token runtime.
next-intl: first-class internationalisation for multi-market storefronts.
Built on real enterprise B2B implementations
Every flow in the storefront is a production-grade implementation. Each maps onto what real B2B operators put in front of buyers:
- Quote threads: multi-version negotiation with internal and external comments.
- Approval routing: spending limits, named approvers, multi-level chains, timeouts.
- Quick-order validation: SKU and CSV lines resolved against catalogue and contract pricing.
- Multi-step checkout: split addresses, PO references, and customer-group pricing.
The storefront codifies the B2B flows teams otherwise rebuild from scratch, so you start from a working implementation instead of a blank app.
Trusted by complex B2B commerce and enterprise retail.
One storefront across every capability area
The storefront is where every capability area on Vendure Platform lands in front of a customer. One application, every category:
- B2B workflows: company accounts, approvals, and the quote-to-order surface.
- Pricing and promotions: resolves the price on every line.
- Search and discovery: powers the catalogue and faceted browsing.
- Operations and automation: checkout durability and integrations.
- Governance and compliance: identity and audit underpinning every action.
What digital commerce leaders ask before they commit
Common questions from Heads of Digital Commerce and VP eCommerce evaluating Vendure for a real B2B storefront.
