Stencil or Catalyst? How to Choose Your BigCommerce Storefront Architecture

Every BigCommerce build now starts with a fork in the road. You can launch on Stencil, the platform’s native theme framework, or on Catalyst, the headless storefront framework BigCommerce released to developers and agency partners in February 2024. Both are first-party, both are supported, and they lead to very different projects. Merchants ask us which one is better. The honest answer is that they solve different problems, and picking the wrong one is expensive in both directions.

This is the decision guide we walk clients through.

What Stencil Is

Stencil is BigCommerce’s native storefront engine. Themes are built on Handlebars templates, developed locally with the Stencil CLI, and hosted by BigCommerce alongside everything else. Cornerstone is the base theme most custom builds start from, and the Theme Marketplace sells ready-made options for merchants who want to launch without a design project.

Because Stencil runs inside the platform, everything native just works. Page Builder lets marketers drag widgets into layouts without a developer. Apps from the marketplace inject their scripts and widgets through the Script Manager with no integration effort. Checkout, customer accounts, search, and B2B Edition features render without anyone wiring them up. Performance is respectable and improves with disciplined theme development, though it’s constrained by the architecture and by whatever scripts the app stack adds.

What Catalyst Is

Catalyst is BigCommerce’s open-source headless framework. It’s built with Next.js and React, uses BigCommerce’s React storefront components, and talks to the platform through the GraphQL Storefront API. The storefront runs as its own application, typically deployed on Vercel, with BigCommerce handling catalog, cart, checkout, orders, and customers behind the API.

Two things separate Catalyst from the do-it-yourself headless builds of a few years ago. First, it ships as a working store: product pages, category pages, search, cart, and account flows exist on day one, built with SEO, accessibility, and performance already handled, so developers start from a functional storefront instead of an empty repository. Second, it comes with Makeswift, the visual editor BigCommerce acquired in late 2023, which lets marketers build and edit pages on a Next.js site without touching code. That editor is the answer to the classic headless complaint that every content change required a developer.

Catalyst also supports multi-region and multi-lingual configurations from the start, which matters for merchants planning international storefronts.

What Headless Actually Buys You

Strip away the vocabulary and headless buys four things.

Front-end freedom. Anything React can render, your storefront can be. Unusual product experiences, configurators, editorial layouts that would fight a theme, and interface patterns from outside ecommerce are all available.

Performance headroom. Server-side rendering, edge delivery, and full control over what loads on each page give a well-built Catalyst store Core Web Vitals that a script-heavy theme struggles to match. This is real, and it’s also earned: a headless store built carelessly is slower than a clean Stencil theme.

Composability. Headless makes it natural to plug in a headless CMS, a dedicated search engine, a PIM, or a personalization layer, each best-of-breed, each swappable.

Multi-experience flexibility. One BigCommerce backend can serve a Catalyst storefront, a mobile app, and a Stencil site simultaneously, which is how many merchants pilot headless without betting the business on it.

What Headless Actually Costs

Every one of those benefits has a bill attached, and the bill is the part sales conversations skip.

You run a separate application. That means hosting (Vercel or equivalent), deployment pipelines, environment management, monitoring, and someone who understands Next.js when something breaks at 2 a.m. on Black Friday. Stencil has none of that; BigCommerce hosts the theme.

Your developers need React and Next.js skills, which are more expensive and less common in the ecommerce agency world than Stencil skills. Estimate build costs accordingly.

Apps behave differently. Many marketplace apps rely on injecting scripts into a Stencil theme. On a headless storefront, some integrate cleanly through APIs, some need custom work, and a few don’t work at all. Audit your app stack against headless compatibility before committing, because “the reviews widget doesn’t render” is a bad discovery in week ten.

And the ongoing cost is higher. Framework updates, dependency management, and security patches on your own codebase are permanent responsibilities. A Stencil theme needs maintenance too, but the surface area is a fraction of the size.

The Decision, in Questions

Ask these in order. The answers usually settle it.

Do you have a specific experience requirement Stencil can’t deliver? A concrete requirement looks like a product configurator, an editorial-first layout, or a design system shared with a non-commerce site. “We want a modern site” doesn’t qualify; Stencil delivers that. No concrete requirement usually means Stencil.

Is performance a measured business problem? If you’ve quantified conversion loss from page speed and exhausted theme-level optimization, headless is a legitimate fix. If speed is a feeling rather than a number, fix the theme and the app stack first.

Do you need composability now? A merchant with a headless CMS strategy, a PIM, and a dedicated search vendor is already living in a composable world and Catalyst fits it. A merchant with none of those should be suspicious of buying architecture for a future they haven’t planned.

Can you staff it? Either an internal team with React skills or an agency relationship you trust for years. Headless with no one to maintain it is a liability with a nice homepage.

What’s the budget reality? Stencil launches cost a fraction of Catalyst builds, and the gap persists in maintenance. For a lot of mid-market merchants, the money is better spent on merchandising, search, and content.

Two Merchants, Two Right Answers

A specialty food retailer came to us with 1,200 SKUs, a marketing team of two, a marketplace app stack it liked, and a site that looked dated. The temptation was headless. The right answer was a new Stencil theme with a disciplined script audit, which cut page weight substantially, kept every app working, and launched in a fraction of the time and budget a Catalyst build would have needed. Nothing about that business required owning a front end.

A manufacturer of configurable equipment had the opposite profile: a product configurator no theme could deliver cleanly, a headless CMS already in place for its non-commerce content, an internal team with React skills, and measured conversion loss on slow product pages. Catalyst fit every requirement, the Makeswift editor gave marketing its independence, and the build was justified by a concrete list rather than a preference.

Same platform, same year, opposite decisions, both correct.

What About Existing Stencil Stores?

A working Stencil store doesn’t need to move. The questions above apply to a replatform decision exactly as they apply to a new build, and “our theme is old” is a reason for a theme refresh rather than a change of architecture. Merchants that migrate to headless for novelty tend to rediscover the maintenance bill about a year in. Move to Catalyst when a requirement demands it, and keep the app-compatibility audit at the front of the plan when you do.

A Sensible Middle Path

The choice can be revisited, and it can be partial. BigCommerce’s Multi-Storefront capability lets a single account run Stencil and headless storefronts side by side, which opens a low-risk pattern we like: launch or stay on Stencil for the main store, build a Catalyst storefront for a new brand, region, or campaign site, measure it against real traffic, and let the results decide the long-term direction.

Merchants who go this route learn what headless costs and delivers on a bounded project instead of a bet-the-company replatform.

Getting the Build Right Either Way

The two paths need different teams. A Stencil launch is a well-defined project with a known shape, and a partner who runs BigCommerce implementation projects regularly will bring a checklist that covers theme customization, app configuration, data setup, and launch, with a timeline you can trust.

A Catalyst build is software development. It needs BigCommerce development services with real Next.js depth, a plan for hosting and deployment, an app-compatibility audit before design starts, and a maintenance agreement for after launch, because the storefront is now code you own.

Both are good choices for the right merchant. Stencil is the right default for most stores, and it’s a better platform than its reputation among developers suggests. Catalyst is the right choice when a concrete requirement, a measured performance problem, or a composable strategy justifies owning a front end. Answer the questions above honestly, and the architecture chooses itself.

Leave a Reply

Your email address will not be published. Required fields are marked *