Next.js Commerce

The all-in-one starter kit for high-performance e-commerce sites. With a few clicks, Next.js developers can clone, deploy and fully own their own store. Start right now at nextjs.org/commerce

Demo live at: demo.vercel.store

This project is currently under development.

Goals and Features

Performant by default
SEO Ready
Internationalization
Responsive
UI Components
Theming
Standarized Data Hooks
Integrations - Integrate seamlessly with the most common ecommerce platforms.
Dark Mode Support

Work in progress

We're using Github Projects to keep track of issues in progress and todo's. Here is our Board

Integrations

Next.js Commerce integrates out-of-the-box with BigCommerce. We plan to support all major ecommerce backends.

Troubleshoot

I already own a BigCommerce store. What should I do?

First thing you do is: set your environment variables

.env.local

BIGCOMMERCE_STOREFRONT_API_URL=<>
BIGCOMMERCE_STOREFRONT_API_TOKEN=<>
BIGCOMMERCE_STORE_API_URL=<>
BIGCOMMERCE_STORE_API_TOKEN=<>
BIGCOMMERCE_STORE_API_CLIENT_ID=<>

If your project was started with a "Deploy with Vercel" button, you can use Vercel's CLI to retrieve these credentials.

Install Vercel CLI: npm i -g vercel
Link local instance with Vercel and Github accounts (creates .vercel file): vercel link
Download your environment variables: vercel env pull .env.local

Next, you're free to customize the starter. More updates coming soon. Stay tuned.

BigCommerce shows a Coming Soon page and requests a Preview Code

After Email confirmation, Checkout should be manually enabled through BigCommerce platform. Look for "Review & test your store" section through BigCommerce's dashboard.

BigCommerce team has been notified and they plan to add more detailed about this subject.

Contribute

Our commitment to Open Source can be found here.

Fork this repository to your own GitHub account and then clone it to your local device.
Create a new branch git checkout -b MY_BRANCH_NAME
Install yarn: npm install -g yarn
Install the dependencies: yarn
Duplicate .env.template and rename it to .env.local.
Add proper store values to .env.local.
Run yarn dev to build and watch for code changes
The development branch is development (this is the branch pull requests should be made against). On a release, the relevant parts of the changes in the staging branch are rebased into master.

kikoanis / commerce