BigCommerce

Publicly traded (NASDAQ: BIGC), headquartered in Austin, Texas; founded in Sydney, Australia.

Founded by Eddie Machaalani and Mitchell Harper in Sydney, Australia, launching as a SaaS ecommerce platform in August 2009 (the founders had run a prior company, Interspire, since 2004).

Core SaaS platform is proprietary, closed-source, hosted software. BigCommerce does maintain open-source developer tooling (Stencil CLI, and the Catalyst headless framework built on Next.js/React) on GitHub, but the commerce backend and admin are not open source.

The BigCommerce platform itself is closed, hosted software available only by subscription. Catalyst (headless storefront framework) and Stencil CLI are open-source developer tools on GitHub, but Catalyst still requires an active BigCommerce store/account to connect to.

No free-forever tier. Cheapest paid entry is Core at $29/mo (annual billing).

Not applicable - no free plan exists.

Core plan, billed annually. Month-to-month billing is $39/mo. Core includes a full storefront and custom domain, capped at $30,000 in trailing-twelve-month GMV before BigCommerce auto-upgrades the store to Growth.

Scale plan (billed annually; $399/mo month-to-month) is marketed by BigCommerce as its 'Most Popular' tier. Growth ($79/mo annual) is the mid-tier immediately above Core, but Scale is the one BigCommerce itself flags as most popular on the pricing page.

BigCommerce is ecommerce-only; every plan (starting with Core at $29/mo annual) includes a full storefront, catalog, and checkout.

Unlike some website builders, BigCommerce does not gate removal of platform branding behind a paid tier; the free 15-day trial store itself is not branding-restricted either.

No teaser/renewal price gap of the kind seen on some builders. The advertised annual-billing price ($29/$79/$299 for Core/Growth/Scale) is the ongoing subscription rate for as long a merchant stays on that plan and under its GMV threshold; the higher figure shown alongside it is simply the month-to-month (non-annual) rate, not a post-promotional renewal increase.

BigCommerce explicitly states it does not offer refunds on subscriptions; it offers the 15-day free trial instead as the way to evaluate the platform before paying.

Storefront theming uses BigCommerce's Stencil framework with Page Builder, a widget/section drag-and-drop editor layered on top of fixed page templates (home, category, product, etc.); full custom layout/markup requires editing Handlebars/SCSS/JS theme files directly via the Stencil CLI.

Page Builder widgets (text, image, banner, video, carousel, custom HTML, etc.) are dragged from a side panel and dropped into preset page regions; a Layers tool allows reordering by drag-and-drop.

Text widgets support editing content directly on the page/preview inside Page Builder.

Page Builder has an Undo button and a Save-vs-Publish flow within a single editing session; this is session-level undo, not a persistent, browsable version-history timeline for page content (separate from theme-file version control available via Stencil CLI/git for developers).

Page Builder requires an explicit Save action; documentation does not describe autosave of in-progress edits, and warns against multiple simultaneous editors/tabs, which is consistent with a manual-save model.

No official BigCommerce mobile app for editing storefront design/Page Builder content was found; BigCommerce's mobile presence is oriented toward store management (orders, products) rather than a mobile theme/Page Builder editor.

Core catalog data (products, categories, customers, orders) is independent of theme and carries over when switching themes, but Page Builder customizations and theme-specific settings are tied to the active theme and are not guaranteed to transfer automatically to a newly applied theme.

Editorial: catalog setup, checkout configuration, and basic Page Builder edits are approachable for non-developers, but BigCommerce's plan structure (GMV thresholds, Open Payment Provider Fee logic), theme file editing via Stencil CLI, and B2B/headless capabilities add real complexity that pushes typical merchant experience above a pure drag-and-drop site builder.

BigCommerce's official theme marketplace pages (bigcommerce.com/themes/, /theme-store/) do not publish an exact total theme count on-page; third-party estimates (roughly 100+ Stencil themes, ~12-15 free) are not first-party figures and were excluded per sourcing rules.

Custom fonts can be added via theme font settings (Google Fonts picker built into most Stencil themes) or by uploading font files and referencing them with custom CSS in the theme's Advanced/Custom CSS panel; not a universal one-click uploader across every theme.

Stencil themes and Page Builder widgets are responsive by default; Page Builder offers desktop/tablet/mobile preview and limited per-device overrides (e.g., text color) rather than a full visual breakpoint editor.

Every plan has access to a theme CSS editor in the control panel (Storefront > Themes > Advanced/Edit CSS) plus full Stencil theme file access (SCSS/CSS) via Stencil CLI for local development; not gated by plan tier.

Custom JavaScript can be added via Script Manager (header/footer script injection, available on every plan, with per-page targeting and cookie-consent categorization) or directly in Stencil theme JS files; not plan-gated.

