Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Headless Shopify starter built on Next.js 🤘
Headless CMS powered by

FeaturesToursSet UpSpin UpDeploymentExtras

✨ Features

  • Utility-first CSS with Tailwind CSS
  • Animations powered by Framer Motion
  • Cart powered by Shopify Buy SDK
  • Real-time inventory check for products using SWR
  • Customizable Filtering & Sorting for product collections
  • Klaviyo waitlist form for out-of-stock products
  • Klaviyo newsletter form with opt-in field
  • Dynamic Page Routes for custom page creation
  • Automatic Sitemap.xml generation
  • Automatic robots.txt generation
  • Automatic 301 Redirects from Sanity
  • Live Preview content directly from Sanity
  • Modern Image component using Sanity's Hotspot, Crop, and automatic WEBP format
  • Modular page content for all pages, including dynamic grid layouts
  • Customizable Promotion Banner
  • Customizable Cookie Notice
  • Accessibility features:
    • ARIA Landmark Roles
    • Default focus states preserved for keyboard navigation
    • Correctly trap focus for drawers with focus-trap-react
    • Roving tabindex for radio buttons
    • Input-based quantity counters
    • Required alt text for all images
    • "Skip to Content" link
  • SEO features:
    • Page-level SEO/Share settings with previews
    • Fallback Global SEO/Share settings
    • Automatic JSON-LD Schema markup for products

Shopify Integration Features

  • Automatically syncs products from Shopify into Sanity
  • Custom action to sync product cart thumbnails back to Shopify from Sanity
  • Tracks product status (draft/published) from Shopify to help control visibility while editing
  • Deleted products and variants are preserved and flagged in Sanity
  • Updates the URL on variant changes while keeping a clean history stack
  • Vanity shop URL masking
  • Global Cart with access to all variant data for line items
  • Supports Single Variant products out of the box
  • Product photo galleries with variant granularity
  • Dynamic /shop collection page
  • Custom collection pages
  • Ability to surface a variant option on product cards

🎧 Tours

Still not sold? Here's some videos to get you psyched:

Famous 5-Minute Setup™ - Coming Soon
From sync to sale, watch me spin up a fresh storefront in under 5 minutes!

Explore the file Structure - Coming Soon
In-depth look at the file structure, naming conventions, and logic under the hood

Setting up your first Product - Coming Soon
Explore the Product settings within Sanity and how to properly setup PDP pages and PLP cards

Connecting to Klaviyo and testing your Forms - Coming Soon
Learn how to quickly connect Klaviyo to utilize product waitlist and newsletter forms

Setup your first Vercel deployment - Coming Soon
Using the Sanity Vercel Deploy plugin, see how easy it is to empower your clients to trigger deploys

🔥 Automatic Set Up

Quickly deploy as a Sanity Starter on Vercel with a pre-populated store! Once deployed, simply follow step 2 and 3 below to connect your Shopify store.

You should delete the demo products once you connect your own Shopify account. Demo products will not function properly as they are not part of your Shopify store. Additionally, any existing products in your Shopify store will not automatically sync into Sanity. To trigger a sync, you must make a change to your existing product(s) in Shopify first.

💀 Manual Set Up

Clone this repository from your GitHub account with the Use this template button

1) Sanity

  1. Initialize and build the Sanity Studio
    • Make sure you have the Sanity CLI installed globally first
    • yarn && sanity init in the /studio folder
    • During Sanity's initalization it will warn you that the Sanity Studio is already configured. Type Y and hit enter to reconfigure it to your own project
    • When it asks you what dataset configuration to use, go with the default
  2. Add CORS Origins to Sanity project
    • Visit and go to [your-project] > API > "CORS origins"
    • Add your Studio URLs with credentials: http://localhost:3333 and [subdomain]
    • Add your front-end URLs without credentials: http://localhost:3000 and https://[subdomain]

