Shopify OS 2.0: What Store Owners Need to Know Before Upgrading

Shopify launched Online Store 2.0 in June 2021. Since then, every new theme on the Shopify Theme Store has been built on the new architecture. But a significant portion of active Shopify stores — particularly those that launched before 2022 — are still running on legacy themes.

If your store is one of them, you're not just missing out on new features. You're carrying technical debt that limits what you can do with your store, slows down your development work, and increasingly limits which apps can support you.

What Actually Changed in OS 2.0

The difference between legacy Shopify themes and OS 2.0 themes is architectural — it's not just a visual update. Here are the key changes that matter for store owners:

JSON Templates vs. Liquid Templates

Legacy themes use a single .liquid file per page type. Everything on the page — the layout, the sections, the content — is defined in that file. To change the page structure, a developer has to edit the code directly.

OS 2.0 themes use JSON templates that define which sections appear on each page and in what order. Store owners can add, remove, and reorder sections in the Shopify theme editor without touching code. Product page, collection page, blog posts, landing pages — all become drag-and-drop configurable.

App Blocks vs. App Embeds

This is the change that has the biggest impact on day-to-day operations. In legacy themes, when you install an app that adds content to your product pages — a review widget, a size guide, an upsell block — the app has to inject code directly into your theme files. This creates a fragile dependency: update your theme, and the app's injected code might break.

OS 2.0 introduced app blocks— a standardized way for apps to add content to theme sections through the theme editor, without modifying theme files. Apps become theme editor citizens: you drag them into position, configure them visually, and they're decoupled from your theme code.

Section Groups and Global Sections

Legacy themes could only add customizable sections to the homepage. OS 2.0 introduced section groups, which allow sections to be added and customized across all page types — including header and footer areas.

This means store owners can add announcement bars, promotional banners, trust badges, and navigation elements to any page type through the theme editor, rather than asking a developer to hardcode them.

Why Not Upgrading Is Getting More Expensive

The Shopify ecosystem is moving fast. Here are three specific ways legacy theme users are paying a hidden cost:

App Compatibility

The most powerful Shopify apps — particularly in the review, loyalty, and subscription categories — are building their newest features exclusively for OS 2.0 app blocks. Legacy theme users either get a degraded version of the feature or are told their theme isn't supported. This will get worse over time, not better.

Shopify Checkout Extensibility

Shopify's Checkout Extensibility framework — which allows UI customizations within the checkout flow — is only fully supported on OS 2.0 themes. Legacy stores using the older checkout.liquidcustomization approach will have that feature removed from non-Shopify Plus plans by August 2024, per Shopify's announcement.

Developer Hours

Every time a developer needs to make a change to a legacy theme, they're working in an architecture that most experienced Shopify developers haven't touched since 2021. Expect slower work, more caution, and higher rates for legacy theme work.

The Migration Process

Migrating from a legacy theme to OS 2.0 is not a theme swap — it's a rebuild. Here's what the process actually looks like:

Phase 1: Audit (1–2 days)

Document every customization in your current theme: custom sections, hardcoded content, injected app code, custom JavaScript, and modified Shopify files. This becomes the scope of work for the rebuild.

Phase 2: Theme selection or custom build (1–4 weeks)

If your needs are standard, a quality OS 2.0 theme from the Theme Store — priced $140–$400 — can serve as a starting point. If your store has significant custom functionality, a custom-built OS 2.0 theme will be more efficient long-term.

Phase 3: Content and settings migration (2–5 days)

Product data, customer data, and order history migrate automatically. What doesn't migrate automatically: theme settings, customizer configurations, hardcoded homepage content, and custom metafield setups. These need to be manually rebuilt in the new theme.

Phase 4: App reconfiguration (1–2 days)

Reinstall apps using their OS 2.0 app blocks, configure them in the theme editor, and verify they're working correctly across page types. This is typically where you find apps that have been superseded by better OS 2.0-native alternatives.

Phase 5: QA and launch (1–2 days)

Test across devices and browsers, verify checkout functionality, check all third-party integrations, and confirm Core Web Vitals scores meet your targets. Then do a clean theme swap — Shopify lets you switch themes without affecting your store's data or URLs.

Is It Worth It?

Almost always yes — the question is when. If your store is doing less than $10k/month and running stable with no immediate app or customization needs, you can delay. If you're actively trying to grow, running into app compatibility issues, or spending developer hours on theme maintenance, the migration ROI is typically positive within 2–3 months.

The longer you wait, the more technical debt accumulates, and the more disruptive the eventual migration becomes. There's no version of this where waiting is free.