No dedicated native animation/interaction builder in Page Builder; any scroll/hover/transition effects come from the theme's own built-in CSS or require custom CSS/JS added by the merchant or a developer.

Theme-level style settings (colors, typography, layout options) are configurable store-wide through the theme editor/Page Builder's global theme settings panel.

Editorial: Page Builder's section/widget model constrains no-code design to preset regions within a theme's layout, similar to Shopify's model, but full Stencil theme code access (Handlebars/SCSS/JS) on every plan, plus the Catalyst headless option for a fully custom React/Next.js frontend, gives developers a path to near-unconstrained design at the cost of needing code.

Fully managed, PCI-compliant hosting is included in every subscription plan; no separate hosting purchase required.

The standard BigCommerce storefront cannot be self-hosted; it is a closed managed SaaS backend. A headless build via Catalyst (Next.js/React frontend against the GraphQL Storefront API) lets the frontend layer be hosted elsewhere, but the commerce backend, admin, and checkout remain BigCommerce-hosted and are not self-hostable.

Global CDN (Akamai) is included as part of managed hosting on every plan; image optimization is additionally handled via Cloudflare Polish and Akamai Image Manager.

Free SSL certificate is included and auto-provisioned for storefronts on every plan.

This is BigCommerce's own marketing claim on its site-performance page; it is not confirmed as a contractual, financial-credit-backed SLA for self-serve (Core/Growth/Scale) plans versus a formal Performance/Enterprise contract term.

No native static HTML export of a live storefront. Stencil theme code (Handlebars/SCSS/JS templates) can be bundled/downloaded as a ZIP via Stencil CLI, but it is not a static rendered site and will not run outside BigCommerce's Stencil rendering engine and API connection.

May 2026 CrUX data via HTTP Archive CWV Technology Report API: 60.0% combined pass rate across 23,888 tested origin-device combinations (desktop 55.7% of 11,618 origins; mobile 64.1% of 12,270 origins). Report technology name: 'BigCommerce'.

Cloudflare Polish automatically optimizes images for size/quality/format by device, and Akamai Image Manager provides additional automatic image optimization as part of BigCommerce's managed hosting/CDN.

Modern Stencil themes (e.g., Cornerstone) implement lazy loading for images as part of standard performance/accessibility best practices in the default theme.

Caching and CDN behavior are managed by BigCommerce's platform.(Akamai); merchants do not get direct, general-purpose cache-control configuration comparable to a self-hosted setup. Some cache-related behavior can be influenced indirectly through Script Manager page targeting or theme-level settings, but there is no dedicated merchant-facing cache-control panel.

Page title and meta description are editable per product, category, brand, web page, and blog post in the admin's SEO/search engine listing preview fields.

Custom URLs (slugs) are editable per product, category, page, and blog post via the storefront URL field in the admin.

Precise platform-wide URL prefix rules were not confirmed from a single official BigCommerce doc; this reflects the general consensus across BigCommerce SEO documentation and community sources describing customizable per-item URLs.

Native 301 redirect tool built into the admin (Storefront > 301 Redirects), including bulk CSV import of redirects.

BigCommerce automatically generates canonical tags for many page types (e.g., pointing duplicate category/filter URLs and multi-category product listings back to a preferred URL) and canonical tags can also be customized/overridden via theme code for edge cases.

robots.txt is editable natively in the admin under Storefront/Settings > Website, allowing merchants to add custom disallow rules (e.g., blocking filtered/sorted category URL variants) without a theme file edit.

sitemap.xml is auto-generated and kept up to date as products and pages are added; it is not manually editable/configurable by merchants through the admin.

Default Stencil themes include some baseline structured data (e.g., basic Product/Organization schema), but coverage is limited; richer schema (FAQ, enhanced Review/AggregateRating, Article) is not comprehensively auto-emitted and typically requires manual JSON-LD theme customization or a dedicated schema app.

BigCommerce does not automatically generate hreflang tags for multi-storefront or multi-language configurations; hreflang must be implemented manually via Script Manager, custom Stencil theme code, or a third-party app/solution.

Open Graph/social preview meta tags are generated by Stencil theme templates and can be customized via theme code; social share image typically defaults to the primary product/page image.

Individual web pages can be set to 'unpublished' or hidden from search via visibility/search-engine settings, and meta robots noindex tags can be added per page/product via custom fields or theme code for finer control.

Alt text is editable natively for product images and other uploaded media in the admin.

Native blog engine included on every plan (Storefront > Blog), but it is a lightweight, secondary feature relative to BigCommerce's ecommerce core: limited design control, and third-party sources consistently note it lacks the SEO tooling (schema, analyzer) and content depth of a dedicated blogging/CMS platform, leading many merchants to pair BigCommerce with a specialized blog app like DropInBlog.

