BigCommerce Review

BigCommerce is a hosted commerce platform, but treating it simply as another website builder understates what it is designed to do. The more interesting use case is when the storefront is only one layer of a larger commerce operation. A business can run multiple customer-facing storefronts, organize different customer groups and pricing rules, integrate external systems, or use BigCommerce as the commerce engine behind a custom frontend.

That distinction matters as a business becomes more complicated. A merchant may begin with one catalog and one audience, then add a second brand, a wholesale channel, regional storefronts, customer-specific pricing or a headless frontend. BigCommerce is structured so those additions do not necessarily require separate commerce backends for every new customer experience.

An overlooked part of evaluating BigCommerce is therefore operational consolidation. Multi-Storefront is designed to let merchants manage several storefronts from a common control environment, while Price Lists can be assigned using both a customer group and a storefront channel. B2B Edition extends the same model further with company accounts, buyer permissions, quotes and purchasing workflows.

The trade-off is that this architecture becomes more valuable as complexity grows. A merchant operating one straightforward catalog may never need much of it. BigCommerce becomes considerably more distinctive when pricing, buyer types, storefronts or integrations begin multiplying.

A BigCommerce store starts with a central control panel where the merchant manages products, orders, customers, payments and storefront configuration. For a conventional setup, the business can use BigCommerce's hosted storefront and configure the catalog, checkout and payment provider without maintaining the underlying commerce infrastructure.

The workflow becomes more interesting once additional sales experiences are introduced. A merchant can create separate storefront channels for different brands, regions or audiences while continuing to manage the commerce operation centrally. Products do not have to behave identically everywhere: Price Lists can be assigned according to channel and customer group, allowing the same underlying product to participate in different pricing strategies depending on where and to whom it is being sold. BigCommerce's API structure explicitly supports Price List assignments containing a price_list_id, customer_group_id and channel_id.

Customer Groups add another layer. They can be used not only for differentiated pricing but also to control access to particular products or categories. This means a merchant can create experiences such as a public retail catalog alongside restricted trade pricing without necessarily maintaining two independent product databases.

For B2B operations, Company accounts can connect several buyers to the same business customer and support purchasing roles, quote workflows and other account-level buying behavior. Multi-Storefront can also be combined with B2B functionality while backend processes remain centralized.

Finally, the merchant needs to monitor not only orders but also GMV, because BigCommerce's self-service plan structure can change as commerce volume grows. That makes growth itself part of the platform workflow, not merely a sales metric.

BigCommerce pricing needs more explanation than the monthly subscription figures suggest.

The self-service plans currently start with Core at $39/month, Growth at $105/month and Scale at $399/month. Annual billing reduces those effective monthly prices to $29, $79 and $299 respectively. Performance starts at $1,499 per month and is billed annually. BigCommerce also offers a fully functional 15-day free trial without requiring a credit card.

The unusual part is how growth affects cost. Core has a $30,000 trailing-twelve-month GMV threshold, while Growth has a $100,000 TTM GMV threshold. BigCommerce says accounts exceeding the relevant threshold can be automatically moved to the next plan. Scale works differently: its base price includes up to $33,333 in monthly GMV, after which a 0.9% overage applies only to GMV above that amount, rather than using fixed revenue blocks.

There is another cost that deserves attention. BigCommerce distinguishes between Embedded Payment Providers and Open Payment Providers. Eligible orders processed through an Open provider can incur an additional BigCommerce fee of 2.0% on Core, 1.0% on Growth and 0.6% on Scale, separate from whatever the payment processor itself charges. Orders through Embedded Payment Providers are not subject to that BigCommerce fee.

One particularly easy detail to miss is that BigCommerce's billing GMV may not equal the revenue figure in a merchant's accounting dashboard. BigCommerce says it evaluates plan thresholds using gross order value after a 10% reduction, and eligible sales can include product value after discounts plus taxes and shipping. Certain integrated marketplace and social-commerce transactions also count.

For that reason, the useful way to compare BigCommerce pricing is not merely “What does the plan cost today?” but “What will the platform cost at my projected GMV, with my payment provider and storefront architecture?”

BigCommerce has the standard ecommerce capabilities expected from a mature hosted platform, but several less obvious features are more useful for understanding where it differs.

Multi-Storefront allows more than one storefront to be operated from the BigCommerce environment. The value is not simply having several designs. Different storefronts can represent separate brands, audiences or markets while orders and customers remain manageable from the broader BigCommerce operation.

Price Lists are particularly important for more complex businesses. BigCommerce's underlying assignment model supports combinations of a Price List, Customer Group and Channel. In practice, this means pricing can be structured around both who the buyer is and which storefront they are using, rather than applying one universal catalog price everywhere.

Customer Groups can also change catalog access, not just pricing. Specific products or categories can be made available to selected groups, which creates useful scenarios for wholesale catalogs, member pricing or controlled product ranges.

B2B Edition introduces company-oriented purchasing rather than treating every customer as an isolated consumer account. Company accounts, multiple buyers, buyer permissions, sales quotes and approval-oriented workflows move BigCommerce closer to procurement software than a conventional consumer storefront in these use cases.

