The Best SvelteKit Ecommerce Starters: Shopify, Medusa & More

Building an ecommerce frontend with SvelteKit makes sense. The framework is fast, the DX is excellent, and server-side rendering with streaming gives you the page speed that search engines and impatient shoppers demand. But “ecommerce” means wildly different things depending on your scale, and picking the wrong starter architecture will cost you months.

Here is what actually exists in the SvelteKit ecommerce space right now, broken into three approaches: headless commerce platforms, direct payment integration, and full-platform storefronts.

The Three Approaches

Before I get into individual starters, you need to understand the architectural split:

Headless commerce (Medusa, Commercetools, Crystallize) gives you a backend that handles products, inventory, orders, and fulfillment. Your SvelteKit app is just the storefront. This is the right choice if you are selling physical products at scale — dozens or hundreds of SKUs, fulfillment logic, discount engines, multi-currency.

Direct Stripe gives you payment processing and nothing else. No product catalog, no inventory, no order management. You build all of that yourself or skip it entirely. This works for digital products, subscriptions, or simple one-product businesses.

Full-platform storefronts (Shopify, WooCommerce) mean someone else handles the entire backend. Your SvelteKit app talks to their API. You get a proven commerce engine but lose control over the data layer and pay platform fees.

Pick based on what you are actually selling, not what sounds coolest.

Headless Commerce Starters

SvelteShop (Medusa.js) — Free

SvelteShop is the headless option in our directory. It pairs SvelteKit with Medusa.js and Stripe for payments.

What you get: Product listing pages, product detail pages, cart management, checkout flow, Stripe payment integration, and all the backend commerce logic Medusa provides — inventory tracking, fulfillment workflows, discount codes, multi-currency support, tax calculations.

What is good: Medusa is open-source and self-hosted, so you own your data and pay nothing in platform fees. The SvelteKit frontend is server-rendered for SEO. The architecture is clean — API calls to Medusa, rendering in SvelteKit, payments via Stripe. If you outgrow the starter, you are not locked into anything proprietary.

What is not: You are running two services (SvelteKit app + Medusa backend), which means two things to deploy and maintain. Medusa’s admin panel is functional but not beautiful. The learning curve is real — you need to understand Medusa’s plugin system to customize anything beyond the basics.

Best for: Teams building a real store with 20+ products, physical goods, and actual inventory needs.

Crystallize + SvelteKit Boilerplate — Free

Crystallize offers a SvelteKit boilerplate that connects to their GraphQL-first PIM (Product Information Management) system. It uses Houdini for GraphQL and Tailwind for styling.

What you get: A storefront connected to Crystallize’s headless CMS that specializes in rich product content — think subscription boxes, digital products with complex pricing, or anything where the product story matters as much as the SKU.

What is good: Crystallize excels at structured product content. If your products need rich media, storytelling, or complex variant configurations, their content modeling is superior to Medusa’s. The SvelteKit boilerplate deploys cleanly to Vercel or Netlify.

What is not: Crystallize is a paid service. The free tier is limited. You are coupling your frontend to their proprietary API. The boilerplate is less actively maintained than Medusa-based options — check the commit history before committing.

Best for: Content-heavy stores where product storytelling drives conversion. Subscription businesses with complex pricing models.

svelte-commerce (Litekart/Medusa) — Free

The itswadesh/svelte-commerce project on GitHub is an open-source storefront that works with multiple backends — Litekart, Medusa, and has WIP support for Shopify, WooCommerce, and BigCommerce.

What you get: A PWA-enabled storefront with adaptor-based architecture, meaning you can swap the backend without rewriting the frontend.

What is good: The multi-backend approach is clever. If you are not sure which commerce engine you will end up with, this gives you flexibility. PWA support means mobile performance is prioritized.

What is not: “WIP” means work in progress. The Shopify and WooCommerce adaptors are not production-ready. The project has many forks and spin-offs, which makes it hard to tell which version is canonical. Documentation is thin.

Best for: Developers who want backend flexibility and are willing to contribute to an open-source project that is still maturing.

Direct Stripe Starters

PayKit — $49

PayKit takes the opposite approach from headless commerce. There is no product catalog. There is no inventory system. It is Better Auth for identity and Stripe Checkout for payments. That is the entire scope.

What you get: User authentication, Stripe Checkout sessions, webhook handling for payment events, and a clean codebase that does not pretend to be more than it is.

What is good: If you are selling a single digital product, a course, a subscription to your SaaS, or access to content — this is all you need. The simplicity is the feature. Better Auth handles the identity layer without the weight of a full commerce backend. At $49 you are paying for clean Stripe integration that actually handles edge cases (failed payments, subscription changes, webhook retry logic).

What is not: The moment you need a product catalog, variant pricing, inventory, or fulfillment — you have outgrown this. There is no admin panel for managing products. If you add more than three or four products, you will wish you had started with a headless solution.

Best for: Solo founders selling digital products, SaaS subscriptions, or gated content. One to three products maximum.

Full-Platform Storefronts

SvelteKit Commerce (Vercel/Shopify) — Free

Vercel’s official SvelteKit Commerce template connects to Shopify’s Storefront API. It is the SvelteKit equivalent of their hugely popular Next.js Commerce starter.

What you get: Product listings, search, cart, and checkout — all powered by Shopify’s backend. You manage products in Shopify’s admin. SvelteKit renders the storefront.

What is good: Shopify handles everything you do not want to think about — inventory, payments, shipping, taxes, fraud detection, order management. The Storefront API is mature and well-documented. Vercel’s template is well-built and deploys instantly to their platform. If you already have a Shopify store and want a custom frontend, this is the path of least resistance.

What is not: You are paying Shopify’s monthly fees plus transaction fees. You are limited to what Shopify’s Storefront API exposes — which is a lot, but not everything. Customizing checkout requires Shopify Plus ($2,000+/month). The template is tightly coupled to Vercel’s deployment model, though it runs anywhere SvelteKit runs.

Best for: Existing Shopify merchants who want a custom frontend with SvelteKit performance. Teams that want to offload all commerce operations to a proven platform.

Comparison Matrix

Starter	Backend	Products	Inventory	Self-hosted	Monthly cost
SvelteShop	Medusa.js	Unlimited	Yes	Yes	Hosting only
Crystallize	Crystallize	Unlimited	Via PIM	No	Free tier + paid
svelte-commerce	Multi	Unlimited	Backend-dependent	Yes	Hosting only
PayKit	None	Manual	No	Yes	Stripe fees only
SvelteKit Commerce	Shopify	Unlimited	Yes	No	$39+/month

Which One Should You Pick?

You are selling physical products at scale — SvelteShop with Medusa. You need inventory, fulfillment, and discount logic. Medusa gives you all of that without platform fees.

You are selling 1-3 digital products — PayKit. Do not overcomplicate it. Stripe Checkout handles the hard parts.

You already use Shopify — SvelteKit Commerce by Vercel. Keep your existing product management, get a faster frontend.

You need rich product content and storytelling — Crystallize boilerplate. Their PIM is built for this.

You are not sure yet — Start with PayKit and validate demand before investing in a full commerce stack. You can always migrate up. You cannot easily migrate down.

A Word on Performance

Every option here, when deployed correctly, will give you sub-second page loads. SvelteKit’s server-side rendering combined with streaming means your ecommerce pages load fast regardless of which backend you choose. The performance differences between these starters are negligible compared to the architectural decisions around your commerce backend.

The real performance question is: how fast can you ship? Pick the architecture that matches your actual needs today, not the one you might need in eighteen months.