BigCommerce B2B Features: How to Set Up Wholesale Pricing and Customer Groups

BigCommerce can handle core wholesale selling without turning your store into a custom project. Customer groups support segmentation, discounts, and access control, so you can place approved buyers into wholesale groups, apply store-wide or category discounts, and hide products or categories from retail shoppers. That covers a large share of BigCommerce wholesale setups, especially if your pricing model is consistent across a dealer tier.

Setup complexity starts when pricing stops being group-based and becomes account-specific. BigCommerce supports multiple pricing tiers by customer context, but customer-specific pricing is a more complex B2B approach. In practice, that means customer groups alone are not always enough. Your implementation usually starts in Customers > Customer Groups, then moves into pricing rules and Products > Price Lists when a single discount percentage no longer fits every buyer.

This article stays focused on that decision path: customer groups for segmentation and visibility, price lists for more precise wholesale pricing, and B2B Edition when you need company accounts, quote and invoice workflows, buyer portal tools, sales rep masquerading, or other advanced control panel functions. BigCommerce B2B is practical once you separate native features from edition-specific ones, confirm what your plan includes, and test both storefront visibility and account assignment before launch.

Choose the right wholesale pricing model before you configure anything

Before you configure anything, map one question: does the price change by tier, by product, or by individual account. That decision determines whether customer groups are enough or whether you need a separate pricing layer.

1. Use customer groups when your wholesale pricing follows one tier-wide rule. In BigCommerce, groups created in Customers > Customer Groups can apply discounts store-wide or by category, and those same groups can also control access to products or categories. If your rule is “all dealers get the same discount” or “resellers see one restricted category,” customer groups are the cleanest build.
2. Use price lists when the discount cannot be expressed as one blanket group rule. Price lists are created under Products > Price Lists as a separate admin object, and BigCommerce supports multiple pricing tiers customized by customer context. If Tier A and Tier B need different numbers on the same SKU, start here instead of trying to force that logic through category discounts.
3. Use customer-specific pricing only for true contract business. BigCommerce treats customer-specific pricing as the more complex B2B pricing approach. That makes it the right fit for negotiated accounts, but the wrong starting point for a simple wholesale program.

Account structure can change the setup

BigCommerce B2B features change the design once you need company accounts and buyer workflows, not just discounted catalogs. B2B Edition adds its own toolset, including a default customer group setting, segmentation by factors such as order volume and company size, and workflows for quotes, invoices, buyer portals, and sales rep masquerading. If you sell to companies with approval chains or negotiated terms, map those account workflows first, then attach pricing to them.

The practical rule is simple: use customer groups for broad tiering and visibility control, use product-level pricing for structured multi-tier catalogs, and reserve customer-specific setups for exceptions. Test each segment with a real customer account before launch so pricing, tax behavior, and catalog visibility stay aligned.

Create wholesale customer groups and control who gets access

Create wholesale groups in Customers > Customer Groups, then name them by business rule, not by vague tier labels. “Wholesale US Resale,” “Wholesale Canada Taxable,” and “Distributor Restricted Catalog” are maintainable. “Tier 1” is not. BigCommerce customer groups do more than trigger pricing. They can also control access to products or categories and support tax-zone configuration, so the group name should tell your team exactly who belongs there and what rules apply.

1. Create the base group first. If your wholesale program is simple, start with one group and apply a store-wide or category-level discount. Split groups only when margin structure, tax treatment, or catalog visibility genuinely differs.
2. Review every wholesale registration before assignment. Collect company and resale details on the application, then approve manually unless you already have a reliable verification process. That prevents retail shoppers from landing in buyer groups that expose discounted pricing.
3. Assign approved existing customers to the correct group, then test the storefront with an actual login for that account. Confirm price display, category visibility, and tax behavior from the shopper side, because the control panel view will not catch merchandising mistakes.

Use default assignment carefully

