BigCommerce is a strong hosted e-commerce choice when you can name the operational depth you need: multiple storefronts, account-based B2B buying, broad channel connections, or a commerce backend behind a custom frontend.

For a lean product brand launching one retail store, we wouldn’t buy BigCommerce to prepare for growth you can’t yet name. There, the deciding question is whether its theme tools fit the store you want and who handles the changes they can’t make. Setka, our product, answers that question differently: the platform builds the store and keeps changing it as you direct.

We wrote this review from BigCommerce’s public documentation, not a test store.

The strongest reason to choose BigCommerce

BigCommerce combines hosted commerce with several paths for presenting and extending it. Its product offer covers catalog management, checkout, discounts, a built-in blog, product reviews, payment connections, and sales channels, and you don’t have to arrange separate hosting for the commerce application.

The catalog allowance helps too: the current plan comparison lists unlimited products on every self-service plan. Catalog size alone is a poor measure of fit, though. A retailer with 3,000 straightforward products may have a simpler purchasing process than a manufacturer selling 30 products at negotiated prices to company accounts.

BigCommerce’s case becomes stronger as those operational distinctions matter. It documents multi-storefront operations for separate brands or regions and connections to marketplaces, social channels, and other business systems. Those count when a business already sells through several coordinated routes to market; a new brand doesn’t need all of them.

The practical benefit is one commerce backend behind whichever selling surfaces and integrations the business needs. The matching work is configuring those connections and making someone responsible for them.

Choose the storefront path before judging ease of use

BigCommerce has two materially different implementation paths. Treat them as one builder and you miss both its strengths and its costs.

Stencil: a hosted theme with everyday editing

Stencil is BigCommerce’s integrated theme system. According to the Stencil documentation, Page Builder and theme settings change typography, colors, banners, headings, layouts, and widgets without editing the theme files. That is a sound way to run a store, and not every update needs a developer.

Deeper changes use the theme’s templates, styles, JavaScript, and development tooling. If your chosen theme and available widgets already carry the buying journey, this may be work you rarely need. If the theme fights the way you want to explain the catalog, the merchant or agency owns the implementation that bridges the gap.

That makes theme selection a business decision. Judge a theme with real product information and the types of collection page you will need, rather than a demo populated with different products.

Catalyst: a custom frontend with a visual editor

Catalyst is BigCommerce’s composable storefront framework built with Next.js and React and connected to its GraphQL Storefront API. It includes a visual editor, so routine changes don’t all go through developers. Still, the Catalyst overview and FAQ describe it as a fit for complex needs and teams with developer resources, and commercial terms require a conversation with BigCommerce.

Choose this path when control of the frontend or a specific integration justifies an implementation team. Distinctive typography or a better collection introduction is not, on its own, a reason to commission a custom stack.

B2B depth is real, and it has its own scope

BigCommerce B2B Edition documents company accounts, user roles, sales quotes, invoices, and a Buyer Portal. Its broader offer includes purchasing workflows such as customer-specific prices and approval chains. For a wholesaler, those can be core buying requirements rather than conveniences, as the B2B offer makes clear.

B2B Edition is provisioned through its app and BigCommerce support, according to its documentation. Don’t read the retail subscription price as an all-inclusive quote for a configured B2B operation: the account structure, storefront behavior, and required integrations need their own implementation and commercial scope.

We would shortlist BigCommerce for a manufacturer whose buyers need company permissions, quotes, and invoice management. We would not use those strengths to persuade a candle brand with one public catalog to buy complexity it has no present use for.

The current bill includes more than the subscription

As checked on 16 October 2026, the current USD plans are Core, Growth, Scale, and Performance. Core, Growth, and Scale cost $39, $105, and $399 on monthly billing, or monthly equivalents of $29, $79, and $299 on annual billing, before tax, according to BigCommerce pricing.

Three cost rules matter even in a general review:

  1. Core and Growth can move up automatically at $30,000 and $100,000 of trailing-12-month BigCommerce GMV, respectively.
  2. Scale includes $33,333 of monthly GMV, with a 0.9% overage rate above that amount.
  3. Orders through Open Payment Providers incur separate BigCommerce fees of 2%, 1%, or 0.6% on eligible order GMV on those three plans. Orders through listed Embedded Payment Providers do not incur that additional fee. Processor fees still apply.

BigCommerce defines GMV using gross order value after a 10% reduction. Its eligible-sales scope includes shipping and tax, so these thresholds are not profit or simply the merchandise revenue in your own spreadsheet. Older reviews describing Standard, Plus, and Pro with a universal “no transaction fees” policy predate the 2026 plan and payment-provider changes.

Additional storefronts, paid apps, a theme, or implementation help can add costs when your setup uses them. A free theme and ordinary Page Builder settings remain a legitimate branch. For the complete commercial explanation, read our BigCommerce pricing guide.

A better growth question: what changes next?

Imagine a hypothetical candle brand launching eight scents, then adding a winter collection of separately sold products. Its next job is to help shoppers choose: which scents suit which rooms, what each candle contains, and when an order will arrive.

In BigCommerce, adding the products and setting the selling rules are commerce tasks. Promoting the collection may fit Page Builder. A new product-page structure outside the chosen theme’s controls may become theme work. A Catalyst store gives the team another route, with its own developer responsibility.

All three can be reasonable, as long as you choose the work on purpose. More traffic, a larger catalog, and a more specialized purchasing process are different kinds of growth, and they don’t call for the same architecture.

In Setka, the same collection is a request to the store: lead with the winter candles, explain which scents suit which rooms, and keep each candle’s contents and delivery times exact. You fix any wording directly, preview the next version, and publish it. No theme work sits between the decision and the live store, and the previous storefront version stays available if you want it back.

Our recommendation

Choose BigCommerce when its operations justify the platform: defined B2B workflows, several storefronts, required channel or system connections, or a custom frontend with an owner who can support it. Begin with the least elaborate storefront path that satisfies those requirements.

For a single product brand whose main need is a store it can keep shaping, we recommend Setka. Its price doesn’t rise with your sales: no GMV threshold moves you up a plan, and no platform percentage is added to your orders. Stripe’s processing fees still apply. You bring the products and direction; Setka builds the storefront into the commerce platform. You can describe changes, edit exact words, preview before publishing, and branch from an earlier storefront version without maintaining theme code.

That recommendation is about storefront work, not about matching BigCommerce’s enterprise features. If company accounts, negotiated purchasing, or a required specialist integration decides your choice, BigCommerce’s documented operations deserve priority.

If your decision now comes down to who builds the store, read our BigCommerce alternative, which shows how a collection change works in Setka and what to settle before you move.