Metafields (native, no app required) let developers attach custom key-value structured data (up to 65,535 characters) to products, categories, and other store objects; custom resources/fields provide additional native ways to extend content beyond standard product/page fields, though managing metafields in the admin UI typically requires a metafields-editor app rather than a built-in admin screen.

Products support nested categories and brands; the native blog supports tags. Blog Tags are exposed via the REST Content API.

Blog posts support scheduled future publish dates in the native blog editor, and this is also exposed via the Blogs API.

No native version history/rollback UI for regular web page or blog post content was found in BigCommerce documentation. Theme-level version control exists for developers via Stencil CLI combined with external git usage, but that is a developer workflow, not a merchant-facing content revision/rollback feature.

The native blog's author field is a single text/name field per post rather than a multi-author collaborative byline system with per-user accounts and profiles; documentation and community support threads describe it as a simple author-name field, not a role-based multi-author system.

BigCommerce provides a native RSS feed for the built-in blog.

REST Content API and GraphQL Admin API provide read-write access to products, pages, blog posts, categories, and metafields for custom content management and integrations.

Ecommerce is BigCommerce's core product, not an add-on; every plan includes full catalog, cart, and checkout.

This is a materially different mechanic than 'always-zero' platform fees: it is zero only when using an embedded/approved processor, not an unconditional zero across every possible payment gateway choice.

Native support for digital/downloadable products: files can be attached directly to a product listing, with configurable download-count and expiration-window limits; digital file storage is capped at 512MB. No separate app required, unlike Shopify's approach.

BigCommerce does not ship a first-party native subscriptions/recurring-billing product; merchants add a subscriptions app from the App Marketplace (e.g., PayWhirl, Recharge, MINIBC, Rebillia, Sticky.io) that integrates with supported payment gateways to expose recurring billing at checkout.

Native multi-currency selling (100+ currencies) is available across all plan types at no additional cost, via pre-built integrations with supported payment providers (e.g., Adyen, Elavon, Klarna, PayPal Express Checkout, Stripe); requires a Stencil theme and BigCommerce's Optimized One-Page Checkout. Enterprise/Performance adds Price Lists for per-market fixed pricing beyond simple exchange-rate conversion.

BigCommerce does not offer its own first-party point-of-sale product (unlike Shopify POS). It instead advertises native/pre-built integrations with third-party POS platforms of the merchant's choice (e.g., ConnectPOS, Lightspeed, Square), so in-person selling requires connecting an external POS system rather than a BigCommerce-owned one.

Native Abandoned Cart Saver (up to 3 automated recovery emails with cart contents and a direct checkout link) is included on Growth, Scale, and Performance plans, but is NOT available on the entry-level Core plan.

Products, customers, and orders export via native CSV export tools in the admin (Products > Export); blog/page content and broader store data are accessible via the REST/GraphQL APIs but do not have a single one-click full-site export tool. BigCommerce documentation itself notes native import/export is not sufficient to export an entire store, pointing merchants toward third-party migration apps for a complete data pull.

Stencil theme files can be bundled/downloaded as a ZIP, but the theme is written against BigCommerce's proprietary Handlebars-based Stencil rendering engine and API data model - it will not run as a functioning site on another platform. Marketplace-purchased themes are additionally license-locked to the store they were purchased for.

Custom domains (registered through BigCommerce or externally) follow standard domain portability; DNS can be repointed elsewhere at any time.

The standard BigCommerce storefront cannot run off BigCommerce's own hosting. A Catalyst headless build allows the frontend presentation layer to be hosted elsewhere (e.g., Vercel), but the commerce backend, checkout, and admin remain BigCommerce-hosted SaaS and cannot be self-hosted or moved.

REST Content/Catalog/Management APIs and the GraphQL Admin/Storefront APIs expose broad read/write access to products, categories, pages, blog posts, metafields, and customer/order data.

Editorial: core commerce data (products/customers/orders) is exportable via CSV/API and the domain is portable, and BigCommerce's payment architecture is deliberately more open than processor-exclusive competitors, but the storefront itself cannot be self-hosted, Stencil themes and marketplace-purchased themes are not portable to other platforms, and switching away means rebuilding the storefront - broadly comparable lock-in profile to Shopify, moderated somewhat by more portable payment-provider choice.

Exact figure not confirmed from a single official BigCommerce page with a stated total; range reflects the most consistent estimate across sources.

REST Management/Content/Catalog APIs and GraphQL Admin and Storefront APIs are all publicly documented at developer.bigcommerce.com.

