For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Dev Portal
DocsAPI ReferenceLearnCommunityChangelog
DocsAPI ReferenceLearnCommunityChangelog
    • Overview
  • Learning Plans
    • Developer Foundations
    • Composable Developer
    • Stencil Developer
    • B2B Developer
  • Courses
        • Course Overview and Prerequisites
        • Composable Commerce and Headless Storefronts
      • Conclusion
    • Learning Changelog
Dev Portal
LogoLogo
On this page
  • Composable Commerce
  • Headless
  • The Full Picture
  • Resources
CoursesComposable CoreOverview

Composable Commerce and Headless Storefronts

Was this page helpful?
Previous

Course Overview and Prerequisites

Next

The GraphQL Storefront API

Built with

Plan: Composable Developer

Lesson 2 of 27 · 15 min

Two key terms important for the concepts we’ll be exploring in this course are composable and headless. These describe different but related concepts.

Composable Commerce

“Composable” refers to the splitting of systems into specialized components that are orchestrated into a connected ecosystem.

In a well-built composable architecture, each isolated feature component of an application can be sourced from the provider, product, or service that best fits the requirements for that feature. For an ecommerce storefront, typical examples include choosing the best commerce platform, the best content management system (CMS) for rich content, the best search provider, and the best product reviews platform.

The more tightly coupled your web front-end is to a particular platform or architecture for one of these functional components, the more difficult it will be to make independent decisions about the others and make tech stack changes in the future.

Headless

At the simplest level, “headless” refers to interacting with a system bypassing a built-in “head” or front-end. As an API-first SaaS platform, BigCommerce is well suited for headless interactions.

A “headless front-end,” while a bit of a paradoxical term, refers to a front-end that is completely decoupled from and independent from the back-end platform that supports it. Building a headless BigCommerce storefront means complete freedom to build a front-end with your preferred frameworks, tools, and architecture, with core commerce functionality provided via predictable and reliable BigCommerce APIs.

The Full Picture

As you can see, a headless front-end is a piece — perhaps the most important piece — of composability. A front-end that is completely decoupled from any back-end platform is the critical first step to being able to compose together services and functional components from various providers.

In practical terms, the core workflows we’ll examine in this course are centered on building headless storefronts, leveraging the power of BigCommerce, thus enabling you to realize your own composable commerce application.

Resources

  • Introduction to Headless Commerce