BigCommerce Limitations: What BigCommerce Cannot Do in 2026

For merchants evaluating ecommerce platforms in 2026, BigCommerce presents a familiar challenge: a traditional SaaS architecture adapting to meet modern commerce requirements. The platform's June 2026 pricing changes, introducing a new payment-provider fee, lowering revenue thresholds for plan auto-upgrades, and maintaining subscription functionality through apps, highlight considerations that growing brands should evaluate carefully. Headless commerce platforms built with API-first architecture from inception offer flexibility and native capabilities designed for modern commerce needs.

BigCommerce represents a significant presence in the ecommerce market. With headless commerce platforms attracting substantial investment and developer mindshare, understanding the differences between traditional SaaS and API-first capabilities helps inform platform decisions.

Key Takeaways

• BigCommerce's June 2026 pricing update introduced an Open Payment Provider Fee on self-serve plans for eligible order GMV processed through Open Payment Providers: 2.0% on Core, 1.0% on Growth, and 0.6% on Scale, changing the platform's transaction cost structure
• Revenue-based auto-upgrades now trigger at lowered trailing 12-month Inclusive GMV thresholds: $30K for Core (down from the former Standard plan's $50K) and $100K for Growth (down from the former Plus plan's $180K), affecting cost predictability for growing businesses
• BigCommerce's 600-variant maximum per product and reliance on apps for subscriptions create operational considerations that API-first platforms address through native unlimited variants and built-in recurring billing
• BigCommerce lists over 1,200 apps in its marketplace, while its headless capabilities via Catalyst remain newer than purpose-built API-first alternatives
• Some advanced B2B features become available on higher-tier plans, making capabilities like customer-specific pricing a consideration for mid-market wholesale operations

BigCommerce Transaction Fees and Cost Considerations

BigCommerce historically positioned itself without transaction fees on most payment processors. That changed in June 2026.

Understanding BigCommerce Fee Structures

Starting June 1, 2026, BigCommerce applies an Open Payment Provider Fee on self-serve plans for eligible order GMV processed through Open Payment Providers, determined at the order level:

• Core tier: 2.0% on eligible order GMV
• Growth tier: 1.0% on eligible order GMV
• Scale tier: 0.6% on eligible order GMV

Embedded Payment Providers, including Stripe, Adyen, PayPal Braintree, PayPal Complete Payments, PayPal Wallet, and others on BigCommerce's current embedded-provider list (21 providers in total), are not subject to the fee. The fee can also apply to offline orders, including manual payment methods such as purchase orders, when those count as Open Payment Provider volume, meaning wholesale customers paying on net terms can trigger fees despite no card gateway involvement.

The Impact of Plan Thresholds on Growth

Revenue thresholds compound cost considerations. BigCommerce auto-upgrades stores when trailing 12-month Inclusive GMV exceeds plan thresholds, with notice before changes. Inclusive GMV is gross order value after a 10% reduction. Core auto-upgrades to Growth above $30K TTM Inclusive GMV, and Growth auto-upgrades to Scale above $100K TTM Inclusive GMV. For Scale, BigCommerce lists a $33,333/month Inclusive GMV cap and a 0.9% overage on monthly Inclusive GMV above that cap. The same revenue that fit comfortably within previous thresholds now triggers earlier escalation.

Swell's approach provides an alternative. Swell applies revenue-based fees only above each plan's revenue ceiling, while merchants use their preferred payment gateway without percentage-based fees on every transaction. For current plan details, see the Swell pricing page.

Headless Architecture: BigCommerce vs Modern Platforms

The architectural differences between traditional SaaS platforms and purpose-built headless solutions affect long-term flexibility and development efficiency.

The Rise of Headless Commerce

BigCommerce was not originally designed as a headless platform; the company added REST APIs to existing traditional SaaS infrastructure. BigCommerce introduced Catalyst in 2024 as a composable storefront framework, and current documentation describes it as a customizable headless ecommerce storefront framework built with Next.js, React storefront components, and BigCommerce's GraphQL Storefront API.

Headless commerce enables faster performance through edge rendering and CDN delivery. One commerce backend can power multiple frontends: websites, native apps, in-store kiosks, and marketplaces without duplicating infrastructure.

Why API-First Matters for Future-Proofing

API-first platforms expose every component through programmatic interfaces from day one. Swell's developer-focused architecture means the same APIs powering the dashboard are available to developers. Anything possible in the admin interface can be replicated, customized, or extended through code.

BigCommerce's approach asks developers to work within framework conventions designed for traditional storefronts, then adapted for headless use cases. For merchants planning custom mobile apps, IoT integrations, or omnichannel experiences, starting with architecture designed for these use cases provides advantages.

