Skip to content
Tutorials Center
My learning

Topics

Lesson 1 of 28 ยท Getting Started

What Is BigCommerce Development?

Learn what BigCommerce development is: the SaaS model, what you can build (apps, Stencil themes, headless storefronts, integrations) and how this course teaches it.

BigCommerce is a software-as-a-service (SaaS) commerce platform. A merchant signs up, and BigCommerce runs the servers, the database, the checkout, the payment connections and the security patches. You never log in to a machine that hosts the shop. This is the biggest difference from self-hosted platforms such as Magento or WordPress, where you own the whole PHP codebase and the server.

That model shapes what a developer does. You do not change the platform's core code, because you cannot reach it. Instead you work through extension points that BigCommerce publishes: HTTP APIs, webhooks, a theme system, a widget system and a few hosted settings. This course teaches those extension points one by one, from your first API call to a headless product page.

What you can build

There are four broad kinds of work. Most projects mix them.

  1. Integrations. A script or service that calls the APIs with a store-level token: sync products from a supplier, push orders to an ERP, export customers. No UI is needed. You will build one in Project: Product Sync Tool.
  2. Apps. A web application that merchants install into their store. It uses OAuth to get a token, can show its own screen inside the control panel, and listens to webhooks. See App Types and the OAuth Flow.
  3. Stencil themes. The default storefront is rendered on BigCommerce's servers from Handlebars templates, SCSS and JavaScript that you control. You edit a theme on your computer and upload it. See Stencil CLI and the Cornerstone Theme.
  4. Headless storefronts. Your own front end (often Next.js) reads products through the GraphQL Storefront API and sends the shopper to BigCommerce for checkout. See Headless Storefronts.
flowchart TD
    P["BigCommerce platform<br/>(hosted, managed)"]
    P --> A["REST and GraphQL APIs"]
    P --> W["Webhooks"]
    P --> T["Stencil theme engine"]
    P --> H["Hosted checkout"]
    A --> I["Integrations and apps"]
    W --> I
    A --> HL["Headless storefront"]
    T --> S["Theme-based storefront"]
    H --> S
    H --> HL

The platform stays managed; your code attaches through APIs, webhooks, themes and the hosted checkout.

What the platform does for you

Because BigCommerce is hosted, a long list of concerns is already handled. The catalog and order databases, the cart, the checkout pages, PCI-related payment handling, tax and shipping calculation hooks, SSL certificates, backups and scaling all sit on the platform's side. If you want to refresh your memory of how these parts fit in any shop, the Domain Model lesson of the E-commerce Fundamentals track draws them.

In return there are limits. You cannot add a database table to the store, run a cron job on the platform, or rewrite how the checkout totals are computed. When you need your own data or background work, you host it yourself (an "app backend") and talk to the store through the APIs. Knowing where this boundary lies saves a lot of time: always ask "does BigCommerce expose a hook for this?" before you design a solution.

This course is written for developers. For merchants' needs such as choosing a plan or setting up payment methods in the control panel, the official help center is the right place. We only mention settings when they affect your code.

Editions and environments

BigCommerce sells several plan tiers (at the time of writing named Standard, Plus, Pro and Enterprise). Tiers differ in limits, features and support, and the details change often, so check the current plan comparison rather than trusting a course. Two practical points matter for developers:

  • Most APIs, Stencil themes and the app system are available on every plan. Some features, such as multiple storefronts or higher API limits, depend on the plan.
  • You should never develop on a live merchant store. Use a sandbox (trial or developer) store. Setting one up is the topic of Setting Up a Development Environment.

How this course works

Almost everything in BigCommerce development talks to the real platform: a real store, a real token, a real HTTP endpoint. That cannot run inside a web page. So each lesson uses a consistent pattern:

  • Real code is read-only. Requests, theme files, configuration and CLI commands appear in plain code blocks. They are accurate, but you run them in your own sandbox store.
  • Runnable stand-ins. Next to each real snippet, a <TryIt> editor runs a small, honest model of the idea in plain JavaScript or Node.js. For example, the pagination lesson runs a mock catalog service with the same response shape as the real one. We say clearly what is real and what is the stand-in.
  • Shared ideas link out. Concepts that are not BigCommerce-specific, such as webhook signatures, idempotency or price rules, live in the E-commerce Fundamentals track and are linked rather than repeated.

You should be comfortable with modern JavaScript (async and await, fetch, modules) and basic HTTP. If not, start with the JavaScript tutorial and the Node.js tutorial.

A first stand-in: the store model

Here is the first stand-in. It does not call BigCommerce. It sketches the split we just discussed: which parts of a store belong to the platform and which you can extend, and which tool you would pick for a given job. Run it and change the jobs list to see how the choice changes.

JS Which extension point fits the job?

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The output is only a table, but it is the question you will ask at the start of every project: where does my code run, and how does it prove who it is? The answers differ per extension point, and the next lessons fill them in.

A real call, read-only

For a first look at the real thing, this is what a request to list products looks like. It needs a store hash and a token that you create in API Accounts, Tokens and Scopes, so it is shown as text and not run here:

Terminal
curl -s "https://api.bigcommerce.com/stores/$BC_STORE_HASH/v3/catalog/products?limit=2" \
  -H "X-Auth-Token: $BC_ACCESS_TOKEN" \
  -H "Accept: application/json"

The store hash is the short identifier in the store's URL. The token goes in a header and never in the URL. The response is JSON with a data array and a meta object for pagination, which we model in the next lesson's stand-in and in The Catalog API (V3).

The second stand-in makes that response shape tangible. It builds a response in the same layout from a small list, so you can see what code that reads the real API will receive. The values are invented.

JS The shape of a V3 list response

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does "SaaS" mean for a BigCommerce developer?

    The platform is managed. Your code attaches to published extension points instead of changing core code.
  2. 2. Which project type needs OAuth so that many merchants can install it?

    Apps get a token per installing store through the OAuth flow. A script for your own store can use a store-level API account instead.
  3. 3. Where should you develop and test a new integration?

    A sandbox store lets you create and delete data freely without touching real customers or orders.
  4. 4. Why does this course use stand-ins?

    The real code is shown read-only and works in your sandbox; the runnable examples are small models that show the behavior.

Summary

  • BigCommerce is hosted SaaS: you extend it through APIs, webhooks, themes, widgets and the hosted checkout, not by editing core code.
  • The main kinds of work are integrations, apps, Stencil themes and headless storefronts.
  • Use a sandbox store for development, and check current plan limits instead of memorizing them.
  • Real platform code in this course is read-only; each lesson adds runnable stand-ins and says what is real.
  • General e-commerce ideas link to the E-commerce Fundamentals track.

Next: Platform Architecture