A B2B customer portal is what separates a brand that takes B2B seriously from a brand that bolted wholesale onto a DTC store. Buyers logging into a B2B portal expect different functionality than DTC shoppers. They expect to see their company account, their authorised users, their purchase history across the entire company (not just their own account), their negotiated pricing, their open invoices, their credit terms, and the catalog filtered to what they're allowed to order. This is not optional in mid-market B2B. It is table stakes.
Shopify Plus has progressively built more of this into the native B2B feature set since 2024, and as of 2026 the implementation gap between B2B portal turned on and B2B portal operationally working has narrowed considerably. This piece is the walkthrough for setting up the customer portal: what the native feature covers, what needs configuration, the implementation order, and the places most brands get stuck.
What a B2B customer portal actually is
The B2B customer portal is the logged-in experience for B2B buyers. It is functionally the storefront equivalent of an enterprise account dashboard. The portal should cover six things: company account management (who in the buyer's organisation has access), purchase history (orders across all authorised users in the company), custom pricing (what this buyer pays vs the published price), open invoices and credit status (what is unpaid and what is approaching the due date), approved catalogue (what products this buyer can order), and self-service ordering (the ability to reorder, save lists, and request quotes).
In 2026, most B2B buyers expect these features as standard. The portal is not a differentiator. The absence of it is a deal-breaker.
What Shopify Plus B2B covers natively
The native B2B feature set in Shopify Plus 2026 handles the core portal functionality. Company accounts (multi-user accounts where one parent company has multiple authorised buyers). Role-based permissions (admin, location admin, ordering, view-only). Customer-specific catalogs (price lists and product availability per account). Custom pricing per account or per customer group. Quick order forms and reorder functionality. Order history per company across all authorised users. Net terms display and invoice access (we covered the net terms setup in our piece on net terms step-by-step).
What is not covered natively: deep custom layouts beyond the standard B2B theme template, advanced approval workflows above a configurable threshold, ERP-synced product availability (catalog filtering based on real-time ERP stock data), complex quoting workflows beyond simple request-for-quote.
Implementation steps
Five steps.
Step 1: Define the company structure
Map the customer organisations. For each major B2B customer: how many users will have access, what are the roles, what locations or business units exist, what permissions does each role need. This mapping needs to be done before any Shopify configuration because the portal structure mirrors the buyer's actual business structure.
For brands with 10-50 B2B customers, this mapping takes 1-2 days. For brands with hundreds of B2B accounts, it takes 1-2 weeks and is best done as a structured customer onboarding survey. The mapping output is a spreadsheet with one row per company, columns for users, roles, locations, and assigned catalog.
Step 2: Configure customer accounts and locations
Customers > B2B customers > Create company. For each B2B customer, create the parent company record. Add locations (if the customer has multiple ship-to addresses or business units). Add users with their assigned roles. The configuration is one-record-at-a-time in the admin, but bulk import is available via CSV for larger onboarding.
The locations feature matters more than most brands realise. If your B2B customer has multiple warehouses, retail locations, or business units, each one becomes a location under the parent company. Orders placed by users at a location ship to that location's address by default. The reporting and analytics roll up to the company level. The structure matches how the customer actually buys.
Step 3: Configure catalogs and pricing
Settings > Products > Catalogs. Create a default catalog (your full product range) and any restricted catalogs (limited subsets). Assign the appropriate catalog to each customer account. Configure price lists with the negotiated pricing for each account or customer group.
For brands with simple pricing (everyone gets the same wholesale rate), one catalog and one price list work. For brands with complex pricing (multiple tiers, contract-specific overrides, volume discounts), you'll have 3-6 price lists and as many catalogs. Past that complexity, custom pricing logic usually needs to move into middleware, which we covered in our piece on why Shopify Plus needs a middleware layer.
Step 4: Configure the storefront experience
For brands on a Shopify theme: enable the B2B section of your theme (most modern Plus themes have this). Customise the storefront sections that B2B customers see when logged in: the homepage variant, the navigation, the product grid layout, the cart, the checkout. For brands on Hydrogen: build the portal pages as separate routes (typically /account/dashboard, /account/orders, /account/quotes, /account/users).
The native Shopify B2B theme is functional but generic. Brands wanting a polished B2B experience usually invest 2-3 weeks in design and front-end work to bring the portal up to the same quality as their DTC storefront. This investment pays back in adoption: B2B buyers use portals that feel built for them and bypass portals that look like an afterthought.
Step 5: Test from the buyer side
Create test B2B accounts with different role permissions. Log in as each test user. Verify they see only what they should: their pricing, their catalog, their company orders, their permissions. The most common failure at this stage is role permission misconfiguration: a 'view only' user can place orders, or an 'admin' user cannot manage other users.
Test every permission combination at least twice. Test the buyer-side experience on mobile (50% of B2B portal usage is mobile in 2026). Test invoice access, order history, reorder flow, and quote requests. The full test takes a half-day and prevents most of the support tickets that arrive in the first month after launch.
Where the customer portal gets complicated
Three areas.
ERP-synced product availability. If product availability needs to reflect real-time ERP stock (typical for distributors), this requires either an inventory sync app or custom middleware. The native catalog system handles 'what products this customer can see' but not 'what's actually in stock from their assigned warehouse'.
Complex quoting workflows. The native request-for-quote feature is simple. If your business requires multi-step quotes with approval workflows, sales rep involvement, or complex pricing logic, you need either a quoting app or a custom workflow.
Multi-region B2B portals. If you operate across the US, UK, EU, AU markets with different pricing, products, and terms by region, the portal structure becomes more complex. The expansion store model handles this cleanly. The combined-store model can handle it but with more workarounds.
Where to start
For brands setting up a B2B portal from scratch, the sequence is: map the customer structure first (week 1), configure accounts and catalogs in Shopify (week 1-2), customise the storefront experience (week 2-3), test from buyer side (week 3), soft launch with 3-5 trusted accounts (week 4).
Most mid-market brands get to a working portal in 4-6 weeks. The portal then evolves over the next 3-6 months based on customer feedback. The biggest predictor of adoption is the buyer-side test discipline in week 3. Brands that test thoroughly launch portals that customers actually use. Brands that skip the testing launch portals that customers complain about.
Talk to our team if you want help mapping the company structure or implementing a custom portal on Hydrogen. The first conversation walks through the customer-side flow before any Shopify configuration starts.
What is a B2B customer portal on Shopify Plus?
The logged-in experience for B2B buyers, including company account management, purchase history, custom pricing, invoices and credit status, approved catalogue, and self-service ordering. Shopify Plus B2B handles the core portal natively as of 2026, with the implementation work focused on storefront customisation and operational integration rather than building portal features from scratch.
Does Shopify Plus include a B2B customer portal out of the box?
Yes. As of 2026, the core B2B portal is included in the Shopify Plus B2B feature set. Company accounts, role-based permissions, custom catalogs and pricing, order history, and net terms all work natively. The customisation gap is in storefront layout and ERP integration, not core portal functionality.
How long does it take to implement a Shopify Plus B2B customer portal?
2-3 weeks for a standard portal on a Shopify theme. 4-6 weeks for a custom portal on Hydrogen or with significant theme customisation. Add 1-2 weeks for ERP integration if real-time stock or pricing is required. Most mid-market brands launch a working portal in 4-6 weeks from kickoff.
Can a B2B customer have multiple users on Shopify Plus?
Yes. Company accounts support multiple users with role-based permissions: admin, location admin, ordering, view-only. Each user gets their own login. The company is the parent record. Orders placed by any user roll up to the company-level order history. This pattern is fully supported natively as of Shopify Plus B2B 2026.
What permissions can I set for B2B users?
Four standard role levels: admin (can manage users, locations, and orders), location admin (can manage orders for their assigned location only), ordering (can place orders but not manage users), and view-only (can see history but not order). Custom role configurations require either an app or custom implementation, but the four standard roles cover most mid-market needs.
Can different B2B customers see different products?
Yes. Customer-specific catalogs are a native feature. You create catalogs (subsets of your full product range), assign products and prices to each catalog, then assign each customer account to a catalog. Customers only see products in their assigned catalog. This is how brands handle restricted SKUs, contract-specific products, and channel-specific catalogs.
How does the B2B customer portal integrate with my ERP?
The native portal shows Shopify-side data: order history, customer-side pricing, products. For real-time integration with ERP data (live inventory, dynamic pricing, ERP-driven catalog filtering), you need either an integration app, an iPaaS connector (Celigo, Boomi), or custom middleware. The typical pattern is to sync ERP data into Shopify on a schedule rather than query ERP in real time from the portal.
What's the biggest mistake brands make implementing a B2B portal?
Launching without testing from the buyer side. Brands configure the portal in admin, look at it from the admin view, and call it done. The buyer experience is different. Role permissions, catalog visibility, pricing display, and order history all need to be tested by logging in as a real B2B user. Skipping this step almost always produces a portal that breaks for customers in ways the merchant never sees until support tickets start arriving.
A Shopify Plus Agency for Strategic Design & Advanced Engineering
Building something ambitious?
- A B2B customer portal is the logged-in experience for B2B buyers: company accounts, purchase history, custom pricing, invoices, open orders, approved catalog.
- Shopify Plus B2B handles the core portal natively as of 2026. Company hierarchies, customer-specific catalogs, negotiated pricing, and account-specific terms all work out of the box.
- The implementation gap is in customisation: the portal looks like a standard Shopify customer area unless you invest in the layout and component work.
- Typical implementation time: 2-3 weeks for a standard portal on a Shopify theme. 4-6 weeks for a custom portal on Hydrogen or with significant theme customisation.
- The most-missed feature is multi-user accounts with role-based permissions, which works natively but needs explicit configuration for each customer account.
- Pitfall: launching a B2B portal without testing the buyer-side experience. The portal works fine in the admin and breaks for the customer if user role permissions are configured incorrectly.
