BigCommerce

What Is BigCommerce?

BigCommerce is a fully hosted, software-as-a-service e-commerce platform built for growing and enterprise stores, and one of the principal competitors to Shopify. The short answer is that BigCommerce gives merchants a turnkey, no-server-maintenance storefront with an unusually deep set of built-in features and, notably, no platform transaction fees on any plan. Technology-detection sources such as BuiltWith report BigCommerce powering a meaningful share of mid-market and larger online stores, with a footprint that skews toward established brands and B2B sellers rather than the smallest shops.

Founded in 2009, BigCommerce differentiates itself in three ways. First, it ships with more native functionality (multi-currency, faceted search, customer groups, abandoned-cart recovery) so merchants rely less on paid apps. Second, it charges no transaction fees regardless of which payment processor you use. Third, it offers strong support for headless commerce, letting teams pair its commerce backend with any modern frontend framework.

The result is a platform positioned for businesses that have outgrown the most basic tools but want SaaS simplicity instead of self-hosted complexity.

How BigCommerce Works

BigCommerce is a multi-tenant SaaS platform: Google-grade infrastructure, hosting, security, PCI compliance, and uptime are all handled by BigCommerce, and merchants manage their store through a web control panel. There is no server to patch and no software to install.

Storefronts are traditionally built on Stencil, BigCommerce's theme framework. Stencil themes use the Handlebars templating language, a defined directory structure, and a local development workflow via the Stencil CLI. Rendered pages reference assets and theme files under /stencil/ and load store data into a JavaScript global named window.BCData, which carries cart, product, and customer context to the frontend.

Static assets, images, and theme files are served from BigCommerce's content delivery network on cdn11.bigcommerce.com and related cdn*.bigcommerce.com hosts. Product images, in particular, are delivered through these CDN domains, which makes them a reliable fingerprint. The hosted checkout is served from checkout.bigcommerce.com, isolating the payment step on BigCommerce's PCI-compliant infrastructure.

For modern architectures, BigCommerce embraces headless commerce. Its Storefront API, GraphQL Storefront API, and Management API let developers build custom frontends with frameworks such as Next.js, Gatsby, or Nuxt while BigCommerce handles catalog, cart, checkout, and order management behind the scenes. The platform also provides multi-channel connectors so the same backend powers a website, marketplaces, and social storefronts simultaneously.

Because it is SaaS, merchants trade some low-level control for reliability, automatic scaling during traffic spikes, and freedom from infrastructure management.

It is worth distinguishing the two ways merchants run BigCommerce, because they leave different fingerprints. In the traditional (Stencil) model, BigCommerce hosts both the backend and a Stencil-themed storefront, so you see cdn*.bigcommerce.com assets, /stencil/ references, and window.BCData directly in the page. In the headless model, the storefront is a separate application (perhaps deployed on Vercel or Netlify) that calls BigCommerce APIs behind the scenes; in that case the public site may not expose obvious BigCommerce markup, and you confirm the platform by inspecting network calls to BigCommerce API endpoints or the checkout.bigcommerce.com flow. Recognizing which model a store uses is essential for accurate detection.

BigCommerce's checkout deserves special mention. Rather than rendering payment forms inline with the rest of the theme, BigCommerce serves an optimized, PCI-compliant checkout that can run on checkout.bigcommerce.com or be embedded via the Open Checkout (formerly Optimized One-Page Checkout) framework. This isolation keeps sensitive payment handling on hardened infrastructure and is a reliable tell that a store runs on BigCommerce even when the storefront is heavily customized.

Catalog and pricing logic also run server-side. BigCommerce computes faceted search facets, customer-group pricing, and currency conversions on its own infrastructure, then exposes the results to the storefront through templates or APIs. This is part of why so much functionality is available without add-on apps: the platform does the heavy lifting centrally rather than pushing it onto third-party extensions. For merchants, that translates into fewer moving parts to maintain and a more predictable performance profile under load.

How to Tell if a Website Uses BigCommerce

BigCommerce leaves clear fingerprints in asset domains, markup, and JavaScript globals.

Signals in the page and network

