Hosted vs Custom Buyer Portal: Which Should You Use?
Start with the hosted Buyer Portal.
BigCommerce runs and updates it, and you configure branding, features, layout, language and per-account access in the control panel. Fork the open-source Buyer Portal only when you need workflows, business logic or integrations the settings can't provide, and you have React developers to maintain the fork.
BigCommerce, updated automatically
Control panel settings
Store admin
You, from a fork
Code: UI, workflows, logic
React, Node.js, Yarn, Git
Hosted vs custom at a glance
| Hosted Buyer Portal | Custom (open-source) Buyer Portal | |
|---|---|---|
| Who runs it | BigCommerce manages and updates it automatically | You fork the open-source project and deploy it yourself |
| How you change it | Control panel: branding, feature toggles (Quotes, Order History, Account Management and more), layout, localization, per-account controls | Code: full control of UI, workflows, business logic and integrations |
| Updates | Applied by BigCommerce, with ongoing support | You choose when to merge and release upstream changes |
| Skills needed | Store admin | Node.js, Yarn, Git, React and JavaScript or TypeScript; a V3 API token with B2B Edition scope for advanced integrations |
| Best for | Most B2B stores migrating from the legacy experience | Stores with unique buying workflows, or a headless build |
Source: BigCommerce Buyer Portal overview. The custom portal is built with React, React Router, Material UI and Redux on the B2B GraphQL Storefront API.
How it loads on each storefront type
Stencil
Embedded through header and footer scripts and theme hooks.
Catalyst
Rendered on top of Catalyst; you wire up authentication.
Headless (self-hosted)
You deploy the open-source portal alongside your headless storefront.
The hosted version works on any storefront type, but the setup steps differ.
When a custom Buyer Portal is worth it
- Your buyers need a workflow the hosted settings can't express, such as a custom approval chain
- You're on a headless storefront and want the portal to match it exactly
- You need deep integrations inside the portal itself, not just in the back office
- You have a team, in-house or a partner, to maintain the fork and merge upstream updates
If none apply, the hosted portal plus CSS overrides and a CSV of text changes covers most needs (BigCommerce).
Setting the portal type
Enable B2B on the storefront
In the B2B Edition dashboard, open Storefronts, open the menu next to the channel and click Enable B2B.
Choose the Buyer portal type
Open Edit settings for that storefront and choose the Buyer portal type under Buyer portal settings.
On multi-storefront stores, each storefront has its own settings. See our multi-storefront migration service.
Hosted vs Custom Buyer Portal Questions
What's the difference between the hosted and custom Buyer Portal?
The hosted Buyer Portal is run and updated by BigCommerce and configured in the control panel. The custom Buyer Portal is a fork of BigCommerce's open-source project that you deploy and maintain, with full control over the code.
Can I customize the hosted Buyer Portal?
Yes, within its settings: branding, feature toggles, layout, localization and per-account access. You can also add CSS overrides in some areas and upload a CSV to change or translate text.
Does the Buyer Portal work with Catalyst?
Yes. The Buyer Portal renders on top of Catalyst, and you wire up authentication. Headless storefronts can run the open-source portal alongside the storefront.
What skills do I need for a custom Buyer Portal?
Node.js, Yarn, Git, and React with JavaScript or TypeScript. Advanced integrations need a V3 API token with B2B Edition scope. You also need someone to maintain the fork over time.
Not sure the hosted portal covers your workflows?
We compare your buying workflows with the hosted settings and tell you whether a custom portal is worth it.