Sizing is where apparel sales get won or lost. Two pairs of joggers in your catalog might list the same numeric size but fit differently because of rise, inseam, leg opening, and fabric stretch. Shoppers know this from experience, which is why a clear Shopify apparel size comparison table reduces returns and increases purchase confidence in equal measure. This page shows how to build one against your existing product data, using our Shopify comparison tables for apparel stores as the parent reference.
The model below assumes you store sizing data as Shopify metafields, so a single edit in the product editor flows through to every comparison table on your storefront automatically.
Recommended metafield schema for apparel size and fit
Pick the fields that match what your customers actually care about. The schema below covers the common decision-driving attributes for tops and bottoms; trim or extend it to match your catalog.
| Display name | Metafield key | Type | Example value |
|---|---|---|---|
| Fit type | custom.fit_type |
Single line text | Slim straight |
| Rise | custom.rise_inches |
Decimal | 11.5 |
| Inseam | custom.inseam_inches |
Decimal | 30.0 |
| Leg opening | custom.leg_opening_inches |
Decimal | 14.5 |
| Chest width (laid flat, size M) | custom.chest_width_m |
Decimal | 20.5 |
| Length (back of neck to hem, size M) | custom.length_m |
Decimal | 27.0 |
| Stretch percentage | custom.stretch_pct |
Integer | 3 |
| Size range available | custom.size_range |
Single line text | XS–3XL |
| Fits true to size | custom.fits_true_to_size |
Single line text | Yes / Size up / Size down |
Fill these in once per product. From that point forward, SimplyCompare reads them directly — you don’t re-type the values into a spreadsheet or a comparison-table editor.
Building the size and fit comparison table
Open SimplyCompare and click New table. Add the apparel products you want to compare — for size guides, three to five comparable products is the sweet spot, ideally within the same fit family (e.g. three slim-fit jeans, not slim plus relaxed plus jogger).
In the row editor, drag the metafields you set up above into the row order that matches how your customer thinks. A common ordering for bottoms: fit type, rise, inseam, leg opening, stretch, size range, fits true to size. For tops: fit type, chest width (size M), length (size M), stretch, size range, fits true to size.
Use SimplyCompare’s display labels to soften the field names. Show “Rise (inches)” instead of custom.rise_inches, “Stretch” instead of custom.stretch_pct. Customers should never see your back-end naming.
A sample apparel size comparison preview
Here’s roughly what a finished table looks like for a denim collection:
| Spec | Slim Straight 14oz | Relaxed Taper 12oz | Wide Leg 11oz |
|---|---|---|---|
| Fit type | Slim straight | Relaxed taper | Wide leg |
| Rise (inches) | 11.0 | 11.5 | 12.0 |
| Inseam (inches) | 30.0 | 30.0 | 32.0 |
| Leg opening (inches) | 14.5 | 15.5 | 20.0 |
| Stretch | 2% | 0% | 0% |
| Size range | 28W–40W | 28W–38W | 28W–36W |
| Fits true to size | Yes | Size up if between | Yes |
That table answers the questions your support team probably gets every week. And because it reads from your metafields, you’ll never need to update it twice.
Pro tips for size and fit tables
Anchor your measurements to a specific labelled size. “Chest width” without a size reference is useless. Pick one (size M is the convention) and use it consistently across the row.
Add a “fits true to size” row. The single most asked sizing question in apparel support tickets. Surface the answer directly in the comparison and you remove a friction point at the buy decision.
Mix size charts and comparison tables, don’t replace one with the other. A SimplyCompare comparison table tells shoppers how products differ. A traditional size chart tells them which size to pick within a single product. Both belong on the page.
Frequently asked questions
How do I display rise and inseam on a Shopify apparel comparison table?
Create decimal-type metafields under namespace custom with keys rise_inches and inseam_inches. Populate them on each product. SimplyCompare adds them as comparison rows when you select them in the row editor.
Can I show measurements in centimetres for international shoppers?
Yes. Use a separate set of metafields (e.g. custom.rise_cm) and create two table variants — one with imperial units and one with metric. Embed each on the appropriate region’s collection page.
How do I handle products that come in multiple lengths or inseams?
If each length is a separate Shopify product, fill in the inseam value per product and they’ll appear correctly in the table. If lengths are variants on a single product, set the value to a range (e.g. “30 / 32 / 34”) in custom.inseam_inches as text, or compare at the variant level using SimplyCompare’s variant-aware mode.
Will my comparison table show “fits true to size” feedback automatically?
Only if you store it. Add a custom.fits_true_to_size metafield on each product (Yes / Size up / Size down) and add it as a comparison row. SimplyCompare will then display whatever you’ve stored, kept in sync as you update.
Can shoppers see the table without leaving the product page?
Yes — the SimplyCompare app block can be embedded on a product page, a collection page, or a dedicated comparison landing page. Most apparel merchants embed on the collection or a “compare jeans” landing page, then link to it from product pages.
Sizing accuracy you don’t have to maintain
Once your sizing metafields are populated, SimplyCompare keeps every apparel comparison table in sync with your Shopify catalog. Update an inseam, change a fit type, expand a size range — your tables reflect the change instantly, on every page they’re embedded.