2) Shopify Storefront Access

  1. Allow custom app development in Shopify
    • Go to "Settings" (bottom left) > "Apps and sales channels" > "Develop apps" (top right)
    • click "Allow custom app development"
  2. Create a custom app in Shopify
    • Go to "Settings" (bottom left) > "Apps and sales channels" > "Develop apps" (top right)
    • click "Create an app"
    • Give this a relevant App name, I prefer: "Headless Storefront", so it's clear what it's being used for
    • Use your dev account as the App developer to know when there are issues
  3. Configure Admin API scopes
    • Configuration > Admin API integration > "Configure"
    • Check the following boxes for the "Products" scope: write_products and read_products
  4. Configure Storefront API scopes
    • Configuration > Storefront API integration > "Configure"
    • Check the following boxes for the "Products" scope: unauthenticated_read_product_listings and unauthenticated_read_product_inventory
    • Check the following boxes for the "Checkout" scope: unauthenticated_write_checkouts and unauthenticated_read_checkouts
  5. Install the App

3) Shopify Webhooks

  1. Go to "Settings" (bottom left) -> "Notifications" -> "Webhooks" (very bottom)
  2. add the following webhooks with the (Latest) stable API version:
    • Product creation - [live-domain]/api/shopify/product-update
    • Product update - [live-domain]/api/shopify/product-update
    • Product deletion - [live-domain]/api/shopify/product-delete

      You have to use a real, live domain name (not localhost!). Be sure to use your Vercel project URL during development, and then switch to the production domain once live. You may not know your Vercel project URL until you deploy, feel free to enter something temporary, but make sure to update this once deployed!

4) NextJS

  1. yarn in the project root folder on local
  2. Create an .env.local file in the project folder, and add the following variables:


// Needed for Klaviyo forms:

// Needed for Mailchimp forms:

// Needed for SendGrid forms:
  1. Update all the XXXXXX values, here's where to find each:
  • NEXT_PUBLIC_SANITY_PROJECT_ID - You can grab this after you've initalized Sanity, either from the studio/sanity.json file, or from your Sanity Manage dashboard
  • SANITY_API_TOKEN - Generate an API token for your Sanity project. Access your project from the Sanity Manage dashboard, and navigate to: "Settings" -> "API" -> "Add New Token" button. Make sure you give read + write access!
  • SANITY_STUDIO_PREVIEW_SECRET - A unique string of your choice. This is used to confirm the authenticity of "preview mode" requests from the Sanity Studio
  • NEXT_PUBLIC_SHOPIFY_STORE_ID - This is your Shopify store ID, it's the subdomain behind
  • NEXT_PUBLIC_SHOPIFY_STOREFRONT_API_TOKEN - Copy the Storefront API access token from "Apps" -> "Develop apps" -> [your_custom_app] -> "API credentials".
  • SHOPIFY_ADMIN_API_TOKEN - Copy the Admin API access token from "Apps" -> "Develop apps" -> [your_custom_app] -> "API credentials". (Note: you’ll only be able to reveal your Admin API token once.)
  • SHOPIFY_WEBHOOK_INTEGRITY - Copy the Integrity hash from "Settings" -> "Notifications" -> "Webhooks" (very bottom of page)
  • KLAVIYO_API_KEY - Create a Private API Key from your Klaviyo Account "Settings" -> "API Keys"
  • MAILCHIMP_API_KEY - Create an API key from "Account -> "Extras" -> API Keys
  • MAILCHIMP_SERVER - This is the server your account is from. It's in the URL when logged in and at the end of your API Key
  • SENDGRID_API_KEY - Create an API key from "Settings" -> "API Keys" with "Restricted Access" to only "Mail Send"
  1. Create an .env.production and .env.development file in the /studio folder, and add the following (using the same value as above):

5) Shopify Store Theme

