What we build on BigCommerce
The work we are asked for most on BigCommerce.
Stencil themes
Custom or extended Stencil themes with Page Builder regions your team can edit.
Multi-storefront
Several brands or regions from one control panel.
B2B Edition
Company accounts, quotes, price lists and buyer portals.
Catalyst storefronts
Headless storefronts on Next.js using the GraphQL Storefront API.
Catalogue modelling
Variants, modifiers and option sets planned before import.
ERP and app wiring
Orders, stock, prices and customers synced with your ERP.
Speed work
Lean themes and scripts that keep Core Web Vitals green.
Is BigCommerce the right home for you?
A strong SaaS choice for big catalogues and several storefronts, with a few trade-offs.
Teams choose BigCommerce for
- Several storefrontsBrands or regions run from one back office.
- Large cataloguesMany products, variants and options handled natively.
- Open APIsREST and GraphQL APIs for headless and integrations.
- Built-in B2BB2B Edition for wholesale buyers.
When it is not the right fit
- App ecosystem breadthFewer third-party apps than the largest platforms.
- Full server controlIt is SaaS; you cannot run code on its servers.
- Tiny, simple storesA small catalogue may not need its strengths.
- Team familiarityFewer in-house developers know Stencil.
Stencil, Catalyst or a custom headless front end?
BigCommerce lets you keep the back office and swap the front end. That freedom is useful, and it is also where budgets double without anyone planning it. How each option behaves.
Stencil theme
The standard, hosted theme layer
Stencil themes are Handlebars templates, SCSS and a bit of JavaScript, hosted and served by BigCommerce. Page Builder gives your team drag-and-drop regions on top. You get BigCommerce’s own checkout, its caching and its CDN without running a server.
We build or extend a Stencil theme for most stores, and we keep the JavaScript light so mobile scores stay healthy.
Right for most catalogues
If your problem is merchandising, catalogue structure or speed, Stencil solves it for the least money. Most of the stores that ask us about headless don’t need it yet.
Watch out for: theme apps that inject scripts, and Page Builder widgets used as a substitute for a proper template.
Catalyst
BigCommerce’s own Next.js storefront
Catalyst is an open-source React storefront built on Next.js that reads products, carts and customers through the GraphQL Storefront API. It ships with sensible pages out of the box, so you start from a working store rather than a blank repo.
You host it yourself, typically on Vercel or a similar platform, and checkout still runs on BigCommerce.
Headless with a head start
When a store truly needs a React front end, Catalyst is where we start. It saves weeks of plumbing compared with building from nothing.
Watch out for: you now own deployments, preview environments and front-end monitoring. Budget for that every month, not just at launch.
Custom headless
Your own front end on BigCommerce APIs
A front end in any framework, or a content platform such as a headless CMS, talking to the GraphQL Storefront API for shopping and to the REST Management API for back-office jobs. Useful when the store is one part of a bigger app or content site.
Only with a strong reason
We’d choose this only when an existing product or site must host the store. Everything Stencil gives you for free becomes code someone writes and maintains.
Watch out for: search, filtering and SEO metadata, which all need rebuilding.
How BigCommerce integrations talk to the store
BigCommerce exposes two families of API, and knowing which one a job belongs to saves a lot of debugging later.
Read the detail: How BigCommerce integrations talk to the store
The REST Management API runs the back office
Products, variants, price lists, customers and orders are managed over REST. Catalogue work uses the V3 endpoints; some order operations still sit on the older V2 endpoints, which is normal and nothing to worry about. Each store has a rate limit that depends on its plan, and BigCommerce tells you how many requests are left in the response headers, so a well-built sync slows itself down before it is refused.
The GraphQL Storefront API serves shoppers
Headless storefronts, including Catalyst, read products and manage carts through GraphQL with a storefront token. It is designed for the shopper’s view of the catalogue, with customer-specific pricing when a shopper is signed in.
Webhooks tell you something changed, not what
A BigCommerce webhook carries little more than the record type and ID. Your integration then fetches the full order or product. That design keeps webhooks small, but it means every event costs at least one API call, which matters on a busy sale day. We queue those fetches so a burst of orders never trips the rate limit.
If you want the ERP side of this, our Acumatica and NetSuite pages walk through the other half of the sync.
The webhook says “order 10482 changed”. It doesn’t say how, so a good BigCommerce sync depends on handling that second call well.
BigCommerce, wired into the rest
Systems we most often connect to BigCommerce stores.

