BigCommerce’s Catalyst Framework Is Forcing Mid-Market Merchants to Choose Headless or Stay Put

BigCommerce is accelerating its push toward Catalyst — its Next.js-based composable storefront framework — and mid-market merchants who have been quietly running on Blueprint, the platform’s legacy theme architecture, are now facing a decision they can no longer defer. Catalyst, which exited beta in late 2025, is now the architecture BigCommerce recommends for new enterprise builds, and agency partners report that the platform has begun steering sales conversations firmly away from Blueprint-based projects.

For operators doing $5M to $50M in annual GMV on BigCommerce, the question isn’t whether to eventually migrate. It’s whether 2026 is the year to absorb that cost — or whether the disruption pushes them toward a platform switch entirely.

analytics dashboard view" loading="lazy" width="800" style="width:100%;height:auto;border-radius:8px;" />

What Exactly Is Catalyst and Why Is It Forcing a Decision Now?

Catalyst is BigCommerce’s opinionated headless frontend built on Next.js 14, using the platform’s GraphQL Storefront API and a component library called Makeswift for visual editing. Unlike the older Blueprint system — which is a server-rendered, template-based architecture similar to Shopify’s Liquid — Catalyst decouples the frontend entirely from BigCommerce’s backend commerce engine.

The framework is designed to give developers faster page load performance, more granular checkout control, and easier integration with third-party tools like Klevu, Yotpo, and Rebuy. But it requires a meaningfully different development skillset and infrastructure investment. Merchants running on Blueprint can’t simply “upgrade” to Catalyst — they’re rebuilding.

“Catalyst is genuinely the right architectural direction. The problem is BigCommerce hasn’t been transparent enough with merchants about what the transition actually costs. We’re seeing project scopes that merchants budgeted at $40K coming in at $120K once the full picture emerges.” — Jason Stokes, CEO, Eastside Co

💡 Article Summary

Key Insights

1

What Exactly Is Catalyst and Why Is It Forcing a Decision Now?

2

How Much Does a Blueprint-to-Catalyst Migration Actually Cost?

3

Are BigCommerce’s Enterprise Clients Actually Migrating to Catalyst?

4

Is BigCommerce Losing Mid-Market Merchants to Shopify Plus Over This?

5

What Does BigCommerce Need to Do to Retain Its Mid-Market Base?

Source: Ecommerce Times

Eastside Co, one of BigCommerce’s top-tier agency partners, has staffed up on Next.js talent specifically for Catalyst work, but Stokes says smaller merchant teams are getting sticker shock when agencies scope out the full migration, including data migration, app compatibility audits, and QA cycles.

How Much Does a Blueprint-to-Catalyst Migration Actually Cost?

Agency estimates collected by Ecommerce Times from five BigCommerce partners put the median Catalyst migration for a mid-market merchant — defined here as 5,000 to 50,000 SKUs, 3 to 8 integrated apps, and a single storefront — at between $65,000 and $180,000 in development costs, depending on customization depth. That range does not include ongoing hosting infrastructure, which Catalyst merchants must provision independently, typically on Vercel or Netlify.

• Vercel Pro plan: Starts at $20/month per member but enterprise contracts for high-traffic storefronts commonly run $2,000–$8,000/month
• Netlify Enterprise: Similar pricing range, with bandwidth costs adding up for merchants doing meaningful traffic volume
• Makeswift visual editor licensing: Now bundled into Catalyst but previously a separate line item that some merchants still carry
• GraphQL API call volume: High-SKU catalogs with frequent search and filter interactions can generate substantial API usage costs if not architected carefully

For merchants currently on BigCommerce’s $400–$1,000/month standard enterprise tiers, those infrastructure costs represent a meaningful new line item that wasn’t part of their original platform budget.

“The TCO conversation is where deals are stalling. A merchant pays BigCommerce $600 a month and thinks that’s their platform cost. Catalyst changes the math — you’re now buying compute, CDN, and developer hours on top of your license. It’s not a bad deal if you need the performance, but nobody is walking merchants through it clearly.” — Bridget Johns, VP of Strategy, Logical Position

Are BigCommerce’s Enterprise Clients Actually Migrating to Catalyst?

According to three agency partners who spoke with Ecommerce Times, the Catalyst adoption curve among existing BigCommerce merchants is slower than the platform’s public positioning suggests. New greenfield projects — brands building on BigCommerce for the first time, often coming from Shopify Plus or Magento — are more likely to launch on Catalyst. But the installed base of Blueprint merchants is largely sitting still.

BigCommerce has not published specific Catalyst adoption figures. A spokesperson declined to provide merchant count data but said the platform has seen “significant growth in Catalyst-based storefronts in Q1 and Q2 2026.”

