Skip to content

docs: add comments to .env.example explaining how to get Shopify env …#1519

Open
jitheng wants to merge 1 commit into
vercel:mainfrom
jitheng:fix/env-example-shopify-docs
Open

docs: add comments to .env.example explaining how to get Shopify env …#1519
jitheng wants to merge 1 commit into
vercel:mainfrom
jitheng:fix/env-example-shopify-docs

Conversation

@jitheng

@jitheng jitheng commented Mar 12, 2026

Copy link
Copy Markdown

Summary

Fixes #1517

Users were confused about where to obtain the required Shopify environment variables (SHOPIFY_STOREFRONT_ACCESS_TOKEN, SHOPIFY_REVALIDATION_SECRET, SHOPIFY_STORE_DOMAIN) when setting up Next.js Commerce.

Changes

Added inline comments to .env.example with step-by-step instructions explaining:

  • SHOPIFY_STOREFRONT_ACCESS_TOKEN: How to navigate to Shopify Admin → Apps → Develop apps, create/configure an app with Storefront API scopes, and copy the access token from API credentials.
    • SHOPIFY_REVALIDATION_SECRET: That this is a self-chosen secret string (not from Shopify's app credentials), and how to generate one and configure Shopify webhooks to use it.
    • SHOPIFY_STORE_DOMAIN: How to find the store's .myshopify.com subdomain.

Motivation

The original .env.example had empty values with no guidance, causing confusion for new contributors (ref: issue #1517). The SHOPIFY_REVALIDATION_SECRET in particular is easy to confuse with Shopify's app "client secret" — this PR clarifies that it is a user-generated value used to authenticate webhook requests.

…vars

Fixes vercel#1517 - Users were confused about where to obtain the Shopify environment variables. Added inline comments to .env.example explaining step-by-step how to get SHOPIFY_STOREFRONT_ACCESS_TOKEN (from Shopify app API credentials), SHOPIFY_REVALIDATION_SECRET (a self-chosen secret for webhook auth), and SHOPIFY_STORE_DOMAIN.
@vercel

vercel Bot commented Mar 12, 2026

Copy link
Copy Markdown
Contributor

@jitheng is attempting to deploy a commit to the Vercel Solutions Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant