Why Use This

Most storefronts run on a full-stack commerce platform. The platform owns the theme, the rendering pipeline, the cart UI, and most of the surface customers see. It works until what you want to render exceeds what the theme supports, or the features you want to ship live on someone else's roadmap. Headless commerce moves the storefront onto your own stack. Your framework, your infrastructure, your render path. The commerce platform keeps doing commerce. Inventory, checkout, payments, tax.

Going headless means more of the stack is yours. Routing, caching, image optimization, and the rest of what a platform used to handle quietly. Templates and starters have tried to close that distance for a decade, and they keep failing in two ways: undernurtured (the README hasn't been touched since the framework had a different name), or so opinionated that customizing them costs you most of what you saved.

Meanwhile, the way teams write code has changed. Agentic development tools like Claude Code and Cursor keep getting meaningfully better at scaffolding across files, holding a framework's context, and producing software instead of suggestions. A starter aimed at agents isn't the same kind of artifact as a starter aimed at humans. It can be more opinionated and more flexible at the same time, because the opinions are documented in skills the agent reads, not enforced by abstractions you have to live with.

That's why we built Vercel Shop. It's a Shopify storefront in Next.js, deployed on Vercel, with a set of skills that teach your agent how the codebase is shaped, how the Storefront API behaves, and how to keep changes deployable. Drop in your Shopify credentials and go. Swap in your CMS. Swap in your search. Wire up whatever you're convinced matters. The parts we kept stable are the boring ones on purpose.