• CDN asset domains. Look for resources loaded from cdn11.bigcommerce.com or other cdn*.bigcommerce.com hosts, especially product images and theme assets. This is the single strongest signal.
• JavaScript global. Inspect the page for a window.BCData object containing cart and store data. Its presence is a definitive BigCommerce indicator.
• Stencil theme markup. References to /stencil/ paths and Handlebars-rendered Stencil theme structures point to BigCommerce.
• Checkout domain. A checkout flow served from checkout.bigcommerce.com confirms the platform.
• Headers and routes. Response headers may reveal BigCommerce infrastructure, and storefront routes follow BigCommerce conventions.
• Generator hints. Some themes include meta or comment hints referencing BigCommerce or Stencil.

Tools to confirm it

Tool	What you do	What it reveals
View Source	Read the page HTML	cdn*.bigcommerce.com asset URLs, /stencil/ references, window.BCData
Browser DevTools	Check Network and Console tabs	CDN requests, the BCData global, checkout domain calls
curl -I	Run curl -I https://example.com	Headers and infrastructure hints
Wappalyzer	Run the extension on the page	Flags BigCommerce
BuiltWith	Look up the domain	Current and historical BigCommerce detection

For broader methods, see our guide on how to find out what e-commerce platform a website uses. Because BigCommerce is frequently compared with Shopify, our guide on how to tell if a website is built with Shopify helps you distinguish the two when signals overlap.

Key Features

BigCommerce is known for including capabilities that rival platforms reserve for paid apps.

• Rich built-in functionality. Multi-currency, multi-language, customer groups with tiered pricing, faceted (filtered) search, product reviews, and abandoned-cart recovery, all native.
• No transaction fees. Zero platform transaction fees on any plan, regardless of payment processor.
• Headless commerce APIs. Storefront API, GraphQL Storefront API, and Management API for custom frontends.
• Multi-channel selling. Native integrations with Amazon, eBay, Facebook, Instagram, Google Shopping, Walmart, and TikTok with synced inventory and orders.
• B2B and enterprise tools. Customer-specific catalogs, price lists, purchase orders, and the B2B Edition for larger sellers.
• Stencil theme framework. Flexible, developer-friendly theming with a local CLI workflow.
• Open SaaS flexibility. Wide payment-gateway choice (PayPal, Stripe, and many more) without lock-in.
• Strong default SEO controls. Customizable URLs, metadata, and built-in performance optimizations.

Pros and Cons

BigCommerce balances SaaS convenience with breadth of features, but it is not the cheapest or simplest option for everyone.

Pros

• Extensive built-in features reduce reliance on paid apps.
• No transaction fees on any plan, with broad payment-gateway freedom.
• Excellent headless and API support for custom frontends.
• Fully managed hosting, security, PCI compliance, and scaling.
• Strong multi-channel and B2B capabilities out of the box.

Cons

• Plans include annual sales thresholds that can force an upgrade as you grow.
• Smaller app marketplace than Shopify, though built-in features offset this.
• Theme customization can feel more developer-oriented than some no-code rivals.
• Less brand-name ubiquity than Shopify, so fewer agencies specialize in it.
• As SaaS, you have less low-level control than self-hosted platforms like Magento or WooCommerce.

BigCommerce vs Alternatives

BigCommerce competes most directly with Shopify but is also weighed against self-hosted platforms by teams that want more control.

Platform	Hosting model	Transaction fees	Built-in features	Best for
BigCommerce	Fully hosted SaaS	None on any plan	Very high	Growing and B2B brands wanting features without apps
Shopify	Fully hosted SaaS	Fees unless using Shopify Payments	Medium (app-driven)	Merchants wanting the largest app ecosystem
WooCommerce	Self-hosted (WordPress)	None (gateway fees only)	Medium	Content-led, full-control stores
Magento (Adobe Commerce)	Self-hosted or cloud	None (gateway fees only)	High	Complex enterprise and B2B catalogs
Wix / Squarespace	Fully hosted SaaS	Varies	Low to medium	Small stores and simple catalogs

