If you’re going to build a Shopify metafield comparison table for apparel products, the schema decisions you make in the first 30 minutes determine how much maintenance the tables need from then on. Get the metafields right and SimplyCompare reads them directly. Get them wrong and you’ll spend the next quarter renaming fields and rebuilding tables. This page is the schema reference for an apparel catalog. The full setup walk-through lives at the parent Shopify comparison tables for apparel stores page.
Recommended metafield schema for apparel
Tops (tees, shirts, sweaters)
| Display name | Metafield key | Type | Example |
|---|---|---|---|
| Fabric | custom.fabric |
Single line text | 100% Supima cotton |
| Weight (gsm) | custom.weight_gsm |
Integer | 180 |
| Fit type | custom.fit_type |
Single line text | Slim regular |
| Chest width at M (inches) | custom.chest_width_m |
Decimal | 20.5 |
| Length at M (inches) | custom.length_m |
Decimal | 27.0 |
| Care | custom.care |
Single line text | Machine wash cold |
| Size range | custom.size_range |
Single line text | XS–3XL |
Bottoms (jeans, trousers, joggers)
| Display name | Metafield key | Type | Example |
|---|---|---|---|
| Fabric | custom.fabric |
Single line text | 98% cotton, 2% elastane |
| Fit type | custom.fit_type |
Single line text | Slim straight |
| Rise (inches) | custom.rise_inches |
Decimal | 11.5 |
| Inseam (inches) | custom.inseam_inches |
Decimal | 30.0 |
| Leg opening (inches) | custom.leg_opening_inches |
Decimal | 14.5 |
| Stretch (%) | custom.stretch_pct |
Integer | 2 |
| Size range | custom.size_range |
Single line text | 28W–40W |
How those metafields flow into SimplyCompare
Once your metafield definitions exist and you’ve populated values per product, the connection to SimplyCompare is automatic. Open the dashboard, click New table, select your products. The metafields appear as available rows in the row editor — drag them into the order you want, set display labels (e.g. “Inseam (inches)” instead of custom.inseam_inches), save. From that point, every change to a metafield value flows through to every comparison table that uses it.
Schema design tips for apparel catalogs
Anchor measurements to a labelled size. Don’t store “chest width” as 20.5 without a size context. Pick one (M is the convention) and use it consistently with a key like custom.chest_width_m.
Separate fabric content from weight. Two different metafields. Lets you sort or filter by either later.
Use product-level vs variant-level deliberately. Color and size are usually variants in Shopify; fabric and fit type are usually product-level. Set the metafield definition at the right level so you don’t end up duplicating data across variants.
Keep size range as text, not a list. “XS–3XL” reads more clearly than a list field rendering as [“XS”,”S”,”M”,”L”,”XL”,”2XL”,”3XL”]. SimplyCompare lets you choose either.
Frequently asked questions
Should fabric and fit type be product-level or variant-level metafields?
Product-level. They’re attributes of the garment as a whole. Color and size are variant attributes; everything else is usually product-level.
How do I display imperial and metric measurements for international shoppers?
Use parallel metafields (e.g. custom.rise_inches and custom.rise_cm) and build two table variants — imperial for one region, metric for another.
Can I include extended sizing as a comparison row?
Yes. Use custom.size_range single-line text. Write the full available range. SimplyCompare displays it.
What about products with multiple length options (e.g. 30/32/34 inseam)?
If lengths are variants, store inseam as a variant-level metafield and SimplyCompare can compare per variant. If you’d rather keep it simple, store the available lengths as text in custom.inseam_inches (“30 / 32 / 34”).
Are there field-count limits on a comparison table?
Practical limits matter more than technical ones. Tables with more than 12 rows are hard to scan. For deep apparel comparisons, split into “Fit & sizing” and “Fabric & care” tables.
Schema right, comparison sorted
Get your apparel metafields right and the comparison tables write themselves. SimplyCompare reads your schema, renders cleanly, and stays in sync as you grow your catalog.