B2B Edition adds advanced control panel functions, including a default customer group setting. Use it deliberately. A default group works for a gated wholesale portal where every new account should inherit the same rules. It creates risk on a mixed retail and wholesale storefront, because one bad default can push new signups into wholesale pricing automatically.

Know when groups are not enough

BigCommerce customer groups handle segmentation, discounts, and access control well. They are not the right structure for every negotiated account. Customer-specific pricing is the more complex B2B pricing case, and price lists are a separate admin object created under Products > Price Lists. If each account needs unique net pricing, use price lists or B2B Edition instead of creating dozens of groups that are impossible to maintain.

Set up wholesale pricing with customer groups, discounts, and price lists

For standard BigCommerce wholesale pricing, customer groups are the cleanest starting point. BigCommerce uses customer groups for segmentation, discounts at store-wide or category scope, and access control, and wholesale groups can receive discounts at store-wide or category scope. That makes them the right tool when every approved wholesale buyer should see the same baseline rate.

1. Create a wholesale group in Customers > Customer Groups. Name it by actual pricing logic, such as Wholesale 20 or Dealer Parts, so the rule is obvious six months from now.
2. Apply the discount at the broadest scope that matches your margin model. Use store-wide scope for one flat dealer discount. Use category scope when product families need different wholesale treatment.
3. Assign customers deliberately. One group per pricing model keeps administration clean and prevents accounts from drifting into the wrong rate structure.
4. Restrict catalog visibility if needed. The same group framework can also hide retail-only products or categories from wholesale buyers.

Use price lists when pricing varies by SKU, tier, or account structure

A flat group discount stops working once pricing varies by SKU, brand, or customer tier. BigCommerce treats customer-specific pricing as the more complex B2B approach, and price lists are a separate admin object under Products > Price Lists. Use that structure when one account needs negotiated item pricing or when your wholesale catalog requires multiple pricing tiers instead of one blanket percentage.

This is also where feature boundaries matter. BigCommerce offers B2B Edition as a separate app with its own toolset, and its documentation highlights company accounts plus order, quote, and invoice workflows, buyer portal features, sales rep masquerading, and advanced quoting. For many BigCommerce B2B stores, customer groups handle the basic discount layer, while price lists or B2B Edition become necessary once pricing is tied to companies rather than a simple wholesale segment.

Avoid pricing conflicts before they reach checkout

Most pricing problems come from overlapping methods, not from missing features. If you stack a group discount, SKU exceptions, bulk pricing, minimum-quantity logic, and promotional discount rules without a clear hierarchy, buyers will find inconsistencies fast. The practical fix is to keep one source of truth for each scenario: customer groups for broad eligibility, price lists for negotiated product pricing, and promotions for temporary campaigns. Test each wholesale account type with real logins, visible products, and representative quantities before launch.

If you also need automatic assignment for new business customers, tax handling by account type, or deeper segmentation by company attributes and order volume, B2B Edition provides more control, including a default customer group setting. Customer groups alone are enough for a standard wholesale discount. Negotiated, account-level pricing usually needs the more advanced layer.

Control storefront visibility so the right buyers see the right prices

Once you create a wholesale group in Customers > Customer Groups, pricing only changes when the shopper is matched to that customer context. BigCommerce uses customer groups for segmentation and discounts, and those discounts can apply store-wide or only to selected categories. The practical rule is simple: guests stay on retail pricing, while approved wholesale buyers must log in to see their assigned pricing.

Check every storefront touchpoint after setup. A logged-in wholesale buyer should see the wholesale price on category pages, product pages, cart, and checkout. A guest or standard retail account should see the retail price across the same path. If pricing changes on the product page but not in cart or checkout, the problem is usually storefront touchpoint behavior tied to group assignment, not storefront layout.

Use customer groups for access control, then escalate when the model gets more complex

Customer groups also support access control over products and categories, so they can handle basic catalog segmentation alongside wholesale discounts. That works well when one wholesale segment shares one discount structure. It stops being enough when you need customer-specific pricing. BigCommerce treats that as a more complex B2B pricing model, and price lists, created under Products > Price Lists, are the native tool for it.

