Start with a complete buying experience, without a template ceiling
Most B2B teams hit the same wall. A fixed template puts a ceiling on buying flows, checkout, and brand experience. Starting from an empty frontend means rebuilding company accounts, quotes, approvals, reordering, search, and checkout before customers see any improvement.
The Vendure B2B Storefront gives your team a complete starting point while keeping the result in your control. Adopt the whole storefront, change any part of it, or use the same headless APIs from a frontend you already run.
The full B2B procurement surface, in a customer-facing app
Everything a buyer at one of your customers needs to do, already working in the storefront. Each flow connects to the platform capability behind 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.
Catalogue, search, checkout
Buyers find products fast with filtered search in their language, see live stock, and check out with split addresses, purchase-order references, and their own negotiated prices.
Your brand, your experience
The storefront is not a locked template. Your team changes anything: layout, checkout steps, wording, whole pages. What your customers see is decided by you, not by the platform.
One codebase, multiple business models
The storefront supports B2B and B2C experiences on one codebase, configured rather than maintained as unrelated builds.
Under the hood: a stack your engineers will vouch for
One section for your technical team, because they will be asked. The storefront is a Next.js and React application, written in TypeScript end to end, talking to Vendure's GraphQL API with generated type-safe queries. UI primitives (Shadcn, Radix) and styling (Tailwind) live in your repository, with first-class internationalisation for multi-market storefronts.
What that means for everyone else: it is mainstream technology your team can hire for, there is no proprietary frontend runtime between you and your customers, and the whole thing is yours. Adopt it as your day-one storefront, or lift only the flows you want into one you already run.
Teams building complex commerce with Vendure.
One storefront across every capability area
The storefront is where every capability area of Vendure lands in front of a customer. One application, every area:
- B2B buying: company accounts, approvals, and the quote-to-order surface.
- B2B pricing and catalogues: resolves the price and commercial terms on every line.
- Search and discovery: helps customers find products and operators find records.
- ERP and integrations: checkout durability, payments, and data flows.
- Brands and markets: one storefront shell across brands and regions.
- Operations and governance: identity and audit underpinning every action.
What teams ask before they commit to a storefront
Common questions from digital commerce leaders and their engineers evaluating the storefront.
