Shopify multiple size charts per product: skip one mega HTML table. Separate Size chart tables that stack — or shortcodes — on the same PDP.
2026-10-07
Floris-jan de Vries

Shopify multiple size charts on one product: men, women, kids

A unisex hoodie with one HTML table “Men | Women | Kids” in the description. On a phone the third column disappears. Shoppers read the kids row off the men’s grid. Shopify multiple size charts per product is the other path: three Size chart tables on *the same* product page — not one overflowing table, and not three SKUs just because the grid will not split.

We already covered multiple size charts across a *catalogue*: men’s hoodie gets the men’s grid, women’s the women’s. This article is the PDP that needs all three. The OO - Advanced Table Builder listing names size charts; docs talk about several charts as separate blocks. CTA stays that listing (handle `tables-specs-comparisons`).

One product, three grids, no extra option

Shopify variants are S/M/L — not a centimetre table. Adding variants: max three options, 2048 variants. “Fit” as a fourth option does not fit. Line item properties do not build a size chart. Native metafields pasted into the description are still one HTML blob.

Place tables with theme blocks lists five blocks. Size chart is visibility-based: which table shows follows Settings, not a table ID in the block. Tabbed and Us vs Them pick an ID. Specs is a different type — no Add-to-cart auto inject.

What stores try until the grid is unreadable

One wide table in the product description. Men/women/kids side by side. Desktop looks complete. Mobile: horizontal scroll or clipped columns.

Three products so each grid has a URL. Men’s hoodie, women’s, kids’ — same fabric, three SKUs. Inventory and SEO suffer. The unisex page still has no clean trio of grids.

Theme tabs, content in metafields. Works until someone forgets the metafield. Not a Size chart type, no popup/plain in Design, no visibility per table.

None of those is: three enabled Size charts that match that SKU and stack in the Size chart block (or a shortcode per ID).

Three tables, one template — how they stack

OO - Advanced Table Builder is Free, 5.0 (1 review). Listing: size charts, specs, comparison, tabbed, Us vs Them. Visual builder or an AI draft from a description or screenshot. Excel / Google Sheets / AI. No other OO app in this post.

Separate Size chart tables, not one Structure mega-grid

Quick start: Create table → type Size chart, three times — or Generate with AI. AI docs: multiple charts in one photo (Men + Women) become separate blocks. Review Structure. Screenshot max 4 MB (PNG/JPEG/WebP/GIF).

In Structure: groups, modules, measurement blocks depending on type. Men, women, and kids do not belong as three columns in one measurement block. Three tables, or one Size chart with separate measurement blocks — not “add another column”.

Enable, visibility, and products: Enable on. Size charts: All products or Selected products only. For *this* unisex SKU: all three on Selected, including that product. If the men’s table is only on men’s SKUs, it will be missing on the unisex page — that was the earlier article.

One Size chart theme block; matching charts stack

Customize → Products → Default product (or the unisex template) → Add block → Apps → Size chart, near price / buy buttons. Auto-placement: embed on and no Size chart block → enabled matching charts can render above Add to cart. With a block, the block wins. Several matching charts: keep visibility tight or they stack. On this PDP you *want* the stack. Everywhere else: tight visibility, or three grids hang under every jumper.

Two Size chart blocks on the same template do not pick two IDs. The block is visibility-based. A second block duplicates the same matching set — not “block 1 = men”. To pin a table: shortcode `[oo-table id=YOUR_TABLE_ID]` (shortcodes), embed on, table enabled. Or a Tabbed table with three tabs — different type, own block, ID in the block settings.

App embed: Theme settings → App embeds → Tables, Specs & Comparisons. No embed means no auto-placement and no shortcodes.

Design: popup or plain per Size chart (popup vs inline). Three popups in a row is heavy; stacked plain grids or one Tabbed table is often easier to read. Translations: customer-facing strings per locale in Settings — revisit after Structure changes.

Worked example: unisex hoodie, three grids

The supplier sends one PNG with men, women, and 116–164. Generate with AI, 4 MB limit. Check: three Size chart tables, not one mega-column.

  1. Enable all three. Visibility: Selected products → only the unisex hoodie (and maybe the matching collection). Other SKUs keep a single chart, as in the earlier post.

  2. Unisex template: one Size chart block by Add to cart. Embed on.

  3. Storefront: three grids stacked, or triggers if Design is popup. Do not use a Specs block as a second size chart.

  4. Test a men-only SKU: the women’s grid must not stack there. That is visibility, not a second theme block.

A kids line with toddler / kids / teen on one product is the same pattern: three tables, one PDP.

Get it on the template

  1. Install OO - Advanced Table Builder (Free).

  2. Three Size charts (scratch or AI). Keep measurement blocks separate. Enable + Selected products on that SKU.

  3. Embed on. Size chart block on the unisex template, or a shortcode per ID, or Tabbed if you want tabs.

  4. Test unisex (stack) and a SKU with one chart (no leak).

  5. Specs stays a different type, with no ATC auto-inject.

Wrap-up

Shopify multiple size charts per product is not a wider HTML table. It is three Size charts that match the same PDP and stack — or shortcodes/Tabbed when you pin IDs. Native Shopify stops at Size as an option. Visibility keeps the rest of the catalogue clean.

Put those blocks in OO - Advanced Table Builder and let the next unisex hoodie show men, women, and kids — without one unreadable grid.

This blog is presented to you by

team member foto

Floris-jan de Vries

Co-owner / Back-end developer / Shopify Expert

As a full-stack developer, Floris-Jan ensures the technical logic behind the design. He also uses his extensive knowledge of Shopify every day to provide our clients with the best possible support.

social icon

You may also like:

A Shopify AI shipping rules flow is a draft you review. A new price needs the Advanced plan. Hiding a method does not.

shopify

2026-11-12
Floris-jan de Vries

When should AI draft your Shopify shipping rules flow?

A Shopify specs table that must follow price, weight, or a metafield needs a live module. A typed custom cell fails that test.

shopify

2026-11-12
Floris-jan de Vries

When are live Shopify product fields a must-have in a specs table?

online origins logo full

The Shopify Select partner for ambitious e-commerce businesses that want to grow!

linkedin online origins iconinstagram online origins icon

Reviews

5/5

Check on Google

Mail: info@onlineorigins.nl

Tel: 073 234 0612

KVK: 89825624

BTW: NL865123639B01

Bruistensingel 500,
5232 AH 's-Hertogenbosch
Cookies

© 2026 Online Origins