One size chart for the whole store works until your catalogue mixes fits. Once you sell slim tees and boxy hoodies, jeans and dresses, or adults' and kids' sizes, a single chart starts giving shoppers the wrong numbers. Then the question becomes: how do you show the right chart on each product, and keep it right as new products arrive?
This guide compares five ways to do it on Shopify, from no-code to fully automatic, with the trade-offs of each.
What "the right chart" really means
Before choosing a method, group your products by fit family, not by collection. A fit family is a set of products that share the same measurements: "Regular-fit tees", "Slim jeans", "Women's dresses", "Kids' tops". Most stores end up with somewhere between three and fifteen.
Marketing collections like "New arrivals" or "Best sellers" mix fit families, so they're a poor key for size charts. Product type, a tag, or the vendor usually maps to fit much better.
Write down, for each fit family:
- which products belong to it,
- how you could identify them automatically (product type, tag, vendor, or a "real" collection like "Jackets"),
- which chart it needs.
That list decides which method below fits you.
Method 1: Alternate product templates (2–4 fit families)
- In the theme editor, open a product page and choose Create template, for example "product-jeans".
- Add a Pop-up or collapsible row block linking to a page with the jeans chart.
- Repeat for each fit family.
- On each product, under Theme template, choose the right template. You can also set it for many products at once in the bulk editor.
Good for: a few fit families and a stable catalogue. Watch out for: every template is a copy of your product page. Change the layout and you change it in every template. New products default to the main template unless someone remembers to switch them.
Method 2: A product metafield that points to a page
This is Shopify's own documented method.
- Settings → Metafields and metaobjects → Products → Add definition. Name it "Size chart", type Page.
- Create one page per chart.
- In the theme editor, connect the Pop-up block's page setting to the metafield with the dynamic source icon.
- On each product, pick the chart page in the Metafields section, or in the bulk editor.
Good for: one product template with many charts. Watch out for:
- Manual assignment. Every product needs the field set, and new arrivals show nothing until someone does it.
- Empty links. In some themes the link still appears when the metafield is empty.
Method 3: Metaobjects for structured charts
Metaobjects let you store a chart as structured data (title, table, notes) instead of a page, and reference it from a product metafield.
- Settings → Metafields and metaobjects → Metaobjects → Add definition, for example "Size chart" with fields for a title, the table (rich text, or multi-line text holding an HTML table) and notes.
- Add one entry per fit family.
- Add a product metafield of type Metaobject that references the "Size chart" definition.
- Show it with a block's dynamic source, or with a little Liquid in the theme.
Good for: many charts that you edit centrally. Watch out for: the same manual assignment as Method 2. You'll also often need some Liquid to render the table the way you want.
Method 4: Pick the chart by product type or tag in Liquid
If your product types or tags are consistent, you can skip per-product assignment altogether. Name each chart entry so its handle matches a product type, then let the theme look it up:
{%- assign chart = product.metafields.custom.size_chart.value -%}
{%- if chart == blank -%}
{%- assign type_handle = product.type | handleize -%}
{%- assign chart = metaobjects.size_chart[type_handle] -%}
{%- endif -%}
A product of type "Jeans" picks up the entry with the handle jeans. A per-product metafield still wins, so you can override the odd product. The same idea works with tags (product.tags contains 'chart-jeans') or with pages (pages[handle]).
Good for: large catalogues with tidy product types, and teams comfortable editing theme code. Watch out for: it's custom code in your theme. It has to be carried over when you update or switch themes, and nothing in the admin tells a colleague why a product shows the chart it does.
Method 5: An app with assignment rules
Size chart apps store charts as data and decide which chart each product gets with rules you set in the app, such as "Collection is Jackets", "Tag contains denim" or "Vendor is X". Because the rule is evaluated on every product, new arrivals are covered the moment they match. There's no template switch and no metafield to fill in.
When comparing apps, check:
- Which fields rules can use: collection, tag, product type, vendor, metafield.
- Priority: what happens when a product matches two rules. You want a clear "first rule wins" order.
- A way to test a product and see which chart it gets, and why.
- The fallback when nothing matches. Showing nothing is usually better than a wrong chart.
- Whether rules run without slowing the page, that is, rendered with the page rather than fetched afterwards.
How Seamwise does it
Seamwise Size Chart & Guide is our app, so here's how it implements the points above:
- Rule fields: rules target products, collections, tags, product types or vendors, in priority order. On the Pro plan, rules can also require all conditions (AND) and match on a metafield or the shopper's country.
- Test a product: shows which chart a product will get and which rule chose it. A rule preview counts the matching products before you publish.
- No match, no button: if nothing matches, nothing renders, so a product never shows an empty link or the wrong chart.
- Rendered with the page: the rules are compiled into your theme when you publish, so the right chart is in the page HTML. There's no request to our server on each page view.
- Several tables per chart: a jacket chart can hold Short, Regular and Long as tabs. That often means one chart per fit family instead of three.
- Free plan: 5 published charts with no app branding, which covers many stores' fit families. More on the Seamwise page.
Which method should you choose?
| Your situation | Best fit |
|---|---|
| 1 fit family | One page and a Pop-up block |
| 2–4 fit families, few new products | Alternate templates (Method 1) |
| Many charts, small catalogue, no code | Metafield to a page (Method 2) |
| Large catalogue, tidy product types, developer on hand | Liquid lookup by type (Method 4) |
| Frequent new arrivals, mixed fits, no code | App with rules (Method 5) |
Keep the charts right over time
Whatever you choose, three habits stop charts drifting:
- Edit charts in one place. Don't paste a copy of the chart into a product description "just this once". It won't get updated.
- Spot-check new arrivals. Open two or three new products each time you import, and check the chart matches the garment.
- Watch your size exchanges by product. If several customers swap the same item for a size up, the chart or the fit note for that product needs fixing, not the whole store's chart.
The right chart on every product, shown next to the size picker, is one of the cheapest fixes for "which size should I get?" messages. Pick the method that matches how your catalogue actually changes.