BigCommerce

BigCommerce Catalyst explained: headless without starting from scratch

BigCommerce Catalyst is a Next.js headless storefront you own. Here is how it compares with Stencil and custom builds, what it costs to run and who it suits.

BigCommerce Catalyst is BigCommerce's official headless storefront framework, built with Next.js, React and the GraphQL Storefront API. It gives you a working store front end (home page, category and search pages, product pages, cart, account area and a redirected checkout) as open source code you own and style yourself. In short, it is headless BigCommerce without starting from a blank repository.

This guide explains what Catalyst includes, how it compares with Stencil and a fully custom build, what it costs to run, who it suits, and the practical points that decide whether a Catalyst project goes well.

What is BigCommerce Catalyst?

BigCommerce describes Catalyst as its composable, fully customisable headless storefront framework. It is a standard Next.js application released under the MIT licence, so the code is free to use and change. It uses React server components and Suspense, and its components are styled with Tailwind CSS. Visually it starts as a deliberately plain design that you shape to your brand.

Out of the box, Catalyst ships a production-ready business-to-consumer funnel:

  • Home page
  • Category and brand listing pages with faceted search
  • Full-text search
  • Product detail pages generated for every product in the Catalyst channel
  • Shopping cart
  • A redirected checkout hosted by BigCommerce, which can be themed to match the storefront
  • Customer accounts with addresses, settings and order history

The checkout point matters more than it looks. Because checkout runs on BigCommerce's hosted environment, card details never pass through your Next.js application. That keeps the front end largely out of PCI scope, which is one of the hardest parts of going headless on your own.

Makeswift visual editing

BigCommerce acquired Makeswift, a visual page builder for Next.js sites, in late 2023 and integrated it with Catalyst. Catalyst comes in two variants: a core version without Makeswift and a Makeswift-connected version. Marketers can then build landing pages and edit content visually, while developers register their own React components for the editor to use.

If you create a storefront with One-Click Catalyst in the BigCommerce control panel, you get the Makeswift version automatically, plus a hosted preview. If your developers set it up from the command line, Makeswift is not included unless they choose that variant. Decide early which you want, because it shapes how your team will manage content.

Where Catalyst is hosted

BigCommerce documents and tests two hosting options. Storefront Hosting is BigCommerce's own service, built on Cloudflare, billed on your BigCommerce invoice and managed through the Catalyst command line tool. At the time of writing (October 2026) it is in closed beta. The second is Vercel, a third-party Next.js host with its own subscription. You can also use another provider, but it must run a Next.js server, because Catalyst renders pages on request and does not support static exports.

Catalyst vs Stencil vs fully custom headless

BigCommerce now offers three ways to build a storefront. Stencil is the traditional theme framework, using Handlebars templates, fully hosted by BigCommerce. Catalyst is the Next.js headless option. Fully custom headless means building your own front end, in any framework, against BigCommerce's APIs. The table below draws on BigCommerce's own storefront comparison.

Feature Stencil Catalyst Fully custom headless
Front end technology Handlebars, SCSS, JavaScript Next.js, React, GraphQL Any framework you choose
Hosting Included, run by BigCommerce Storefront Hosting (closed beta), Vercel or another Next.js host Your own hosting
Starting point Theme from the marketplace Working storefront code Blank project
Design freedom Within the theme framework Full Full
Storefront apps from the App Marketplace Broadly supported Back-office apps work; most storefront apps do not Custom integration needed
Visual editing Page Builder Makeswift (optional variant) Your own CMS
Ongoing technical ownership Low Medium: code, hosting, upgrades High: everything
Best for Fast, low-maintenance stores Brands that want headless with a head start Unusual requirements or a non-React stack

Stencil remains the right answer for many brands. If your theme does what you need and your team relies on storefront apps, there is no prize for going headless. Catalyst makes sense when you have outgrown what a theme can do and want control of the front end without paying to rebuild cart, search, account and checkout plumbing.

What Catalyst does not do yet

Catalyst runs on the GraphQL Storefront API, and BigCommerce is clear that this API does not cover every platform feature. Its feature support matrix is worth reading line by line before you commit. At the time of writing it lists, among others:

  • Storefront apps that change front end behaviour generally do not work
  • Store-wide promotional banners and the native Meta Pixel integration are not supported
  • Abandoned cart recovery links cannot yet be applied to the Catalyst cart
  • Returns need a partner solution
  • The B2B Edition buyer portal integration is experimental
  • The sitemap does not include pages created in Makeswift

Because you own the code, most of these can be built. The question is whether building them is worth it for your business, and that belongs in the budget before the project starts, not halfway through.