The platform also exposes substantial API capacity for integrations and headless implementations. An operational detail rarely mentioned in general reviews is that BigCommerce currently states 20,000 API calls per hour for Core and Growth and 60,000 per hour for Scale, while Performance includes API support. For stores synchronizing catalogs, inventory, ERP data or custom frontends, this can matter more than the number of themes available.

Another practical feature difference sits between Growth and Scale. BigCommerce identifies functionality such as customer groups, abandoned-cart recovery and persistent carts with Growth, while Scale adds capabilities including advanced product filtering and additional inventory-location/storefront capacity.

The broader pattern is that BigCommerce's strongest features become progressively more valuable as the merchant needs different prices, different buyers, different storefronts and different systems to behave as one commerce operation.

BigCommerce is strongest for businesses whose ecommerce complexity is increasing faster than their desire to maintain infrastructure.

A particularly good fit is a multi-brand business that wants separate storefront identities but does not want every brand to become an entirely isolated commerce system. Multi-Storefront gives these businesses a way to separate the customer-facing experience while preserving centralized management.

It is also well suited to hybrid B2C and B2B merchants. A manufacturer, distributor or established retail brand may need normal consumer checkout on one side and company accounts, multiple corporate buyers, quotes, restricted catalogs or negotiated pricing on the other. BigCommerce's B2B tools and customer-group/Price-List structure are unusually relevant to that combination.

Another strong fit is a business planning headless or heavily integrated commerce. When the frontend, ERP, inventory system, CRM or other operational software has its own lifecycle, using BigCommerce primarily as the commerce backend can make more sense than forcing the whole organization into a website-builder workflow. The published API limits also give technical teams a concrete capacity consideration when selecting a plan.

BigCommerce is less compelling for a merchant whose requirements are essentially one small catalog, one storefront, one customer type and basic checkout. That business can still use it, but much of the architectural advantage remains unused while GMV thresholds and payment-provider rules still need to be understood.

The platform is therefore best evaluated not by asking “Can BigCommerce build my store?” — many platforms can — but by asking “Will my commerce operation become complicated enough that centralized channels, customer-specific pricing, B2B workflows and API-driven integrations save me from rebuilding it later?”

Shopify is the closest alternative when a business wants a more standardized merchant experience and a large commerce ecosystem without making architecture the center of the decision. Shopify now includes core B2B capabilities such as companies, catalogs, net terms and self-service ordering across its main plans, although lower tiers limit B2B market catalogs and reserve direct company-level catalog assignment for Shopify Plus. For merchants that want B2B capabilities but do not need BigCommerce's broader multi-storefront operating model, Shopify can therefore be the simpler fit.

WooCommerce is the better alternative when ownership and infrastructure control matter more than SaaS convenience. It is open source, runs inside WordPress, and lets the merchant choose the host, payment stack and underlying implementation. That removes the idea of a SaaS plan automatically changing because of platform-defined GMV thresholds, but it also shifts hosting, performance, maintenance and extension decisions back to the merchant or development team.

Adobe Commerce becomes more relevant when the business needs a deeply engineered enterprise environment rather than a managed mid-market SaaS platform. A single Adobe Commerce installation can contain multiple websites, stores and store views with separate catalogs, domains, branding and configuration scopes. That provides extremely granular multi-site control, but Adobe's own documentation also shows that multi-store configuration can extend into server-level setup, making it a stronger fit for organizations with dedicated technical resources.

BigCommerce occupies an interesting position between these approaches. It keeps the core commerce infrastructure managed while still allowing multiple storefronts, differentiated customer pricing, B2B workflows and API-driven frontends. The strongest reason to choose it is therefore not that it can launch a store faster, but that it can let a growing business add operational complexity without immediately replacing the commerce backend.

BigCommerce earns a strong editorial score because its most valuable capabilities appear after a store becomes complicated. Multi-Storefront, customer-specific pricing, B2B workflows and API access are not isolated features; together they allow several commercial experiences to operate around one underlying commerce system. BigCommerce currently allows additional storefronts directly on its self-service plans and describes Multi-Storefront as a way to manage separate brands, customer segments and regions from one account.

The platform does not score equally well on simplicity or value because its commercial model now requires more attention than the headline subscription price suggests. Core and Growth use trailing-twelve-month GMV thresholds, Scale introduces a monthly GMV allowance followed by continuous overage pricing, and Open Payment Providers can create a separate BigCommerce fee on eligible orders. That means two merchants using similar features can experience different platform economics depending on revenue growth and payment-provider choice.

This is why BigCommerce makes more sense to us as commerce infrastructure for a business that expects complexity than as a generic store builder. A merchant with one storefront, one pricing model and a straightforward catalog may never extract enough value from its deeper architecture. A business adding brands, regions, B2B buyers, custom pricing or external systems has a much stronger reason to choose it.

Our 8.5/10 rating reflects that balance: excellent feature depth and expansion potential, offset by greater operational complexity and a pricing model that requires merchants to understand GMV and payment architecture rather than looking only at the monthly plan price.