Online Store 2.0: what it changed and why it still matters

It is technically old news and it is still the dividing line between stores that can do things easily and stores that cannot. Worth ten minutes if you have never had it explained without jargon.

What changed

Sections everywhere

Before, only the home page was built from sections you could rearrange. Product pages, collection pages and everything else had a fixed layout you could only change by editing code.

After, every page is built from sections. You can rearrange a product page the way you always could a home page.

App blocks

Apps can offer blocks you place through the theme editor instead of editing your theme files. This is the change with the most day-to-day consequence: apps became things you arrange rather than things you install into your theme and hope to be able to remove.

Metafields in the editor

Custom fields on products, collections and pages became usable from the theme editor rather than requiring a developer to wire up.

Why it still matters in practice

Nearly every app built in the last few years assumes it. On an older theme you will hit a specific, frustrating pattern: the app installs, the dashboard works, and there is no way to put anything on your storefront without a developer.

It is also the difference between changing your product page layout in ten minutes and it being a project.

How to tell what you have

Go to Online Store → Themes → Customize and use the page selector at the top to open a product page. If you can see a list of sections and blocks down the left with an “Add block” option, you are on 2.0. If the product page shows a handful of fixed settings and nothing to rearrange, you are not.

If you are not on one

Updating a theme is more work than it sounds, mainly because of accumulated customisations rather than the theme itself. But the honest position is that the platform has moved, the tooling assumes it, and the gap widens every year.

The usual approach: install a 2.0 theme alongside the current one, rebuild the important pages, check the templates that get traffic, and publish once it is right. Nothing is live until you publish, so the risk is mostly time.

One practical note: a widget or block you configured on the old theme will not appear on the new one automatically. Blocks belong to a theme, so a theme change means placing them again — a few minutes’ work, but a surprise if you were not expecting it.