If your requirement is login-required pricing, company accounts, or a distinct wholesale buying experience, customer groups alone are too limited. B2B Edition adds its own feature set, including company accounts, buyer portal functions, quoting, invoice workflows, and additional control panel capabilities. It also supports a default customer group setting. For merchants who want to hide pricing from retail shoppers entirely, native access restriction is stronger than trying to show the full catalog while selectively removing prices. In BigCommerce B2B, that distinction determines whether customer groups are enough or whether price lists and B2B Edition are the cleaner implementation.

Test the setup, troubleshoot edge cases, and know when B2B Edition is worth it

Customer groups in BigCommerce do more than apply a discount. They are used for segmentation, pricing differences, access control, and tax-zone configuration, so final QA has to happen from the storefront with real customer logins, not only from Customers > Customer Groups in admin.

1. Log in as each customer group and test the same 3 to 5 live SKUs. Use one standard item, one restricted item, one discounted item, and one high-volume SKU so you can verify visibility, product-page price, and cart price against the expected outcome.
2. Verify quantity pricing at the exact breakpoints you configured. Test one unit below the break and the breakpoint itself so tier errors show up before launch.
3. Check taxes with billing and shipping addresses that match your active tax zones. Confirm the total changes for tax treatment, not because the underlying item price shifted.
4. Submit a test wholesale application and confirm the approved account lands in the intended segment before the first order is placed.

If you use BigCommerce B2B Edition, validate the control panel’s default customer group setting with a real submission. A bad default puts new applicants into the wrong pricing and tax logic immediately, especially when broader B2B capabilities become necessary.

Catch pricing conflicts before customers do

Broad wholesale discounts can sit at store-wide or category scope through customer groups, while price lists are a separate admin object under Products > Price Lists and the more complex route for customer-specific pricing. That mix is where conflicts appear. Test one shared SKU across every relevant group, price list, and quantity tier before launch.

Troubleshoot by isolating the failure. If visibility is wrong, inspect the group’s access rules. If price is wrong, review the group discount or price-list assignment tied to that SKU. If tax is wrong, review the group’s tax-zone configuration before touching product pricing.

Know when native tools stop being enough

Native customer groups and price lists are enough for straightforward wholesale segmentation and negotiated pricing. They stop being enough when a single login no longer represents the account accurately, such as multiple buyers under one company, a shared catalog, quote and invoice workflows, or assisted ordering by your internal team. BigCommerce B2B Edition adds its own app layer plus documented workflows for company accounts, buyer portal access, quoting, invoicing, and sales rep masquerading. That is the tipping point: your process has moved from discount management into account structure and operational workflow.

Repeat this checklist after any catalog import, tax update, price-list change, or signup-flow edit. Wholesale issues rarely break every SKU. They break one group, one breakpoint, or one onboarding path, which is exactly why disciplined regression testing protects margin.

Set up wholesale pricing with a structure you can maintain

A maintainable setup starts with sequence, not features. First, decide the selling model: one wholesale tier, a few segment-based tiers, or customer-specific pricing. Then create the customer groups in Customers > Customer Groups, assign the right buyers, and apply the pricing layer that fits the model. Native customer groups handle segmentation, discounts, and product or category access control, so they work well for store-wide or category-level wholesale pricing. If your rules go account by account, use price lists, which BigCommerce manages as a separate admin object under Products > Price Lists.

That line matters because complexity compounds fast. Customer-specific pricing is the more complex B2B path, and it stays manageable only if the business truly needs it. If you just need a few discount tiers and restricted catalog visibility, native tools are usually enough. If you need company accounts, quote and invoice workflows, buyer portal features, sales rep masquerading, or advanced control panel functions, BigCommerce B2B Edition is the right upgrade. Its default customer group setting also helps standardize account onboarding.

Before launch, test every role with real login scenarios: pricing, hidden categories, tax behavior, and checkout. The winning setup is the one your team can update without rebuilding rules every month.