Skip to content
ShirtMath
SIZE DATA INTEGRATION

Shopify size chart apps and the measurement alternative

A chart widget puts your size table on the product page. It does not answer the shopper's actual question — which row is me — and that is the question fit returns come out of.

Last verified: 26 August 2026

A Shopify size chart app is a rendering layer. It stores a size table, attaches it to a product or collection, and shows it on the product page — usually a modal behind a "Size guide" link, injected as a theme app extension so nobody edits Liquid. That is worth having — a buried chart helps no one. It is also the ceiling: the chart hands the shopper back the problem they arrived with, deciding which row is them.

This page sits on the ShirtMath for Brands shelf, next to reducing fit returns and returns management. Below: what these widgets do, where the approach stops, and what you can and cannot integrate with ShirtMath today.

What a Shopify size chart app does

Stores a table. You paste in rows and columns, one chart per product type. The chart is content, not data: the app cannot tell whether the "20" in a cell is a flat chest width or a body circumference.

Attaches it to products. Rules match charts by collection, tag or product type. Most of the setup labour goes here, and so does the drift: a rule written in March serves the wrong chart to a style added in June.

Renders it at the decision point. An app block puts a link beside the variant selector and opens a modal. A minority also ask for height and weight and suggest a size — still off the same chart.

All of it is presentation. None of it changes the data underneath, where the fit problem lives.

Where a chart hits its ceiling

The chart rarely says what it measured. Body circumference and flat garment width are different numbers, and a column headed "Chest" can honestly be either. A shopper who measures around their chest and reads a flat width off your chart is out by roughly a factor of two.

The row is still a guess. A letter is not a measurement — it is the name a brand gives a set of numbers, and different brands give the same name to different numbers. One letter, across the eight blank tee styles ShirtMath holds specs for:

StyleChest at M (in)Length at M (in)
Bella+Canvas 3001C20.029.0
Champion T525C20.029.0
Comfort Colors C401720.529.5
Gildan 540020.029.0
Gildan G50020.029.0
Gildan G500L (ladies)17.526.0
Hanes 5250T20.029.0
Next Level 360020.529.0

The seven unisex styles agree within 0.5" at Medium. The ladies' cut is 17.5" — a 3.0" gap on the same letter, 3.5" at Large (19.0" against 22.0–22.5"). A shopper who knows they wear a Medium knows nothing useful about which of these fits, and no modal can tell them: the fact is in the data, not the presentation. The letter drifts within one brand over the years too — the separate problem vanity sizing documents.

Under both sits the tolerance the brands state on these specs: ±0.3–0.8". An engine promising quarter-inch precision on top of a chart promises more than the chart holds.

Garment-to-garment matching, mechanically

The alternative does not ask the shopper to describe their body. It asks for a garment they already own and already like, then subtracts.

  1. The shopper supplies a reference garment — a shirt from their own drawer, measured with a tape or photographed and read by the scanner.
  2. The engine compares it to your published per-size specs — point by point, for every variant you publish.
  3. The output is a signed difference in inches — this shirt is 0.5" wider in the chest and 0.5" longer than yours. Not a letter, and not a score in place of the numbers.
  4. The shopper picks a direction — closer to the body, or roomier. A judgement they can make, because they know the reference shirt.
Garment-to-garment comparison, in numbers A reference shirt at chest 20.0 inches, length 29.0 inches, compared with a catalogue Medium at 20.5 and 29.5 inches: plus 0.5 inches on both points. SHOPPER REFERENCE GILDAN G500, M CHEST 20.0 IN LENGTH 29.0 IN CATALOGUE VARIANT COMFORT COLORS C4017, M CHEST 20.5 IN LENGTH 29.5 IN DIFFERENCE, PER POINT OF MEASURE CHEST +0.5 IN · LENGTH +0.5 IN

The comparison runs over eight points of measure for tops, weighted by how much each decides whether a shirt fits. Bottoms have a separate eight, waist through outseam, and a top is never scored against them.