What it costs to run Catalyst

The Catalyst code is free. The costs sit around it:

  • Your BigCommerce plan. Catalyst does not replace it. Products, orders, promotions and checkout all stay in BigCommerce.
  • Hosting. Either Storefront Hosting on your BigCommerce invoice, which BigCommerce recommends for new Catalyst storefronts, or a separate Vercel subscription. Usage-based hosting bills grow with traffic, so model your peak periods.
  • Build time. Catalyst saves you building the commerce basics, but design, content, integrations and any unsupported features still need development.
  • Upgrades and maintenance. BigCommerce releases new Catalyst versions regularly, including security updates when Next.js publishes them. Someone has to apply those, test them and deploy them. With Stencil, much of that is handled for you.

We do not quote hosting prices here because they depend on your traffic and plan. Ask your hosting provider and BigCommerce account manager for figures based on your real visitor numbers.

Who Catalyst suits

Catalyst is a good fit if you:

  • Want a fast, highly custom front end and have outgrown theme limits
  • Have, or can retain, React and Next.js developers
  • Sell in several countries or languages and want one codebase
  • Run content-heavy campaigns and want marketers editing pages visually through Makeswift
  • Rely mainly on back-office apps rather than storefront widgets

It is probably not for you if you have no development support after launch, depend on several storefront apps, or simply need a cleaner theme. In those cases a well-built Stencil store, or a design refresh, is cheaper to run and easier to own.

Practical tips for a Catalyst build

Get caching right first

Catalyst uses Next.js request memoisation and the Data Cache. By default, product data is cached for guest shoppers and fetched fresh for signed-in customers, whose prices and visibility can differ by customer group. Catalyst also caches route data in a key-value store. On Storefront Hosting and Vercel this is set up automatically. On any other host you need to configure an external key-value store, otherwise route data is held only in memory and is not shared between servers. A large, frequently updated catalogue usually needs webhook-driven cache refreshes rather than long fixed timers.

Server rendering and speed

Catalyst renders pages on the server, which is good for search engines and first load, but only if every slow call is cached or deferred. Watch third-party scripts closely: one heavy tag can undo the framework's performance work. We look after L'azurde, a headless BigCommerce and Next.js jewellery store (not built on Catalyst), where a focused round of speed work took the mobile homepage PageSpeed score from 42 to 93. The lesson carries over: the framework gives you a fast starting point, but speed is kept through discipline. Our L'azurde case study has the detail.

SEO

Catalyst serves BigCommerce's sitemap index from your domain, but pages built only in Makeswift are not included, so submit a separate sitemap for them if they matter for search. If you are moving from Stencil, map every URL and plan redirects before launch, and check canonical tags, structured data and hreflang on each template. Treat it like any platform migration and monitor rankings for at least the first few months.

Multi-storefront and international

Out of the box, one Catalyst project serves one domain. You can map locales to separate BigCommerce channels under subpaths (for example /fr and /de) from a single project, or deploy one project per domain. Each channel can carry its own payment methods, shipping, promotions and catalogue for its market.

Languages

Catalyst uses next-intl for translations. Fixed interface text lives in per-locale message files, while translated product data comes from BigCommerce. Every locale you enable needs its own message file, otherwise its pages return a 404. For right-to-left languages such as Arabic, test layouts, carousels and icons on real devices early. It is easy to treat as a final polish step and expensive to fix late.

FAQs

Is BigCommerce Catalyst free?

The Catalyst code is free and open source under the MIT licence. You still pay for your BigCommerce plan, hosting, development and ongoing maintenance.

Do I need Vercel to use Catalyst?

No. BigCommerce supports its own Storefront Hosting (in closed beta at the time of writing) and Vercel. Other hosts work if they can run a Next.js server with the features Catalyst relies on.

Can I move from Stencil to Catalyst?

Yes. Your catalogue, customers and orders stay in BigCommerce, so the move is a front end rebuild rather than a full replatform. Check apps and features against the support matrix, and plan redirects and SEO checks as you would for any migration.

Does Catalyst work with Next.js developers I already have?

Yes. It is a standard Next.js application, so any experienced React and Next.js team can work on it, provided they also understand the GraphQL Storefront API and BigCommerce channels.

How Superior can help

We are an official BigCommerce Partner and look after headless BigCommerce and Next.js stores as well as Stencil builds. If you are weighing up Catalyst, Stencil or a custom front end, talk to our BigCommerce team and we will give you an honest view of which route fits your catalogue, team and budget.

All insights

Start a project

Want help with this?

Tell us about your store. We reply within one working day with next steps.

Prefer email? hello@superiorecom.com