Product Management: Scalability for Variants and Attributes

Product catalog flexibility determines whether platforms can grow with businesses or become constraints requiring workarounds.

Product Variant Considerations

BigCommerce supports a maximum of 600 SKUs/variants per product, which works for many businesses while creating a ceiling that complex catalogs eventually encounter. Merchants selling configurable products with multiple option sets (size, color, material, style, length) may approach this ceiling.

The workarounds create operational overhead:

• Splitting single products across multiple listings
• Managing inventory synchronization between related SKUs
• Creating fragmented product pages
• Complicating analytics and reporting

Future-Proofing Your Product Catalog

Swell removes these restrictions. Unlimited variants with custom data models mean product complexity doesn't force architectural compromises. The model editor allows creating custom fields on all standard models (products, orders, customers, carts), plus entirely custom data structures for business-specific requirements.

A jewelry brand can capture metal type, stone characteristics, and engraving details. A subscription box company can track dietary preferences. A B2B wholesaler can store net payment terms at the customer level. This happens as native platform functionality without third-party apps or workarounds.

Subscription Business Complexity: Recurring Revenue Considerations

Subscription commerce drives predictable revenue, and platform support varies between native and app-dependent approaches.

Third-Party Subscription Integration Approaches

BigCommerce requires an app or specific payment gateway for recurring billing and subscription functionality. Its marketplace lists recurring billing apps such as PayWhirl, Rebillia, Chargebee, and Ordergroove. This creates considerations:

• Additional monthly subscription fees
• Integration complexity between checkout and subscription management
• Customization within app-provided capabilities
• Data spread across platform and app

Third-party apps add cost layers that compound over time. A merchant managing app fees, platform fees, and transaction fees faces cost structures to evaluate carefully.

Building a Seamless Subscription Experience

Native subscription billing consolidates these dependencies. Swell provides built-in recurring revenue capabilities including:

• Flexible billing intervals (monthly, yearly, custom)
• Separate invoicing and fulfillment schedules
• Mixed carts combining subscription and one-time products
• Automatic payment retry with configurable dunning rules
• Customer self-service for pause/resume and plan changes

Swell's subscription engine works with any connected payment gateway through its encrypted card vault. There's no app to install, no additional subscription to manage, and no integration to maintain. Subscription capabilities ship as core platform functionality across all tiers.

Custom Checkout Experiences: Brand Control Considerations

Checkout optimization directly impacts conversion rates, and platforms approach checkout customization differently.

Optimizing Your Checkout for Conversions

BigCommerce's Page Builder offers design control through its interface. Deep checkout customization involves Stencil development expertise, with custom development representing a project investment for meaningful modifications.

The platform provides baseline checkout functionality, while merchants wanting branded experiences, custom fields, or non-standard payment flows can evaluate development requirements versus configuration options.

The Importance of API-Driven Customization

Swell offers two checkout paths at all tiers: hosted PCI-compliant checkout or custom checkout via API. The Checkout API can be used to build custom checkout and payment flows using the same APIs as Swell's hosted checkout, across all plans.

Guest checkout, abandoned cart recovery, and saved payment methods work out of the box. For businesses requiring complete checkout control, the API provides full flexibility while the hosted option handles compliance and payment security for merchants preferring simplicity.

Evaluating Extensibility and Integrations

App ecosystems extend platform capabilities, while ecosystem size and quality vary across solutions.

Understanding App Marketplace Approaches

BigCommerce lists over 1,200 apps and integrations in its Apps Marketplace, providing options for various functionality needs. The platform includes built-in features like native wishlists, persistent cart, and faceted filtering. Subscription billing, advanced product options, and deep checkout customization typically use external solutions or higher-tier plans.

Building a Future-Proof Integration Strategy

API-first platforms shift the integration paradigm. Rather than depending solely on app marketplace availability, developers build custom integrations directly against platform APIs. Swell provides native integrations with essential services:

• Klaviyo for email marketing
• ShipStation for fulfillment
• Avalara and TaxJar for tax calculation

APIs enable custom connections to services with programmatic interfaces. The Custom Swell Apps framework enables building full-stack extensions on the platform, providing developer-friendly extensibility.

International Commerce: Global Expansion Considerations

Global selling requires more than translated content. Multi-currency pricing, localized tax compliance, and regional payment support separate successful international operations from basic global presence.

Navigating Global Tax and Currency Challenges

BigCommerce offers multi-currency support, while explicit multi-currency pricing and granular tax rules can involve higher-tier plans or manual configuration. Merchants selling across multiple markets need:

