The urge to redesign almost always starts the same way: "I don't like how it looks anymore." That's a real feeling, but it's not a diagnosis. Before committing budget and weeks of work to a rebuild, the question worth answering first isn't aesthetic, it's architectural: can your current theme actually do what you need, or can't it?
Refresh, Redesign and Rebuild Aren't the Same Decision
A refresh keeps the existing theme and changes what's on top of it: images, copy, colors, spacing, the things covered in a conversion diagnostic rather than a platform decision. A rebuild replaces the theme's underlying architecture itself, the actual system the store is built on. Redesign sits in between: real changes to structure and experience that don't necessarily require a new architecture underneath. Conflating these three is how stores end up paying for a full rebuild to solve a problem a refresh would have fixed for a fraction of the cost, or the reverse, polishing a theme that's structurally incapable of supporting what the business has become.
The Actual Test: What Architecture Is Your Theme Running?
Shopify's own documentation draws a clean line here, and it's the most useful diagnostic available. Vintage (legacy) theme architecture only supports sections on the homepage, everything else is fixed layout, hardcoded by whoever built it. Online Store 2.0 architecture supports sections on every page, uses JSON templates instead of Liquid-only templates, connects directly to metafields in the visual editor instead of requiring custom code per template, and lets you install or swap app functionality through app blocks without touching code. Shopify has since added a further layer, theme blocks, for even more granular customization on top of OS 2.0.
If you can't tell which one you're running: try adding a new section to a page that isn't your homepage, your About page, a collection page, anywhere. If the option isn't there, you're very likely on vintage architecture, and that's a real, structural reason a redesign might actually need to be a rebuild.
When a Refresh Is Actually the Right Call
If the store is already running Online Store 2.0 (or the newer theme-blocks architecture) and functioning normally, most of what feels like "the whole site needs a redesign" is usually something narrower: outdated imagery, copy that doesn't sell the product, an add-to-cart rate below benchmark, checkout friction, the exact layers covered in a conversion diagnostic. None of that requires new architecture. A refresh addresses it directly, at a fraction of the disruption and cost of a full rebuild, and without the real risk every rebuild carries: losing SEO equity and functioning integrations in the process if it isn't handled carefully.
When a Rebuild Is Actually the Right Call
The legitimate signals are structural, not aesthetic:
- The theme is confirmed vintage architecture, sections only work on the homepage.
- A developer has told you a specific feature "isn't possible" on the current theme more than once.
- The business model has genuinely changed, single product to multi-category, B2C to a wholesale tier, and the current structure was never built for it.
- Every content change requires a developer because nothing is editable through sections or metafields.
If none of these are true, "I don't love how it looks" is a refresh, not a rebuild, and treating it as the bigger, more expensive project doesn't make the outcome better, just slower and pricier to reach.
What This Isn't: Whether to Leave Shopify Entirely
Everything above assumes the store is staying on Shopify. Whether Shopify itself is still the right platform, versus a custom build, is a separate and bigger question that depends on transaction fees, how app-dependent the store has become, and how much custom backend logic the business actually needs. Worth answering on its own, not folded into a theme decision.
Not sure which one your store actually needs?
Get Your Visibility Audit →Frequently Asked Questions
What's the difference between a Shopify refresh, redesign and rebuild?
A refresh keeps the existing theme and architecture and changes surface-level things: images, copy, colors, layout tweaks within what the theme already supports. A rebuild replaces the underlying theme architecture itself, moving to a modern theme when the current one structurally can't support what the store needs. Redesign sits between the two: real changes to structure and user experience, without necessarily changing the underlying theme architecture.
How do I know if my Shopify theme is legacy or Online Store 2.0?
Check whether you can add and rearrange sections on pages other than the homepage, product and collection pages, the About page, anywhere. Vintage (legacy) themes only support sections on the homepage. Online Store 2.0 themes support sections everywhere, use JSON templates, connect to metafields directly in the editor, and support app blocks that install without custom code, all confirmed in Shopify's own theme documentation.
Can I fix conversion problems without rebuilding my Shopify theme?
In most cases, yes. If the store is already on Online Store 2.0 (or the newer theme-blocks architecture) and the actual problems are traffic quality, product-page content, or checkout friction, none of that requires a new theme. Run the diagnostic first; a rebuild doesn't fix a problem the architecture wasn't causing.
Is it worth rebuilding a Shopify store that's already on Online Store 2.0?
Rarely, at least not for architecture reasons. If a store is already OS 2.0 and functioning, the case for a full rebuild has to come from somewhere else, a business model change the current theme genuinely can't support, not from wanting a visual update, which a refresh handles at far lower cost and disruption.
Should I leave Shopify instead of rebuilding?
That's a different, bigger question than refresh vs. rebuild, and one worth answering separately rather than folding into a theme decision. Whether Shopify itself is still the right platform depends on factors a theme rebuild doesn't touch: transaction fees, app dependency, and how much custom backend logic the business actually needs.
Related reading: Shopify vs. Custom Website Development