Since we're serving our store through a headless environment, we don't want visitors accessing our unused shopify theme. The domain for this is visible during checkout, and is publicly accessible. To silence it, replace your current theme's theme.liquid file with the one from this repo, and replace YOUR_STOREFRONT_DOMAIN_NO_PROTOCOL with your actual frontsite domain URL (do not include protocol or trailing slash)

This will essentially "pass-through" URLs accessed at your Shopify Store to your true headless storefront (ie. ->

⚡ Spin Up

Next (Front End)

yarn dev in the project folder to start the front end locally

Sanity (Back End)

yarn dev in the /studio folder to start the studio locally

  • Your Sanity Studio should be running on http://localhost:3333

    If you did not manually set up your project, the projectId in /studio/sanity.json will still be set to the HULL demo project. Make sure to update this before starting the studio, otherwise you will be denied access when trying to access your studio.

🚀 Deployment


This is setup to work seamlessly with Vercel, which I highly recommend as your hosting provider of choice. Simply follow the on-screen instructions to setup your new project, and be sure to add the same .env.local variables to your Vercel Project


This is an easy one, you can simply run sanity deploy from the /studio folder in your project. Select a subdomain you want; your Studio is now accessible from the web. This is where I'll invite the client to manage the project so they can both add billing info and begin editing content.

Client Updates

Once you hand off to the client you'll want to give them the ability to generate builds when they make updates within the Sanity Studio. The easiest way to do this is through my Vercel Deploy plugin.

🤘 Extras/Tips

This looks like a theme... How can I use this like a starter?

While this starter is relatively opinionated, the goal was three-fold:

  1. Use high-quality packages that don't get in the way
  2. Solve common UX problems and complex logic so you can focus on the fun stuff
  3. Create a more approachable starter for anyone looking to build production-ready headless Shopify experiences

That being said, I understand this means a lot of what's included is very opinionated. However, you'll find that at it's core the structure and naming conventions lend itself to really making it your own.

I've purposefully used extracted component classes, not only for cleaner file structure, but also so you can easily work in your own styles exclusively within the styles folder. Feel free to extend or outright remove the applied styles for all of the components!

What's up with the CSS? Why are you using @apply?

Previously, @apply was used to extract component classes away from your javascript files. However, since then Tailwind has been opposed to this approach. In the coming releases HULL will move away from this approach in favor of applying styles directly to the components so functionality and styling is done in one place.

You can read more about Tailwind's stance on @apply here:

Can I use this for non-Shopify projects?

Absolutely! This starter was actually born out of a non-shopify starter I had been using for my own client projects.

I made a marketing-starter branch that is HULL without all the Shopify logic! The fastest way to get started is simply cloning that branch locally into an empty project folder:

git clone -b marketing-starter --single-branch .

You can read the setup instructions for this version from the branch's README.

Error: Failed to communicate with the Sanity API

If you get this error in your CLI, you need to logout and log back in again. Simply do sanity logout and then sanity login to fix.

Access your "product_sync" metafields in Shopify without using a plugin

Simply navigate directly to: https://[store_id]

(making sure to replace [store_id] with your Shopify Store ID)

How do I properly hand-off a Vercel project to the client?

While not as easy as Netlify, what I prefer to do is:

  1. Have the client create their own Vercel account
  2. At the time of writing, Github connections can only be connected to one Vercel account at a time, so have the client create a Github account if they don't already have one, and transfer the project repo to them
  3. Delete the dev project from your own Vercel account (this is so the client can utilize the project name and domain you were using during dev)
  4. You or the client can now connect their newly transferred Github repo to their own Vercel account!
How can I see the bundle size of my website?

Simply run yarn analyze from the project folder. This will run a build of your site and automatically open the Webpack Bundle Analyzer visuals for your site's build files.

💯 Shoutouts

Huge ups to the following talented and rad folks who helped in countless ways. Thank you for all the support, code contributions, and discussions.



🤝 License

MIT  ·  Github @ndimatteo  ·  Instagram @ndimatteo