Point of measure (tops)Weight
Chest, pit to pit0.28
Body length, HPS to hem0.20
Shoulder, seam to seam0.16
Sleeve length0.12
Hem width (sweep)0.08
Bicep0.08
Sleeve opening0.04
Neck opening0.04

Where those numbers come from matters, and the methodology page states it plainly: a tape is exact, the photo scanner is experimental. About half of readings land within an inch of a real tape, so treat them as a guide and check anything that matters; sleeve opening and bicep are the least reliable — both carry the lowest weights above.

What a brand has to supply

Nothing exotic: the per-size flat measurements already on the spec sheet your manufacturer sends, keyed to the variant, with the unit stated. The standard is one line — flat, in inches, on a hard surface, seams smoothed, nothing stretched — and it has to be one standard, or the numbers do not compare. How to measure a shirt is that procedure for a person.

What you publish per variantShare of top-fit weightingWhat it supports
Letters only, no measurements0.00No match; excluded rather than estimated
Chest and body length0.48The working minimum
Plus shoulder and sleeve0.76Catches long-torso and short-arm mismatches
All eight top points1.00Full comparison, sweep to neck

The cost of stopping short is visible in ShirtMath's own catalog. Of 677 garment rows, 601 carry a chest and a length, but only 53 — eight styles — come from published spec sheets. Those rows carry a data confidence of 60 to 68, against 20 to 24 for the 476 rows built from category priors, a prior being a projection rather than a measurement. Bottoms are starker: 74 of them, 17 rows anywhere with a waist figure, the rest excluded from matching rather than given invented numbers.

What you do not need: new photography, 3D body scanning, a proprietary format, or shopper body data. For the finished shape, the t-shirt size chart is eight styles published exactly this way.

What integration actually looks like today

Plainly, before anyone spends a procurement cycle: there is no ShirtMath listing in the Shopify App Store. Nothing to install from it, and no partnership with Shopify. ShirtMath for Brands is pre-launch, and integration there means your published size data plus either a hosted widget or an API call your own front end makes — both reading the same per-variant measurement table, neither a one-click install.

Which makes the vendor decision and the data work separable, and the data work carries the long lead time: that measurement table is the asset a chart app can only render, never create.

One limit before anyone builds a business case: matching numbers are necessary, not sufficient. Two shirts can publish identical chest and length and still wear differently, because taper, drape and fabric weight are not on a spec sheet. Measurement matching removes the guesswork letters create. It does not remove the part of fit that lives in the cloth.

Questions from store owners

Do size charts reduce returns?
A chart helps a motivated shopper who owns a tape measure and will use it. That is the mechanism — real, but narrow. It does not remove the guess, it relocates it: the shopper still decides which row describes them, and that letter is not a constant. ShirtMath publishes no return-rate figure here, because it has not measured one. A percentage quoted at you is someone else's catalog, someone else's shoppers, and usually no control group.
What works better than a size chart?
Comparing your garment against one the shopper already owns and likes. That replaces a judgement — which row am I — with a subtraction: this shirt is 0.5" wider in the chest and 0.5" longer than the one in your drawer. No body measuring, no fitting room, no trust in the letter. The cost sits on your side: it only runs on published per-size measurements.
What data does ShirtMath need from my catalog?
Per-size flat garment measurements, keyed to the variant, in inches or centimetres with the unit stated. Chest and length carry 0.48 of the top-fit weighting on their own; shoulder and sleeve bring it to 0.76. They are already on your manufacturer's spec sheet. No new photography, no body scanning, no shopper body data.
Is there a ShirtMath Shopify app?
No. There is no ShirtMath listing in the Shopify App Store, nothing to install from it, and no partnership with Shopify. ShirtMath for Brands is pre-launch: integration today means your published size data plus a hosted widget or an API call, wired directly, once there are customers to wire.

The shopper half of this is already running. Scan a shirt to see the comparison a brand integration would run against your catalog, one garment at a time.

Scan a shirt