Online Store 2.0: sections, blocks and metafields in practice
Online Store 2.0 turned the theme from a set of fixed templates into a composable system: sections on every page, blocks inside them, and structured metafields to hold your own data.
The features are widely known. What is less common is building as though they exist, rather than bolting them onto an older approach.
The three pieces and what each is for#
| Piece | What it gives you | Who edits it |
|---|---|---|
| Sections | Reorderable modules on any template | Merchants, in the theme editor |
| Blocks | Repeatable items inside a section | Merchants |
| Metafields | Structured, typed data on products and other objects | You define, merchants fill |
| Metaobjects | Your own content types, reusable across pages | You define, merchants fill |
How this changes theme design#
The old instinct is to hard-code a product page and give merchants a handful of settings. The 2.0 instinct is to ship a small set of well-made sections and let the merchant compose pages. Fewer bespoke templates, more reusable parts — and far fewer developer requests for layout changes six months later.
Every layout tweak a merchant can make themselves is a support ticket you never receive.
Metafields deserve a data model#
- Define types deliberately: a size chart is a metaobject, not a rich-text blob.
- Name them for what they mean, not where they appear on the page.
- Decide which are merchandising data and which are content — they have different owners.
- Fill them at import time, not manually, if your catalogue is more than small.
- Document them; an undocumented metafield is discovered a year later by someone who deletes it.
A good starting structure#
One product template with sections for gallery, buy box, description, specifications, and cross-sells. Specifications read from metafields. Cross-sells configurable per collection. That structure covers most catalogues without a single bespoke template.
Frequently asked questions
Do I need to migrate an older theme to 2.0?
Not urgently, but new builds should assume it. The editing experience and the maintenance cost are both meaningfully better.
Metafields or a separate content system?
Metafields for anything attached to a product or collection. A separate system when the content has its own life and audience.
How many sections is too many?
When merchants cannot tell two apart. Fewer, better-named sections beat a long list of near-duplicates.
online store 2.0shopify sectionsshopify metafieldsshopify metaobjectsshopify theme architecture