If you prefer an open-source, self-hosted route with full control, compare BigCommerce with our profile of WooCommerce. Choose BigCommerce when you want SaaS simplicity with deep built-in features and no transaction fees; choose Shopify if app breadth and brand familiarity matter most.

A closer look at BigCommerce versus Shopify clarifies the trade-off. Shopify's strength is its ecosystem: tens of thousands of apps, a huge agency network, and a famously smooth checkout. Its weakness, for some merchants, is the transaction fee charged when you do not use Shopify Payments, and a reliance on paid apps to add capabilities that BigCommerce includes natively. BigCommerce flips this: more is built in, there are no platform transaction fees on any plan, and you keep full freedom over payment gateways, but the app marketplace is smaller and fewer agencies specialize in it. For a feature-rich store that wants to minimize monthly app costs and avoid transaction fees, BigCommerce is compelling; for a store that wants the deepest possible ecosystem, Shopify still leads.

Use Cases

BigCommerce is built for businesses in a growth phase that need capability without operational overhead.

• Mid-market brands. Stores that have outgrown basic builders and want native features rather than a stack of apps.
• B2B sellers. Businesses needing customer-specific catalogs, price lists, and purchase orders via the B2B Edition.
• Multi-channel retailers. Merchants selling across Amazon, eBay, social platforms, and their own site from one backend.
• Headless commerce teams. Developers pairing a modern frontend (Next.js, Gatsby, Nuxt) with BigCommerce APIs.
• High-catalog stores. Sellers needing robust faceted search and multi-currency support out of the box.
• International sellers. Merchants serving multiple regions who benefit from native multi-currency, multi-language, and localized pricing without bolting on extra apps.

For sales and competitive intelligence, detecting BigCommerce signals a growth-stage or enterprise merchant with budget and specific integration needs, making it a useful technographic data point. Because BigCommerce charges no transaction fees and supports many gateways, a BigCommerce store is also a strong prospect for payment, shipping, tax, and marketing tools that integrate through its APIs.

Agencies evaluating a re-platforming or optimization project use BigCommerce detection to scope work accurately: knowing whether a store uses a traditional Stencil theme or a headless frontend determines whether a project is mostly theme work or full frontend engineering. The clear CDN and window.BCData signals make this assessment fast and reliable even before a discovery call.

Frequently Asked Questions

How is BigCommerce different from Shopify?

Both are fully hosted SaaS platforms, but BigCommerce includes more native features (multi-currency, faceted search, customer groups) and charges no transaction fees on any plan, whereas Shopify charges fees unless you use Shopify Payments. Shopify has a larger app marketplace and more brand recognition. BigCommerce also leans more openly into headless commerce. The right pick depends on whether you value built-in breadth and fee-free flexibility (BigCommerce) or the largest ecosystem (Shopify).

How can I tell if a store uses BigCommerce?

The clearest signals are assets served from cdn11.bigcommerce.com or other cdn*.bigcommerce.com hosts, a window.BCData JavaScript global, /stencil/ theme references, and a checkout served from checkout.bigcommerce.com. Inspect the page with View Source or DevTools, or run the domain through Wappalyzer or BuiltWith to confirm.

Does BigCommerce charge transaction fees?

No. BigCommerce does not charge platform transaction fees on any plan, regardless of which payment gateway you use. You still pay your payment processor's standard rates, but BigCommerce itself takes no additional cut, which is one of its headline advantages over Shopify's fee structure when not using Shopify Payments.

Is BigCommerce good for headless commerce?

Yes. BigCommerce is one of the more headless-friendly SaaS platforms. Its Storefront API, GraphQL Storefront API, and Management API let teams build custom frontends with frameworks like Next.js or Gatsby while BigCommerce manages the catalog, cart, checkout, and orders. This makes it popular with developer teams wanting SaaS reliability and frontend freedom. It suits growing and enterprise merchants, B2B sellers, and multi-channel retailers, while very small stores may find lighter builders cheaper and teams needing total control sometimes prefer self-hosted WooCommerce or Magento.

Want to identify BigCommerce and the complete technology stack behind any online store instantly? Try StackOptic at https://stackoptic.com.