# Your Next Store: an AI-native Next.js storefront template on Stripe > Your Next Store is an MIT-licensed Next.js 16 commerce template that pairs a typesafe Commerce Kit SDK with an AGENTS.md context file so Claude Code, Cursor and Codex can edit the storefront. It is a starting point for developers, not a hosted platform. **yournextstore/yournextstore** — AI-Native Open-Source Next.js commerce. Powered by Stripe. Ultra fast with typesafe Commerce SDK. Built for AI development (Claude, Codex, Cursor). - Repository: https://github.com/yournextstore/yournextstore - Website: https://demo.yournextstore.com - Stars: 5,519 · Forks: 671 - Language: MDX - License: MIT - Published: 2026-09-22 · Updated: 2026-09-22 · Language: en - Canonical page: https://hysenlabs.com/projects/yournextstore-yournextstore ## What Your Next Store actually is, and who it is for Your Next Store is a storefront template, not a store. The README calls it an "Open-source AI-native Next.js e-commerce template" and the repository is a Next.js 16 application with App Router routes, React Server Components and React Compiler enabled. Products, variants, carts and checkout are not stored in this repository. They live behind the YNS platform, which the template reaches with a Commerce Kit SDK and a single API key. The intended reader is a developer who already knows Next.js and wants a commerce front end they can reshape quickly. The pitch is narrower than "e-commerce for everyone": the README devotes a whole table to why AI coding tools work better in this codebase, pointing at idiomatic App Router patterns, typed SDK methods such as productBrowse() and cartUpsert(), and the AGENTS.md file that ships with the repo. If you are not using an AI coding agent, that table is mostly irrelevant to you, though the typed SDK still saves you from writing your own API client. It is a poor fit for anyone who wants to run a store without touching code. There is no admin UI described in the README beyond the hosted YNS admin panel at yns.store, and no plugin or extension model. The unit of customisation here is a Git branch. ## How the Commerce Kit SDK and YNS API key drive the storefront The data flow is one-directional and thin. The Next.js app renders React Server Components; those components call methods on the commerce-kit package, which is pinned at version 0.61.0 in package.json. Every call is authenticated with YNS_API_KEY, read from .env.local or .env. The template never talks to a database directly, and the repository contains no migrations, schema files or ORM configuration that would suggest one. That shape explains the SDK's design. Methods like productBrowse() and cartUpsert() have defined input and output shapes, so the type checker catches a wrong argument before runtime. The README argues this matters for AI agents specifically: an LLM writes correct code when the contracts are visible to it, and the domain models already exist, so the agent does not have to invent them. The same shape is the main architectural constraint. Anything the YNS API does not expose, the storefront cannot do on its own. You are building a client, and the server belongs to someone else. The README points at the API documentation at yns.store/manage/settings/api for "fetching products, managing carts, and building on top of YNS", which is where the real surface area lives. Two scripts in scripts/ wrap that API from the terminal. scripts/api.sh is described as a thin wrapper around curl that handles auth, base-URL resolution and pretty JSON output for every /api/v1/* endpoint. scripts/publish.sh triggers a production publish, the same action as the admin Publish button, and deploys the tenant repository's remote main, so uncommitted or unpushed work is not included. ## Installing Your Next Store with Bun and getting a first page rendered The README gives a four-step quick start. Node.js 24+ and Bun 1.0+ are listed as prerequisites, and you need a YNS API key from the admin panel before the storefront will return real data. Clone the repository, move into it and install dependencies with Bun. The README uses bun install rather than npm or pnpm, and package.json scripts call bun for dev, build, start and test. ```bash git clone https://github.com/yournextstore/yournextstore.git cd yournextstore && bun install ``` Copy the example environment file and fill in the key. .env.example contains two entries: YNS_API_KEY, which the README says you obtain from https://yns.store/manage/settings/api, and NEXT_PUBLIC_YNS_API_TENANT, described in the file as an optional API base URL. ```bash cp .env.example .env.local ``` Start the dev server. The dev script is bun next dev, so the README's bun dev is shorthand for the same thing. It serves on port 3000, and the README says opening localhost:3000 shows your store running. ```bash bun dev ``` Once it is up, the CLI wrappers are the fastest way to confirm the key works. This calls a Store API endpoint and prints pretty JSON, so a 401 or an empty list tells you the credential or the tenant base URL is wrong before you debug any component. ```bash bun run api GET /products?limit=5 ``` Before shipping anything, the repository defines a check script that chains the Biome linter, a TypeScript compile with no emit, and the test runner. The build script runs next build and then a shell check script. Both are the closest thing to a validation gate the project documents. ## Themes as Git branches, and the sync problem they create The README states that Your Next Store ships with 149 ready-made themes, each on a branch named theme-001 through theme-149. Switching is a checkout, and the README claims themes modify only visual components and static assets, leaving products, cart and checkout untouched. ```bash git checkout theme-016 ``` Each theme branch is described as a single commit on top of main whose message describes the theme's vibe. You can list them without opening a browser, which is the practical way to browse 149 options. ```bash git for-each-ref --sort=refname --format='%(refname:short) %(subject)' 'refs/remotes/origin/theme-*' ``` This is a clever use of Git, and it has a cost the README is honest about. Stores are seeded from a snapshot of the repository and share no commit history with it, so a plain merge has no common base. The README directs readers to docs/sync.md for a graft-and-merge procedure and explains why merge is preferred over rebase in that situation. If you fork the template and then want upstream fixes, that document is not optional reading. A theme branch also means your visual customisation lives on a branch name you did not choose; keeping your own edits mergeable with 149 sibling branches is a discipline the project does not automate. ## Where Your Next Store is the wrong choice The first limitation is the hosted dependency. YNS_API_KEY is not optional in the quick start, and the README's environment variable section lists it as the only required variable. If the YNS platform is unavailable, or if the API does not expose a capability you need, the storefront cannot compensate. There is no documented fallback to a local product source. The second is the demo. The README links to demo.yournextstore.com as a live demo, but nothing in the repository or README states what data that demo runs against, so treat it as a rendering reference rather than a behaviour specification. The third is documentation depth. The README does not document rollback for the publish script, does not describe rate limits or error semantics for /api/v1/* endpoints, and does not explain what happens to an in-flight cart when a publish completes. The publish script is described as deploying remote main, which means an unpushed commit is silently absent from a publish you thought included it. Finally, the AI-native framing is a codebase property, not a runtime one. The README lists AGENTS.md, CLAUDE.md and a .agents/ directory, and the dependency list includes the ai and @ai-sdk/react packages, but the README does not describe a customer-facing AI feature. If you arrived expecting a shopping assistant, the repository does not describe one. ## Your Next Store against the Next.js Commerce starter The obvious comparison is Vercel's Next.js Commerce starter, which is also a Next.js storefront template. The difference is where the commerce state lives. Next.js Commerce is built around pluggable provider packages, so you can point the same front end at different backends and keep the catalogue logic in your own repository. Your Next Store takes the opposite position: one hosted platform, one SDK, one key. That is less flexible and considerably less code to maintain. A second difference is the AI tooling. Your Next Store commits AGENTS.md, CLAUDE.md and a .claude/ directory, and the README argues that typed SDK contracts are what let an agent write correct code. A generic starter gives an agent an unfamiliar provider abstraction and no project-specific context file. Whether that translates into fewer bad edits depends on your agent and your prompts; the repository makes the claim, and the mechanism is at least inspectable. A third is theming. Branch-per-theme is unusual. Most starters ship one design and leave visual work to you. 149 branches is a large ready-made surface, and it is also 149 branches to keep in mind when you diff upstream changes. ## Licence, maintenance and what an upgrade costs The repository is MIT licensed, with LICENSE.md at the top level. MIT permits commercial use, modification and redistribution provided the copyright notice and permission notice are retained. That covers the template code. It does not cover the YNS platform, which is a separate hosted service reached through YNS_API_KEY and governed by its own terms. Nothing in the repository describes pricing for that service, so the total cost of running a store on this template is not something the repository answers. The last push to the repository was on 2026-09-17 and it is not archived, so the codebase is being touched. The single listed release is v1.0.0 from 2026-01-26. The dependency set is aggressive: Next.js 16.3.4, React 19.2.8, Tailwind CSS v4 and commerce-kit 0.61.0, several of them pinned exactly rather than with ranges. Upgrading means moving those pins together, and the check script is your only documented regression gate. For forks, the upgrade path runs through the graft-and-merge procedure in docs/sync.md rather than a normal merge, because seeded stores share no commits with the template. Budget time for that on every upstream pull, not just the first. ## Conclusion Adopt Your Next Store if you write TypeScript and want a Next.js App Router storefront that an AI agent can edit without inventing data models, and you accept that the catalogue, carts and checkout run through the hosted YNS platform behind YNS_API_KEY. Do not adopt it if you need a self-contained stack with your own database, or if you want a visual page builder rather than theme branches. Before committing, verify three things: that the YNS API key can be issued for the tenant you intend to use, that the sync procedure in docs/sync.md is workable for your fork, and that the theme branch you pick touches only visual components as the README claims. ## FAQ ### What is Your Next Store and who is it for? It is an open-source, MIT-licensed Next.js 16 e-commerce template powered by Stripe and the YNS platform. The README targets developers who want a typed, AI-friendly storefront codebase they can customise, not merchants looking for a no-code store builder. ### How do I install Your Next Store? The README's quick start clones the repository, runs bun install, copies .env.example to .env.local with a YNS_API_KEY, and runs bun dev, which serves the store on localhost:3000. Node.js 24+ and Bun 1.0+ are listed as prerequisites. ### Do I need a YNS API key to run Your Next Store? Yes. The README lists YNS_API_KEY as the required environment variable and points to the admin panel at https://yns.store/manage/settings/api to obtain it. .env.example also includes NEXT_PUBLIC_YNS_API_TENANT, described there as an optional API base URL. ### How do I change the theme in Your Next Store? Themes live on branches named theme-001 through theme-149, and switching is a git checkout of the branch, for example git checkout theme-016. The README states that theme branches change only visual components and static assets, leaving products, cart and checkout unchanged. ### Can I publish my store from the command line? Yes. The README documents bun run publish:store, which triggers a production publish and waits for the build, with a --no-wait flag to fire and forget. scripts/publish.sh deploys the tenant repository's remote main, so commits must be pushed first. ## Sources - [License: MIT](https://github.com/yournextstore/yournextstore/blob/main/LICENSE) - [Project website](https://demo.yournextstore.com) - [README](https://github.com/yournextstore/yournextstore/blob/main/README.md) - [Releases](https://github.com/yournextstore/yournextstore/releases) - [yournextstore/yournextstore on GitHub](https://github.com/yournextstore/yournextstore) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/yournextstore-yournextstore