A BigCommerce build, start to launch
- Week 0
Audit call
Your catalogue, channels and ERP in 30 minutes.
Gap list - Weeks 1–2
Catalogue plan
Products, options and storefronts modelled.
Catalogue map - Weeks 3–9
Build
Themes or Catalyst, B2B and integrations, demoed weekly.
Staging store - Weeks 10–11
Test
Orders, payments, tax and sync tested end to end.
Test report - Week 12+
Launch and run
Go-live and redirects, then support or hand-over.
Live store
What makes a BigCommerce project cost more, or less
We can’t give you a number before the audit, but we can tell you which levers move it. Typical ranges are in the pricing section below.
Pushes the cost up
- Several storefrontsEach storefront in a multi-storefront set-up has its own theme settings, domains, channel listings and tests.
- Messy option setsProducts built from modifiers and old option sets need remodelling before they can be imported cleanly.
- B2B Edition rulesBuyer roles, approval flows, quotes and per-company price lists each add build and test time.
- Going headlessA Catalyst or custom front end adds hosting, deployment and front-end QA to every release.
Keeps it down
- A clean catalogue exportConsistent SKUs and one source of product truth cut the catalogue phase by weeks.
- Extending a good themeStarting from a solid Stencil theme instead of a blank one is usually the cheapest route to a new look.
- Fewer apps, chosen earlyAgreeing the app list in planning avoids rebuilding templates around a late addition.
- One decision-makerWeekly demos go faster when one person can say yes on the call.
BigCommerce builds and what they cost
Typical ranges. Your fixed quote follows the free audit, and nothing is billed before you agree it.
Theme refresh
from $8,5004–6 weeks
- Stencil theme extended
- Key templates redesigned
- Speed budget applied
Full store build
from $18k8–14 weeks
- Custom Stencil theme
- Catalogue and apps
- ERP sync through a workflow engine
Multi-store, B2B or Catalyst
from $30k12–16 weeks
- Several storefronts or B2B
- Headless Catalyst option
- Two months of support
About BigCommerce development
Anything else, ask on the audit call.
Ask an engineer
Not answered here? Ask on the free 30-minute audit call. An engineer replies within one business day.
Quick facts
- Based in Delhi, India Working across time zones, with written weekly updates.
- Fixed quote first Nothing is billed before you agree it.
- You own it The code, workflows and accounts are yours.
- Stores and ERPs Shopify, BigCommerce, WooCommerce and Adobe Commerce, with NetSuite, SAP Business One, Odoo and Dynamics 365.
Is Intelligize Digital a BigCommerce Partner?
Yes. Intelligize Digital is a member of the BigCommerce Partner Program.
What is Catalyst?
Catalyst is BigCommerce’s Next.js storefront for headless builds. Intelligize Digital recommends it when you want a React front end and have a team ready to own and host it.
Can one BigCommerce account run several brands?
Yes. Multi-storefront lets several storefronts share one control panel, catalogue and order management, each with its own domain, theme and settings.
Do you build B2B on BigCommerce?
Yes. Intelligize Digital sets up B2B Edition for company accounts, buyer roles, quotes and price lists, and connects it to your ERP for terms and credit.
Stencil or headless?
Stencil for most stores: faster to build and simpler to run. Headless when the front end itself is the product and you can maintain it.
Can you connect BigCommerce to our ERP?
Yes. We sync orders, stock, prices and customers with NetSuite, Acumatica, Business Central or Odoo using a workflow engine, a custom integration or a proven connector.
Does BigCommerce have API rate limits?
Yes. Each store has a request quota that depends on its plan, and the remaining allowance is returned in response headers. Intelligize Digital queues and paces calls against those headers so syncs slow down before they are refused.
Why does our BigCommerce integration make so many API calls?
BigCommerce webhooks only carry the record type and ID, so the integration has to fetch the full order or product after each event. That is expected. A good integration batches and queues those fetches so busy days stay within limits.
Can BigCommerce handle wholesale and retail in one store?
Yes. With B2B Edition, retail shoppers see standard prices while signed-in company buyers get their own price lists, quotes and payment terms. Intelligize Digital sets this up and connects it to the ERP that holds credit limits.
What does Catalyst cost to run?
Catalyst itself is open source, but you pay to host it and someone has to maintain it. Hosting costs depend on traffic and provider; the bigger cost is the developer time for updates and releases, which Intelligize Digital includes in any headless estimate.
BigCommerce terms you’ll hear in the project
Short definitions for the words that come up in scoping calls.
- ThemeStencilTap for a short definition
- StencilBigCommerce’s hosted theme framework: Handlebars templates, SCSS and JavaScript, served by BigCommerce.
- HeadlessCatalystTap for a short definition
- CatalystBigCommerce’s open-source Next.js storefront for headless builds, reading the GraphQL Storefront API.
- Set-upMulti-storefrontTap for a short definition
- Multi-storefrontSeveral storefronts, each with its own domain and theme, sharing one catalogue and one order list.
Read the detail: BigCommerce terms you’ll hear in the project
- WholesaleB2B EditionTap for a short definition
- B2B EditionBigCommerce’s B2B add-on for company accounts, buyer roles, quotes, shopping lists and price lists.
- CatalogueVariantTap for a short definition
- VariantA buyable version of a product, such as size 9 in blue, with its own SKU, stock and price.
- CatalogueModifierTap for a short definition
- ModifierAn option that changes the order but not the stock record, such as engraving text or gift wrap.
- PricingPrice listTap for a short definition
- Price listA set of prices assigned to a customer group or channel, used for wholesale tiers and regional pricing.
- IntegrationChannelTap for a short definition
- ChannelWhere you sell: a storefront, a marketplace or a POS. Listings and inventory can differ per channel.
Related BigCommerce reading
How many storefronts
are you running?
Tell us your catalogue, channels and ERP. An engineer replies within one business day.
What happens next
- An engineer replies Within one business day, by email.
- A free 30-minute audit On a call with an engineer.
- A fixed quote It follows the audit. Nothing is billed before you agree it.