Native webhook subscriptions (V2 and V3 REST, plus GraphQL Admin API mutations) for order, product, customer, and other store events; a webhook subscription auto-deactivates after 90 days of inactivity.

Script Manager (header/footer script injection with per-page targeting, including checkout) is available on every plan, not plan-gated; full theme-level HTML/CSS/JS embedding is also available via Stencil theme code on every plan.

Stencil CLI (official, open-source, Node.js-based, npm package @bigcommerce/stencil-cli) supports local theme development, live preview via Browsersync, and bundling/pushing themes to a live store from the command line.

Official BigCommerce app on Zapier connects to 9,000+ other apps; requires a paid BigCommerce plan and Store Owner-level API credentials to configure. Make.com also offers a BigCommerce integration.

Store Builder is an AI assistant that generates a functional BigCommerce store (product pages, collections, basic design, checkout/shipping setup) from a merchant's text description of their business.

BigAI Copywriter (built on Google Gemini) generates SEO-oriented, brand-voice-adjustable product descriptions and content.

Third-party sources reference AI product-recommendation and merchandising tools, but a first-party, officially documented AI image-generation/editing tool (comparable to Shopify Magic's Photo Editor) was not confirmed from an official BigCommerce source.

BigAI Copywriter's SEO-focused content generation functions as AI SEO assistance for product/content copy; BigCommerce also promotes AI-catalog-feed tooling to optimize product data for discovery across AI shopping surfaces (ChatGPT, Google AI, Perplexity, Copilot, Amazon).

Predefined roles (Sales Staff, Sales Manager, Store Administrator, Store Owner) plus fully custom roles with granular, individually assignable permissions; only the Store Owner can grant certain high-risk permissions such as app install/uninstall.

Page Builder documentation explicitly warns that simultaneous editing across multiple devices/browser tabs by the same or different users can cause issues; there is no real-time Google-Docs-style co-editing of the same page/content.

No native editorial approval/review workflow for content, product, or theme changes was found in BigCommerce documentation; achieving this would require a third-party app or manual process.

A sandbox/staging store can be created (by converting a trial store, coordinated with a BigCommerce Customer Success Manager) for merchants generally, though data is not automatically synced from live to sandbox and must be manually exported/imported. Enterprise/Performance-tier merchants can additionally use StagingPro, a git-based, API-driven sandbox/CI/CD solution built for BigCommerce.

No native in-editor commenting/annotation feature for reviewing content or design changes was found in Page Builder documentation.

BigCommerce's Security and Compliance overview and staff permission system support tracking of user actions in admin; comprehensive change-history/audit-log detail is more robust on Enterprise/Performance-tier accounts.

BigCommerce states 24/7 chat, email, and US-based phone tech support broadly; phone support specifically is guaranteed starting on Growth and above, while Core includes 24/7 chat/email with phone support addable as needed.

Editorial: developer.bigcommerce.com/docs.bigcommerce.com and the Help Center cover both merchant and developer documentation reasonably well, but during this research many official support.bigcommerce.com article pages returned client-side loading/CSS errors when fetched directly (requiring search-result-cached content instead), and developer doc URLs have undergone recent domain migrations (developer.bigcommerce.com to docs.bigcommerce.com) that produced broken/404 links - a real friction point relative to platforms like Shopify's more consistently reliable dev docs.

BigCommerce backs up its own platform infrastructure, not individual merchant store content on a merchant-facing, automatic, restorable basis; merchants are directed to manual CSV export as their native backup method. Third-party apps (e.g., Rewind, Skyvia, BackupMaster) provide automated daily backups and one-click restore as an add-on.

Native multi-language support via the Localization settings page (added to the control panel starting October 30, 2025), supporting per-storefront language overrides; Multi-Storefront lets merchants run separate language/region-specific storefronts from one account. Catalyst (headless) supports up to 5 locales per channel with additional translation-management tooling. Checkout and transactional emails ship with pre-built translations in 19 languages by default.

Catalyst provides native tooling for managing translations of dynamic catalog data and detecting/switching shopper language preference; for traditional Stencil storefronts, merchants commonly connect third-party translation apps (Weglot, Lokalise, ConveyThis) rather than relying on a single native in-admin translation-management screen.

Multi-Storefront supports per-storefront domains/subdomains for different languages/regions, but BigCommerce does not automatically generate hreflang tags between them - hreflang must be implemented manually (Script Manager, theme code, or a third-party solution), which is a meaningful gap versus platforms with automatic hreflang generation.

No official BigCommerce documentation explicitly confirming or denying platform-wide RTL (e.g., Hebrew, Arabic) storefront rendering support was found; RTL support likely depends on individual theme implementation, consistent with how other Stencil-theme-dependent design features work, but this could not be verified against an official source.