To evaluate a Next.js ecommerce starter, check four things before the design: which backend its data layer reads from, whether checkout is handed off or rebuilt, whether the hard parts of a real catalog (variable products, filtering, stock) actually work, and whether anyone still maintains the repository. Starters are abundant, mostly free and convincing in a demo. They are also the most common source of half-finished storefront projects, because the demo stays quiet about exactly those four.
What follows is an evaluation method, not a ranked list, written from maintaining storefronts after the starter's honeymoon ended. It ends with a test you can run in one afternoon against your own products.
The question that eliminates most options: which backend?
Every starter assumes a commerce backend, and that assumption is baked into its data layer. Vercel's Next.js Commerce reads Shopify's Storefront API. Medusa's starter reads Medusa; Saleor's, Saleor. Forks and community repositories target WooCommerce, BigCommerce and most other backends, and each one is only as current as the person who maintains it. A starter written against a different backend than yours is not a starting point. It is a rewrite of the layer that matters, wearing a nice homepage.
So the first filter is simple: does it read from the backend you actually run? If you are on WooCommerce, a Shopify-first starter gives you a design reference and nothing structural. That is worth something, but it is not worth calling a foundation. The Next.js Commerce vs WooCommerce comparison goes through what does and does not transfer.
- Which backend does the data layer assume, and is that adapter maintained?
- Does it use the REST API or GraphQL, and does that match your setup?
- How is cart state handled: locally, on the backend, or in a third service?
- Is checkout included, handed off to the backend, or left as an exercise?
Twelve products, one currency, no tax rules
That is the typical demo catalog. It has no shipping zones, no coupons, no logged-in customers, no subscription products, no out-of-stock variants and no plugin doing something unusual to the cart. One variable product with three attributes of five options each already has 125 possible combinations, and the demo has none. Your store has some or all of those, and each one is where a starter's clean abstraction meets reality. If variable products, real filtering and stock freshness work, you have a foundation. If they are "coming soon", you have a homepage.
An afternoon test with your own catalog
Reading a README tells you what the authors intended. Running the starter against your data tells you what it does. On WooCommerce, the simplest version is a staging copy of the live store. If that is too heavy, export a slice with the built-in CSV exporter (Products → Export) into a fresh install, and make sure your most complicated variable product is in it. Point the starter at the staging store and work through the list below. Each check takes minutes, and a starter that fails three of them is a rewrite you would be paying for in installments.
- Open the product with the most variations and pick a combination you do not sell
- Load a category holding more than 100 products and page past the first page
- Add to cart, reload, then open the same cart in a second browser tab
- Apply a percentage coupon and a free-shipping coupon to the same cart
- Mark one variant out of stock in the admin and time how long the storefront takes to show it
- View the page source of a product page and check the price is in the HTML
- Run Lighthouse on that product page with your real images, not the demo's
The 100-product category matters because WooCommerce's APIs return at most 100 items per request, and a starter tested only on its demo has often never asked for page two. The out-of-stock timing tells you whether the starter has any cache invalidation at all, or simply rebuilds on a schedule.
Checkout is the part to read carefully
Most starters either hand off to the backend's hosted checkout or implement a minimal custom one. The handoff is safe and preserves every payment, tax and shipping rule you already configured. A custom checkout looks better in a demo and means you now own correctness in the flow where money moves, including failed payments, refunds, tax edge cases and whatever your gateway does on a decline. Budget three to six weeks for the build and a permanent maintenance obligation on top, against a handoff that costs you one redirect.
For a store that already has tax, shipping and payment rules configured, take the handoff, and build custom only when the hosted flow cannot express something you need. The real mistake is adopting a starter without noticing which of the two it chose for you.
Signals that a starter will still be here next year
Look at the repository, not the landing page. Compare the Next.js major version in its package.json with the current release; a starter two majors behind will make you do its upgrade before you can do your own work. A starter abandoned eighteen months ago pins you to a version you will eventually need to leave, and migrating a fork off an unmaintained base is worse than starting fresh.
- Commit activity and answered issues, not the number of stars
- A changelog and a documented upgrade path between major versions
- Dependencies that are current, which npm outdated shows in seconds
- A license, such as MIT, that permits commercial use without ambiguity
The parts you will build regardless
No starter ships your SEO migration, your redirect map, your analytics events, your consent handling or your product data quirks, and those tasks are identical whether you started from a starter or an empty repository. A redirect map is roughly a day per thousand URLs once the exports are clean, and analytics parity is rarely under a week if the old setup was never documented. The full inventory of what a production store needs beyond a free Next.js template is written up separately.
When to skip starters entirely
If your requirements are ordinary (a catalog, categories, product pages, cart, native checkout), a purpose-built storefront against your existing backend is often faster than adapting someone else's abstractions, because you spend the time writing your own logic instead of reading theirs. Starters pay off when they match your backend closely and you need a reference implementation of something non-obvious. They cost you when the fit is approximate and you spend three weeks bending a data layer that was never shaped for your store. The test is cheap: if the starter's backend adapter does not name WooCommerce on its own README, assume it will not fit and price the adaptation before you clone it.
A starter is a set of decisions someone else made. Adopt the ones you agree with, and check what you inherited before you build a business on it.
A disclosure: we build WooCommerce storefronts
We build WooCommerce storefronts for a living, so treat this as an interested opinion. We do not sell starter code, which is why the advice above is about evaluating and not about choosing: the starter question matters far less than whether the backend fit is real and whether someone will maintain the result. Store owners who would rather not run this evaluation at all can look at the done-for-you Next.js WooCommerce template. If you want the same reasoning applied to your specific store, the free audit covers it, including the answer where a tuned theme is the better call.
