BigCommerce Headless Commerce: What Leaves With Stencil, and What Stays Behind
Your developer says the Stencil theme is holding back the redesign, and someone has suggested Catalyst. Going headless on BigCommerce means a separate front end, a Next.js site, a native app, even a kiosk, calls BigCommerce through its APIs, mostly the GraphQL Storefront API. BigCommerce still creates the orders and processes the payments. The storefront changes. The catalog, stock and customer records, and every system they sync with, stay where they are.
A Stencil theme next to a headless BigCommerce storefront
Stencil
- BigCommerce renders the pages from your theme.
- Marketplace apps that add reviews, badges or widgets to the storefront appear once installed.
- Design changes happen in the theme and Page Builder, inside what the theme allows.
Your own front end
- Your app renders the pages and asks the GraphQL Storefront API for products, carts and customers.
- Each storefront is set up as a channel with a channel site in BigCommerce.
- Storefront widgets from apps don't come along; each one is added to the new front end on purpose.
- Checkout can hand off to BigCommerce's hosted checkout, so card details never touch your front end.
Go headless for a front-end reason: design control, speed, or one catalog behind a website and an app. A slow or manual order sync is a separate problem, and a new storefront won't fix it.
Catalyst, your own framework, or keeping Stencil
Settle these before the Stencil theme is switched off
Which apps put something on the storefront today?
Reviews, loyalty, search and chat apps often show up through the theme. On a headless site each one needs its API or script added to the new front end, or it quietly disappears.
Hosted checkout, or a custom one?
Catalyst redirects to BigCommerce's one-page hosted checkout. A fully custom checkout built on the Checkout API means your team owns payments, tax and shipping display.
Where do product prices and stock really come from?
The storefront reads them from BigCommerce. If the ERP sets them, they have to reach BigCommerce first, headless or not.
Which back-office apps sync orders, and do any touch the theme?
Order and accounting syncs that run on the store's back end generally keep working. Ones that also inject storefront scripts need checking.
Who maps the old URLs to the new ones?
A new front end often changes paths. Search rankings and email links depend on redirects being in place on launch day.
The back-office work a new BigCommerce storefront doesn't remove
The front-end choice gets the meetings: which framework, which design system, which host. The connections that made the old store run get far less attention, and they're what fails first. Inventory from the warehouse, orders into accounting, customers into the CRM, contract prices from the ERP: all of it runs against BigCommerce's back end, and all of it still has to work on launch day.
n-frames builds that layer on BigCommerce's management APIs, so it doesn't depend on which storefront is live: Stencil today, Catalyst next quarter. Where an app's storefront feature didn't survive the move, we rebuild it as a direct API connection for the new front end. The BigCommerce API page covers which API does what, BigCommerce integrations covers the common back-office connections, and checkout customization covers changes to the checkout itself.
Leaving Stencil with the order, stock and price links already planned
n-frames lists every app and sync the current store depends on, marks which ones survive a headless move, and builds the back-office connections that have to be in place before the new storefront takes its first order.
Order and stock links for the new front end →Questions people ask
What is headless commerce?
A setup where the storefront shoppers see is built separately from the commerce platform behind it. The platform keeps the catalog, carts, checkout and orders, and the storefront talks to it only through APIs instead of the platform rendering its own pages.
Is BigCommerce headless by default?
No. A standard store runs on a Stencil theme that BigCommerce renders. Headless is a choice to build a separate front end against the GraphQL Storefront API, and to set it up as its own channel.
What is BigCommerce Catalyst?
BigCommerce's open-source headless storefront framework. It's a standard Next.js app that uses the GraphQL Storefront API and hands checkout to BigCommerce's hosted one-page checkout. You can deploy it to Vercel or any Next.js host. It's one way to go headless, not a requirement.
Do I need a developer to go headless on BigCommerce?
Yes. A headless storefront is an application to build, host and maintain, not a theme to customize. The back-office integrations are separate work that a store needs either way, and that's the part n-frames builds.
Will my BigCommerce apps still work if I go headless?
The back-office ones usually do, because they talk to the store's back end. Apps that add something to the storefront, such as reviews or loyalty widgets, don't appear on a headless site until they're added to the new front end through their API or script.