• Currency-specific product pricing (psychological pricing differs by market)
• Regional tax compliance across jurisdictions
• Local payment method support
• Shipping zone configuration by geography

Swell's multi-currency functionality supports 230 currencies with explicit pricing rules per currency. Products, shipping, and discounts can all carry market-specific pricing. Tax calculation integrates with Avalara and TaxJar for region-specific compliance, with support for custom tax rule groups by location and product type.

Seamless Multilingual Customer Experiences

Content localization across 170 languages handles field-level translation for all customer-facing content: product names, descriptions, checkout instructions, and email notifications. Native localization provides automatic currency conversion and pricing adjustments alongside content translation.

Multi-storefront capabilities scale differently across platforms, while API-first platforms enable multi-region, multi-language storefronts through flexible frontend architecture.

Platform Flexibility for Unique Businesses

Standard ecommerce templates work for standard businesses. Unique business models benefit from platforms that adapt to requirements rather than mapping processes into predefined structures.

When Out-of-the-Box Needs Customization

BigCommerce's theme customization involves considerations for businesses with non-standard requirements. The platform offers free themes, with premium options. Customization beyond the drag-and-drop builder typically involves developer involvement and Stencil framework expertise.

Some B2B features become available at higher tiers. Customer-specific pricing, important for wholesale selling, is associated with the Pro or Enterprise tiers, a consideration for some mid-market operations.

The Power of Custom Data Models

Swell's architecture assumes every business has unique data requirements. Custom fields work across all standard models, enabling businesses to capture exactly the information their operations require. The model editor accessible through dashboard or API allows creating entirely custom data structures.

B2B and wholesale features including customer-specific pricing, custom payment terms, and bulk ordering workflows work across all tiers.

For merchants evaluating platforms in 2026, the question centers on whether BigCommerce's approach, new fee structures, and feature distribution align with growth trajectories and operational requirements. For subscription-first brands, complex catalog merchants, and businesses requiring headless flexibility, purpose-built API-first platforms deliver capabilities designed specifically for these use cases.

Frequently Asked Questions

How difficult is migrating from BigCommerce to an API-first platform like Swell?

Migration complexity depends primarily on catalog complexity, subscription data, and custom integrations rather than store size. The technical process follows data dependencies: products (no dependencies) first, then customers, orders, shipments, and subscriptions. Timelines vary by catalog complexity and scope, and proper planning tends to determine success more than store size. Subscription migration requires the most careful attention: active subscribers expect uninterrupted service, so billing schedule continuity and payment token migration are critical. Product catalogs approaching BigCommerce's 600-variant maximum benefit from restructuring during migration to take full advantage of unlimited modeling capabilities.

Does BigCommerce's Open Payment Provider Fee affect all payment methods?

No. Orders processed through Embedded Payment Providers, such as Stripe, Adyen, and PayPal Braintree, are not subject to the fee. Orders processed through Open Payment Providers on self-serve plans are subject to the fee at 0.6% to 2.0% depending on plan tier. The fee can also apply to offline orders and B2B transactions paid on net terms when those count as Open Payment Provider volume, meaning the cost impact extends beyond card transactions. Merchants invested in Open Payment Providers can calculate the annual fee impact when evaluating total platform costs.

Can BigCommerce support headless storefronts and custom mobile apps?

BigCommerce offers headless capabilities through the Catalyst framework introduced in 2024, with its GraphQL Storefront API and REST APIs supporting custom frontend development. The platform's traditional SaaS origins mean APIs were added to existing architecture rather than built as the foundation. This creates development considerations compared to platforms designed API-first from inception. Merchants planning sophisticated omnichannel experiences (custom mobile apps, IoT device integration, kiosk applications) can evaluate whether BigCommerce's headless approach or purpose-built API-first architecture better serves long-term development efficiency.

What are BigCommerce's B2B features for wholesale operations?

BigCommerce offers B2B tools, with some advanced capabilities available at higher tiers. Customer-specific price lists and some quoting workflows are associated with Pro or Enterprise tier plans. The 2026 pricing updates lowered revenue thresholds for plan upgrades while maintaining feature distribution across tiers. Mid-market wholesalers can evaluate which B2B capabilities their operations require and which tiers provide access to those features when calculating total platform investment.

How do subscription businesses operate on BigCommerce?

BigCommerce supports subscription commerce through an app or specific payment gateway, with marketplace apps such as PayWhirl, Rebillia, Chargebee, and Ordergroove providing recurring billing functionality. This approach involves additional app subscriptions, integration between checkout and subscription management, and working within app-provided capabilities. Businesses focused on subscription revenue can evaluate whether third-party app architecture or native subscription billing better aligns with their operational model and cost structure requirements.