One area where Catalyst is gaining genuine traction: B2B merchants and manufacturers using BigCommerce’s B2B Edition product, which includes buyer portal functionality that integrates more cleanly with Catalyst’s component architecture than with Blueprint. Multiple agency sources named custom B2B portal builds as the strongest near-term Catalyst use case.

• Brands with complex pricing rules (tiered, customer-specific, negotiated contracts) are finding Catalyst’s API-first model easier to extend
• Merchants operating multiple storefronts in different geographies are using Catalyst’s multi-tenant architecture to reduce duplication
• Wholesale operators who previously ran separate Shopify Plus and BigCommerce storefronts are consolidating onto single Catalyst deployments

Is BigCommerce Losing Mid-Market Merchants to Shopify Plus Over This?

Platform migration activity data from Akeneo’s 2026 Commerce Platform Report — published in April — shows BigCommerce-to-Shopify Plus migrations increased 22% year-over-year in Q1 2026 among brands in the $10M–$75M revenue range. Agency sources attribute a portion of that churn directly to the Catalyst transition friction.

The competitive dynamic is real: Shopify’s Hydrogen framework, while also headless and also requiring development investment, benefits from Shopify’s dramatically larger app ecosystem and the widely-held perception that Shopify’s platform continuity risk is lower. For a merchant that already relies on Klaviyo, Gorgias, Rebuy, and Yotpo — all deeply integrated with Shopify — the switching cost calculation sometimes flips in Shopify’s favor even when BigCommerce’s licensing cost is lower.

“When a merchant is already looking at $100K in Catalyst work, they start asking why they’re not just moving to Shopify Plus where their whole stack is already native. We’ve had three clients in the past four months where that’s exactly what happened. BigCommerce won them on price but lost them on migration complexity.” — Marcus Webb, Managing Director, Velvet Commerce

BigCommerce counters that its open API architecture, absence of transaction fees, and stronger native B2B tooling differentiate it from Shopify in ways that matter at scale. That argument holds more weight at $50M+ GMV where Shopify Plus fees and app costs compound meaningfully. But in the $5M–$20M band, the equation is less clear.

What Does BigCommerce Need to Do to Retain Its Mid-Market Base?

Agency partners and merchants consulted for this article converged on several near-term actions they say BigCommerce needs to execute to stem blueprint-era churn:

• Publish a formal Blueprint sunset timeline — even a 24-month runway would give merchants planning certainty. The current ambiguity is itself a migration trigger.
• Launch a funded migration program — a structured agency subsidy or merchant credit toward Catalyst migrations, similar to what Salesforce Commerce Cloud has done historically during major architectural transitions
• Simplify Vercel/Netlify procurement — a preferred infrastructure partnership with transparent, bundled pricing would remove a major source of TCO confusion
• Publish reference architecture for common mid-market stacks — documented, proven Catalyst configurations for merchants running Klaviyo + Gorgias + Yotpo + Rebuy would reduce agency scoping risk and speed project starts

BigCommerce’s product team, led by Chief Product Officer Brian Dhatt, has signaled awareness of the adoption friction. In a May 2026 partner briefing, Dhatt acknowledged that the platform is working on “guided migration tooling” and “enhanced Makeswift templates” designed to reduce time-to-launch for mid-market Catalyst projects. No specific release dates were provided.

“We’re not walking away from the merchants who built their businesses on Blueprint. But we do believe Catalyst represents where performant commerce has to go, and our job is to make that path as clear and as affordable as we can make it.” — Brian Dhatt, CPO, BigCommerce (from May 2026 partner briefing)

What Should Mid-Market BigCommerce Merchants Do Right Now?

For operators currently on Blueprint who are not facing immediate performance issues or feature gaps, the practical guidance from agency partners is consistent: don’t migrate reactively, but do audit your position now.

Specifically, merchants should request a formal Catalyst readiness assessment from their agency or a BigCommerce-certified partner — most partners offer this at no cost as a scoping exercise. The assessment should include an app compatibility audit (not all BigCommerce apps have Catalyst-native integrations), an infrastructure cost model for Vercel or Netlify at current and projected traffic, and a realistic development timeline with contingency.

Merchants within 18 months of a planned site redesign anyway should strongly consider accelerating toward Catalyst rather than investing further in Blueprint customization that will eventually need to be rebuilt. For merchants with stable storefronts and no redesign on the roadmap, a 12-month monitoring posture — watching for BigCommerce’s migration tooling releases and any Blueprint support policy changes — is defensible.

What’s not defensible: ignoring the architectural shift entirely and discovering in 2027 that Blueprint support has been formally deprecated on a timeline that doesn’t match your budget cycle.