BigCommerce B2B Features: What Works Natively and What Needs Custom Work

Wholesale and distribution businesses evaluating BigCommerce almost always ask the same underlying question in different words: how much of our actual buying process does this platform handle without us paying a developer to build it from scratch. The honest answer is that BigCommerce, especially with its B2B Edition, covers more of the standard wholesale workflow natively than most competing platforms, but "more" is not "all," and the gap between native and custom is exactly where projects go over budget when nobody mapped it out in advance.

Start With Your Buying Process, Not the Feature List

Before comparing checkboxes, write down how your customers actually place orders today. A distributor selling to independent retailers through a sales rep with negotiated pricing has a very different requirement set than a manufacturer selling direct to other businesses through self-service ordering. BigCommerce's native tools fit the second case almost perfectly and the first case only partially. Knowing which one you are before you scope a project saves months of back-and-forth later.

What BigCommerce Handles Natively or Through B2B Edition

Customer Groups and Price Lists

Customer groups let you segment buyers (retailers, distributors, VIP accounts) and assign different pricing, product visibility, and shipping methods to each. B2B Edition extends this with unlimited price lists that can be assigned per company or per customer group, including bulk pricing rule uploads via CSV. This is one of the more mature parts of the native offering and covers the majority of standard wholesale pricing structures without custom code.

Tiered and Quantity Pricing

Volume discounts (buy more, pay less per unit) are supported natively at the product level and can be layered with customer-group pricing. A distributor can set "10 to 49 units at $8 each, 50 plus at $6.50 each" per SKU without a developer, and combine it with a specific price list for a major account.

Quotes

B2B Edition includes a native quoting workflow: a buyer or their sales rep can request a quote from the cart, a company user can convert an approved quote directly into an order, and quotes can be edited and reissued. For businesses whose sales process runs partly through negotiation rather than fixed pricing, this closes a gap that used to require a third-party app on most platforms.

Purchase Orders

Buyers can check out using a purchase order number as a payment method, which B2B Edition supports natively, useful for companies with net-30 or net-60 terms managed through their own accounts payable process rather than a card at checkout.

Company Accounts With Multiple Buyers

This is arguably BigCommerce's strongest native B2B feature. A single company account can have multiple authorized buyers (a purchasing manager, several employees who place orders against the company's account, and a company admin who manages user permissions), which mirrors how real B2B buying committees actually operate. Buyers see the company's negotiated pricing and shared order history rather than each starting from a blank retail account.

Basic Approval Workflows

B2B Edition includes configurable approval workflows for standard scenarios, for example requiring a company admin to approve orders placed by junior buyers above a set threshold. This covers common cases out of the box, though it is worth flagging early because the complexity ceiling on this one is lower than on the others below.

Tax Exemption Handling

Business buyers with valid resale or tax-exempt certificates can have exemption status applied to their account, and BigCommerce integrates with tax exemption certificate management providers to keep documentation current. This is handled natively at a level that satisfies most B2B sellers without custom tax logic.

Where Custom Development Is Actually Required

Complex Contract Pricing Rules

Native price lists handle straightforward per-customer or per-group pricing well. What they do not handle natively is highly conditional contract pricing: rules that combine customer tier, order timing (seasonal contract rates), specific product bundles, and rebate-style retroactive adjustments. If your sales contracts look like a spreadsheet with nested conditions, expect a custom pricing engine, typically built as a middleware layer that calculates final price and syncs it to BigCommerce via API, in the range of $15,000 to $40,000 depending on rule complexity, over 6 to 10 weeks.

ERP-Driven Pricing and Stock

Most established distributors run pricing, inventory, and customer data as the source of truth in an ERP (NetSuite, SAP, Microsoft Dynamics, Epicor) rather than in BigCommerce itself. Getting BigCommerce to reflect real-time or near-real-time ERP pricing and stock levels is an integration project, not a configuration task. Expect $10,000 to $50,000 depending on whether it is a one-way sync (ERP pushes data to BigCommerce nightly) or a real-time two-way integration handling order writeback, and 4 to 12 weeks of build and testing time. This is the single most common custom line item in the B2B projects we scope through BigCommerce development.

Advanced Approval Workflows

Multi-step approval chains (department head, then finance, then a spending-limit check against a budget that resets monthly) go beyond B2B Edition's native single-tier approval and typically require custom logic built against the B2B API, often as a middleware application. Budget $8,000 to $25,000 depending on how many approval tiers and conditional branches are involved.

