Management APIs
Building Apps
Quick Start
Building Channels
Quick Start
Building Headless Storefronts
Embedded Checkout
Next.js Commerce
Managing Currencies
Partner Information
Becoming A Partner
Getting Started
Staying Current with Platform Changes
POS Solutions
ERP Solutions
PIM Solutions
OMS Solutions
Marketing Solutions
Shipping Solutions
Payment Solutions

Next.js Commerce Quick Start


BigCommerce offers cloud-based multi-channel ecommerce solutions. We also offer themes with powerful design tools and features that let you build and host your storefront on our servers.

Headless BigCommerce

BigCommerce’s flexibility allows for headless architecture, the ability to integrate storefront frontends with the BigCommerce backend. Some of the headless setups have the advantage of providing the following:

  • Customize your frontend technologies without migrating your database
  • Preserve your legacy frontend while switching to BigCommerce as your ecommerce engine
  • Power multiple stores on multiple sales channels from a single BigCommerce dashboard.

Next.js Commerce

Next.js Commerce is a headless integration to BigCommerce. Created in partnership with the Next.js and Vercel teams, Next.js Commerce showcases how powerful Next.js is when partnered with our open SaaS ecommerce platform.

View the demo application to get an idea of the robust set of features that Next.js Commerce offers.

Getting started

To get started with Next.js Commerce, you’ll need to deploy a live version directly from Vercel. Then, you can develop locally by cloning the new Git repository created during deployment. The following steps will walk you through the process.


Deploying Next.js Commerce directly from Vercel

  1. Visit and click Clone and Deploy.

    Clone and Deploy

  2. When prompted, create a Vercel account by logging in using one of the supported Git providers. The Git provider you choose is where Vercel will clone the Next.js Commerce repository.

    Note: If you have an existing Vercel account, you can sign in using those credentials.

    Create Vercel account

  3. After signing in, a Create Git Repository dialogue will appear with a dropdown to select your Git Scope, and a Repository Name text field. You may change the name of the project from the default or leave it as-is. Click Create to proceed.

    Create Git repository

  4. (Optional) Create a team. You can also click Skip to continue without creating a Vercel Team.

    Create Vercel team

  5. In the Add Integrations dialogue box, click Add to connect your BigCommerce store to your Vercel project.

    Add BigCommerce integration

  6. In the Add BigCommerce to Your Vercel Project dialogue, select Sign Up or Log In.

    1. If you are an existing developer on BigCommerce, select Log In and use your BigCommerce credentials to integrate BigCommerce and Vercel. Follow the on-screen instructions to install the Vercel app to your BigCommerce store.

      Existing BigCommerce store log in button

      Log in to existing BigCommerce store dialogue

    2. If you are new to BigCommerce, select Sign Up to create a BigCommerce developer sandbox store and populate it with sample data. Vercel will connect Next.js Commerce to this sandbox store automatically. If you would later like to upgrade your sandbox store to a live store, contact BigCommerce by calling 1-888-248-9325.

      Sign up for BigCommerce store button

      Sign up for BigCommerce store registration form

  7. Upon completion of deployment to Vercel, you will see your site deployed in a thumbnail image.

Commerce deployment confirmation dialogue

Developing locally after Vercel deployment

  1. Visit the Git provider where Vercel created a new repository. Clone that repository locally.
  2. Navigate to the locally cloned project’s root directory and create a copy of the .env.template file. Rename the newly created file .env.local and insert the your environmental variables using the following as a reference:
  • STORE_HASH: You can retrieve it from your BigCommerce store control panel URL in the format of https://store-${STORE_HASH}

    STORE-HASH location in URL

  • STORE_TOKEN|STORE_CLIENT: For instructions on generating Store API credentials, visit Obtaining Store API Credentials.

  • STOREFRONT_API_TOKEN: For instructions on generating the Storefront API token, visit Create a Token.

  • CHANNEL_ID: Use the channel ID of the channel created by Vercel during deployment. For information on how to retrieve channel information, visit Get All Channels.

  1. Open a terminal in your repository’s root directory. To install the project’s dependencies, run npm install.

  2. When dependencies have finished installing, run npm run dev in your terminal. Next.js will load the environmental variables from .env.local, start a local server, and compile your project.

  3. To see your Next.js Commerce storefront running locally, open localhost:3000 in your browser.


Any saved changes you push to your Git repository will trigger a redeployment at Vercel. You can also trigger a redeployment manually through the Vercel dashboard.


The architecture for Next.js Commerce is standard for a Next.js application. To learn Next.js basics, visit the official Next.js tutorial.

To understand how Commerce generates pages and updates product information on your storefront, we will further explore a couple of concepts.

Pre-rendering pages

One of the main advantages of Next.js is the fast page load times you can achieve by pre-rendering your content. By default, Next.js pre-renders all pages.

Next.js allows you to choose how pages are pre-rendered:

  • Static Generation: Next.js generates the HTML at build time and reuses on each request.
  • Server-side Rendering: Next.js generates the HTML on each request.

Next.js Commerce statically generates pages while still keeping store information updated by using Incremental Static Regeneration.

Static Page Generation

Next.js pre-renders static content by calling the getStaticProps() function at build time on the server-side. Since getStaticProps() does not run on the client-side, you can do direct database queries or run other functions without exposing them to the client. To verify what Next.js eliminates from the client-side bundle, use Vercel’s Code Elimination tool.

Incremental Static Regeneration

With getStaticProps(), you may still use dynamic content on your statically generated pages. Incremental Static Regeneration (ISR) updates existing pages by re-rendering them in the background when triggered by site traffic after a set timeout period. By default, data revalidation runs at most once every four hours, though you may customize this frequency.

For more information and a demonstration on how ISR works, visit Vercel’s Static Reactions Demo.

By default, Next.js Commerce revalidates and updates product information from BigCommerce at most once every four hours.

Fetching and populating store data

Next.js Commerce uses Storefront-data-hooks to connect your Next.js frontend with the BigCommerce backend. The package contains code-split React hooks for data fetching using SWR (stale-while-revalidate). SWR is a layer on top of React Hooks that automates cache management. Data can be transitively stale, but SWR will always re-fetch and synchronize the correct data from BigCommerce.

Storefront Data Hooks has helper functions to handle common user actions such as login, logout, and register.

SWR uses FETCH for data fetching: vercel/fetch: Opinionated fetch (with retrying and DNS caching) optimized for use inside microservices.

Application settings

Next SEO

Next.js Commerce includes the Next SEO plugin to simplify SEO settings so that Next.js Commerce appears correctly in search results and is more readily shareable on social media. To learn how to configure Next SEO settings, visit the Next SEO GitHub repository.

Component styling

Next.js Commerce uses Tailwind to style components. Next.js Commerce’s root directory contains a tailwind.config.js file where you can customize much of the project’s styling. For more information on how to configure the tailwind.config.js file, visit Tailwind CSS - Configuration.

Internationalized routing

Next.js supports internationalized (i18n) routing and Next.js Commerce uses sub-path routing which puts the locale in the URL path. By default, the next.config.js file has US English (en-US) and Spanish (es) set as locales with en-US set as the default.

i18n: {
locales: ['en-US', 'es'],
defaultLocale: 'en-US',

For more information on i18n routing in Next.js, see the Next.js documentation on internationalized routing.