BigCommerce · Development
BigCommerce development agency
Development on BigCommerce runs in two lanes. Stencil theme work covers the storefront, and API work covers everything the store connects to. The platform runs the infrastructure, so engineering effort goes into templates, integrations and, when a front end needs to move further than a theme allows, a build on the storefront APIs.
What BigCommerce changes
Platform facts that shape the work
These are true of BigCommerce today and they decide the approach before any strategy does.
Stencil is the theme framework
Themes are Handlebars templates with a local development workflow, so changes are written in code, previewed and versioned rather than edited on a live store. Page Builder regions sit on top for content merchandisers can edit themselves.
The platform runs the infrastructure
Hosting, scaling and the content network belong to BigCommerce. You cannot tune a database or add a caching layer, which means performance engineering happens in templates, image handling and third party scripts.
APIs cover catalog, orders and customers
Documented REST APIs and webhooks support integrations with resource planning, product information, fulfillment and marketing systems. Rate limits differ by plan, so a high volume integration needs designing around them from the start.
Checkout can be rebuilt on your domain
The platform provides a toolkit for building a custom checkout served from the store's own domain. That is unusual among hosted platforms and useful where a business has requirements the standard checkout cannot express.
Storefront APIs allow a headless front end
A custom front end can be built on the storefront APIs while the platform keeps catalog, cart and checkout. That supports moving in stages rather than committing to a full replatform in one release.
One back office serves several storefronts
Multiple storefronts can run from one catalog and one order pipeline. Development effort then goes into the differences between them rather than into keeping separate stores in step with each other.
The work
Item by item, inside BigCommerce
Theme development
Templates built or refactored in Stencil with a local workflow and version control, Page Builder regions defined so merchandisers have room to work, and component behavior kept consistent across product, category and content pages.
Performance engineering
Script inventory reduced and scoped, images sized and formatted through the platform's handling, template rendering simplified where widgets have accumulated, and the result measured on the devices customers actually use.
Integration build
Connections to fulfillment, accounting, product information and marketing systems built on the APIs and webhooks, with retry handling, idempotency and monitoring, because a sync that fails silently costs more than one that fails loudly.
Checkout and payment work
The default checkout configured as far as it will go, with a custom build scoped only where the business case is clear, and payment method behavior tested across devices and card outcomes rather than only on the happy path.
Catalog and data operations
Bulk catalog work, option and variant restructuring, price list management and imports handled through the APIs, with a rehearsal on a sandbox before anything touches the production catalog.
Headless where it is warranted
A front end on the storefront APIs when the requirement genuinely exceeds a theme, scoped so the platform keeps cart and checkout and the team takes on rendering, routing and measurement knowingly.
Release process
A sandbox that mirrors production, theme versions in source control, a documented deployment routine and checks that exercise checkout and integrations, so a release is a routine step rather than an event.
What goes wrong
On BigCommerce, specifically
- Editing a theme directly in the admin so the next deployment overwrites the change
- Building a custom checkout because the default looks unfamiliar rather than because it loses orders
- Designing an integration without reading the plan's rate limits, then discovering them during a catalog import
- Adding widgets to Page Builder regions until the template no longer performs on mobile
- Going headless for the front end while the team has no capacity to maintain a second codebase
When is a custom checkout worth building on BigCommerce?
When a business requirement cannot be expressed in the standard checkout and the lost revenue can be quantified. Regulated products, complex delivery choices and unusual payment flows are real cases. Preference for a different layout is not, because the custom build carries ongoing maintenance.
How do BigCommerce API rate limits affect integrations?
They set the pace of bulk work. Catalog imports, inventory syncs and order exports have to be batched and throttled, and a design that assumes unlimited calls will fail during the busiest week rather than during testing. We size integrations against the plan the store is actually on.
Should a BigCommerce store go headless?
Only when the front end requirement genuinely exceeds what Stencil can do and the team can maintain a separate application. Going headless moves rendering, routing, caching and measurement onto your side. It buys flexibility and it is a permanent increase in engineering commitment.
How are BigCommerce themes kept maintainable?
Keep theme code in version control, develop locally rather than in the admin, keep customization in components with clear responsibilities, and record which Page Builder regions exist and what they are for. Most difficult BigCommerce themes we meet were edited live over several years by several teams.
Can BigCommerce handle a complex catalog?
It handles substantial catalogs well, with platform limits on things like variant counts per product that shape how complex products are modeled. Where a product has very many combinations, the usual approach is to reconsider the option structure rather than to fight the limits.
The service behind it
More on BigCommerce
Grow on BigCommerce.
A free Growth Analysis ranks what your store should fix first, by revenue at stake.