Every Shopify project starts with the same question: do you buy a theme, build something custom on top of Shopify’s framework, or go headless. Most of the advice online skips straight to “it depends,” which is true but not useful. Here’s what each option actually means in practice, and what should drive the decision.
Pick based on how much your store needs to look and behave differently from a standard storefront, not based on which option sounds most advanced.
Primo Collab
Theme-based (off the shelf or lightly customized)
You start with a Shopify theme, either free or paid from the Shopify Theme Store, and adjust colors, fonts, sections, and layout through the theme editor plus some light code changes.
What it’s good for:
- Fast to launch. A theme-based store can go live in days, not months
- Lower upfront cost, since you’re not paying for custom development of every section and layout
- Shopify handles updates to core functionality (checkout, cart, payments) automatically
Where it breaks down:
- Every theme has structural limits. If your product catalog, filtering needs, or checkout flow don’t fit the theme’s assumptions, you’ll be fighting the theme instead of using it
- Heavy customization on top of a theme gets messy over time. Each change stacks on top of the theme’s existing code, and eventually it becomes harder to maintain than starting custom would have been
- Visual differentiation is limited. A lot of theme-based stores end up looking similar to each other, since everyone’s customizing the same starting points
Theme-based makes sense for straightforward product catalogs, standard buying flows, and stores that want to launch fast and iterate later.
Custom Shopify (built on Shopify’s framework, not a pre-built theme)
You build the storefront from scratch using Shopify’s Liquid templating language and its section/block architecture, following Shopify’s standard structure but with no theme starting point.
What it’s good for:
- Full control over layout, structure, and how sections behave, without fighting someone else’s theme decisions
- Still runs on Shopify’s hosted infrastructure, so checkout, payments, and core commerce logic stay stable and Shopify-managed
- Scales better than a heavily modified theme, since the code is built around your actual requirements from day one instead of retrofitted
Where it breaks down:
- Costs more upfront than theme-based, since every section and template is built rather than adjusted
- Takes longer to launch. Custom builds typically run weeks, not days
- You’re still working within Shopify’s Liquid framework, so certain frontend behaviors (page load patterns, some interaction models) are constrained by how Shopify serves pages
Custom Shopify makes sense for stores with a distinct visual identity, non-standard product configurations, or specific UX requirements a theme can’t accommodate, while still wanting Shopify to manage the commerce backend.
Headless Shopify
The storefront (what customers see and interact with) is built separately, often in a framework like Next.js or Remix, and talks to Shopify only through its APIs for product data, cart, and checkout. Shopify becomes the backend, not the thing rendering your pages.
What it’s good for:
- Complete freedom over frontend architecture, performance tuning, and how content and commerce mix on the same page
- Can be meaningfully faster than a standard Shopify storefront, since you control exactly what loads and when, not just what a theme allows
- Makes sense if the storefront needs to do things Shopify’s templating simply can’t, like heavy custom interactivity or tight integration with non-Shopify systems
Where it breaks down:
- Meaningfully more expensive and slower to build than either theme-based or custom Shopify, since you’re building and maintaining an entire separate application
- Ongoing maintenance is higher. Two systems (the headless frontend and Shopify’s backend) both need upkeep, and they need to stay in sync
- Overkill for most small and mid-sized stores. Headless solves problems that only show up at a certain scale or complexity, and building it before you need it adds cost without adding value
Headless makes sense when a store has outgrown what Shopify’s templating can do, has specific performance requirements a standard storefront can’t hit, or needs deep integration with systems outside Shopify’s ecosystem.
Comparison at a glance
| Theme-based | Custom Shopify | Headless | |
|---|---|---|---|
| Launch speed | Fastest | Moderate | Slowest |
| Upfront cost | Lowest | Moderate | Highest |
| Visual/UX flexibility | Limited | High | Highest |
| Ongoing maintenance | Low | Moderate | High |
| Best for | Standard catalogs, fast launch | Distinct identity, non-standard needs | Large scale, deep custom requirements |
How to actually decide
Ask what’s actually driving the desire for something more than a theme. If the answer is “it should look a little different from competitors,” a custom build on Shopify’s framework almost always solves that without headless’s added cost and complexity. If the answer involves specific performance numbers, deep non-Shopify integrations, or interaction patterns Shopify’s templating genuinely can’t support, headless earns its cost.
Most stores that ask about headless don’t actually need it. It’s worth ruling out custom Shopify first, since it solves the majority of “the theme feels limiting” problems at a fraction of the cost and timeline.