Overview
BigCommerce is built as an "Open SaaS" platform -- API-first architecture (REST and GraphQL APIs for both admin and storefront) that supports both traditional theme-based storefronts (using the Stencil framework) and fully headless/custom frontends built on the same backend catalog and order management.
Implementation Context
A concrete differentiator worth knowing: BigCommerce doesn't charge a transaction fee for using a third-party payment gateway, unlike some competing platforms that add a fee unless you use their own native payment processor. Plan tiers (Standard, Plus, Pro, Enterprise) are gated partly by online sales revenue thresholds, so a growing store can be required to upgrade based on GMV, not just a feature need.
Key Considerations
- Decide between a theme-based Stencil storefront and a fully headless build early, since this shapes your whole implementation approach.
- Confirm current transaction-fee policy for your chosen payment gateway, since not charging a fee for third-party gateways has been a real BigCommerce differentiator.
- Check your plan tier's online sales revenue threshold, since exceeding it can require an upgrade regardless of feature needs.