What happened
Catalyst — BigCommerce's Next.js storefront framework — now renders product prices as Inc. Tax, Ex. Tax, or Both in version 1.8.0, driven by the store's existing Tax Display setting. No custom pricing logic, no workaround components: the storefront honors the same control the store already has. BigCommerce calls it the close of a long-standing gap for EU and UK Catalyst storefronts, which is accurate.
The release also ships a new channel link CLI command. It connects a Catalyst project to a storefront channel and writes the credentials into .env.local automatically, replacing the manual copy-paste of tokens that started every new build.
Why this matters
Headless adoption rarely dies on performance — it dies on unglamorous compliance gaps. Showing tax-inclusive prices is table stakes for consumer retail in VAT markets; shoppers there expect the number on the page to be the number they pay. Without it, Catalyst was disqualified for a large slice of merchants before any speed benchmark mattered. If that's why you passed on Catalyst, your evaluation is now stale — the framework didn't just improve, it became eligible.
The CLI change is smaller but real. Every manual credential step in a build is a chance to leak a token, misconfigure an environment, or burn an afternoon debugging a typo. Automating it matters most for teams standing up multiple storefronts — which is exactly the multi-storefront, multi-region merchant the tax fix just re-invited. It also removes a class of onboarding mistakes that otherwise surface as production incidents weeks later, when nobody remembers which token went where.
Keep some skepticism on hand, though. One closed gap doesn't make headless the default answer. Catalyst still means owning a codebase, a deploy pipeline, and a developer relationship for the life of the storefront. Stencil remains the right call for plenty of stores — the question is whether headless buys you something specific, not whether it's current. The stores that regret headless migrations are almost always the ones that couldn't answer that question before signing the statement of work.
What to do about it
Re-open the Catalyst evaluation if tax display killed it
Spin up a 1.8.0 sandbox, cycle the store's Tax Display setting through Inc. Tax, Ex. Tax, and Both, and verify what renders on category pages, product pages, and the cart. Confirm it against your actual VAT presentation requirements before anyone books a migration.
Use channel link on your next build
Adopt the command in your setup checklist so credentials land in .env.local without manual handling. Then make sure .env.local is in .gitignore and stays out of version control — an automated write is convenient right up until it gets committed.
Write down why you'd go headless before you go
One page: the specific things Stencil can't deliver for your store — features, integrations, performance targets with numbers attached. If the page comes back empty, stay on Stencil and spend the budget on catalog data and SEO, where the return is measurable. Revisit the page yearly — the answer changes as your store does.