Credit Limits and Terms Enforcement

BigCommerce supports purchase order checkout, but enforcing a hard credit limit at checkout (blocking an order that would push a company over its approved credit line, checked against real-time ERP or accounting-system balances) requires custom integration with your accounting or credit management system. This is a common request from distributors and almost always needs custom middleware, generally $10,000 to $20,000.

Custom Catalogs Per Account

Some B2B relationships require a specific customer to see only a subset of your full catalog (an exclusive product line, a contractually restricted assortment) rather than just different pricing on the full catalog. B2B Edition's catalog restriction tools cover simpler cases, but highly granular per-account catalogs at scale (hundreds of accounts, each with a distinct assortment) usually need custom logic layered on top, in the $10,000 to $30,000 range depending on account count and how dynamic the assortments need to be.

Punchout Integration

Punchout (allowing a business customer to shop your catalog from within their own procurement system, like SAP Ariba or Coupa, and push the order back through cXML) is not native to BigCommerce and requires custom development or a specialized punchout middleware provider. This is one of the more expensive B2B requirements, typically $20,000 to $60,000 per punchout system integrated, because each procurement platform has its own protocol quirks, and timelines run 8 to 16 weeks including the buyer-side testing cycle.

Native vs Custom at a Glance

Requirement	Native / B2B Edition	Needs Custom Work
Customer group pricing	Yes
Tiered quantity pricing	Yes
Quotes and PO checkout	Yes
Multi-buyer company accounts	Yes
Basic single-tier approvals	Yes
Tax exemption handling	Yes
Contract pricing with nested rules		Yes
ERP-driven live pricing and stock		Yes
Multi-tier approval chains		Yes
Credit limit enforcement		Yes
Per-account custom catalogs at scale		Yes
Punchout (cXML)		Yes

A Requirements Checklist to Take to Any Agency

Before you request a quote from us or anyone else, answer these questions. Any agency worth hiring should be able to map your answers directly to native features versus custom scope, and you should be suspicious of a quote that does not distinguish between the two.

1. How many distinct pricing tiers or customer groups do you need, and are any of your pricing rules conditional (seasonal, bundled, rebate-based)?
2. Where does your product and pricing data live today (ERP, spreadsheet, PIM), and does it need to sync in real time or is a nightly batch acceptable?
3. Do buyers need multi-level approval chains, or is a single approver-per-order sufficient?
4. Do you need to enforce credit limits at checkout, and if so, against what system?
5. Does every business customer see your full catalog, or do specific accounts need restricted or custom assortments?
6. Do any of your customers require punchout integration with their own procurement software, and if so, which platform?
7. What is your realistic timeline, and which of the custom items above, if any, could reasonably launch in a phase two rather than blocking initial go-live?

Answering these before your first agency call typically cuts weeks off the scoping process and prevents the most common source of B2B project overruns: discovering mid-build that a requirement assumed to be "standard" was actually custom. We walk prospective clients through a version of this exercise on every BigCommerce development engagement, and it is worth doing even if you end up building on a different platform through services like custom software development. You can see how this plays out on real projects in our case studies.

FAQ

Do I need B2B Edition, or does standard BigCommerce cover wholesale selling?

Standard plans include customer groups and basic price lists, which cover simple wholesale needs. B2B Edition adds quotes, purchase order checkout, multi-buyer company accounts, and approval workflows, which most established distribution businesses need once they have more than a handful of business accounts.

How long does a typical BigCommerce B2B implementation take?

A native-only implementation using B2B Edition's built-in tools typically takes 6 to 10 weeks. Add ERP integration or custom pricing logic and the timeline extends to 3 to 6 months depending on how many custom components are involved.

Can BigCommerce handle both our B2B and B2C customers on one storefront?

Yes. Customer groups let you serve retail and wholesale buyers from a single catalog and storefront, showing each group appropriate pricing and, with B2B Edition or custom catalog rules, appropriate product visibility.

Is punchout worth building if only one or two customers ask for it?

Usually not immediately. Given the per-integration cost, it typically makes sense once punchout-requiring accounts represent enough order volume to justify the investment, often when three or more major accounts require it or when a single account's volume alone covers the cost within a year.

If your buying process has requirements beyond what a feature list can capture, the fastest way to get a real answer is to walk us through it directly. Book a free 1-hour strategy call through our contact page and we will tell you honestly what is native and what is not.