Variant specification tables for Shopify
Show the specifications that belong to the selected size or model.
Quick answer
Put shared facts, such as material and care instructions, in product metafields. Put changing measurements, such as capacity and height, in variant metafields. TableFlow can combine those sources in one table.
Start with two variants whose values differ. Connect each row to the right source, then compare the table with your Shopify data as you switch between them. Check the selector your customers actually use, including any custom theme controls.
Set up a table for the selected variant
When are your theme’s metafield blocks enough?
A supported Shopify theme can display metafields through its own sections and blocks. That may be enough when you have a few fields and the layout already fits your product page. Custom Liquid is another option when you can maintain the theme code.
Consider TableFlow when you want the same labelled table across a product family, controls for where it appears and a configured approach to empty values. For variant-specific rows, test both the initial selection and later option changes before extending the setup to more products.
Shopify’s metafield display guide
Should the value belong to the product or the variant?
| Question | Source to use | Example |
|---|---|---|
| Does this value stay the same for every option? | Product metafield | Care instructions shared by all sizes |
| Does this value change with the option? | Variant metafield | Height for a 500 mL or 750 mL bottle |
| Does the answer depend on the exact model being sold? | The matching product or variant source | A compatibility note verified for that model |
| Is the value unknown? | Leave it missing and choose how to display missing data | An optional package measurement that has not been confirmed |
Do not put a size-specific measurement in a product metafield merely because the product has a default size. That value can then appear beside a different selected size.
Example: two bottle sizes
These fictional values show the data plan. They are not measurements for a real product.
| Specification | Source | 500 mL variant | 750 mL variant |
|---|---|---|---|
| Body material | Product | Stainless steel | Stainless steel |
| Capacity | Variant | 500 mL | 750 mL |
| Height | Variant | 22 cm | 28 cm |
| Care | Product | Hand wash | Hand wash |
A table for the selected variant should show 22 cm when the shopper chooses 500 mL and 28 cm when they choose 750 mL. The shared material and care rows stay the same. Use the bottle specification tutorial for a complete field plan and sample storefront output.
How do you set up the table?
- List the values that change between saleable variants. Keep shared values in a separate list.
- Create product metafield definitions for the shared values and variant definitions for the changing values.
- Enter each value on the correct product or variant. Include clear units in the displayed answer.
- In TableFlow, give each row a short label and select the matching source. Follow the metafield guide and variant guide.
- Set the table's display conditions and storefront location.
- Choose the empty-row and empty-table settings, save the table, and check the storefront.
For furniture, start with the furniture dimensions tutorial. For fabric sold by length, use the fabric specification tutorial. Each tutorial gives a different data plan; replace all sample values with verified product data.
How should you test variant changes?
| Check | Expected result |
|---|---|
| Open the product with its initial variant | The displayed specifications match that variant |
| Select a variant with different measurements | The changing rows show the new values |
| Return to the first variant | Its original values return |
| Select a variant with an empty optional field | The row follows your chosen empty-value setting |
| Select a sold-out option, if the theme permits it | Any displayed specifications still describe that selected option |
| Repeat on a phone | Labels and units remain readable, and the selector still updates the table |
Test the actual selector that customers use. If your theme replaces the product section or uses a custom selector, confirm that the table still receives the change. If a value stays unchanged, first check its source: a product metafield will not become a different value just because the selected variant changes. Then check the saved table and contact support if the theme behavior still needs review.
FAQ
Does TableFlow create the missing specification values?
You supply the product data. Enter or correct the value on the appropriate source, then check the table. An empty value is not evidence that a product has no such feature.
Can shoppers see several variants beside each other?
That is a variant comparison table, which is a different layout from a specification table that follows one selected variant. The official listing places comparison tables on the Advanced plan. Check the current plan before you choose that workflow.
Is this a searchable order table?
This guide covers specifications for the selected product option. For a catalog with many variant rows and cart controls, review Table Master's variant product tables.
Which specification app should I choose?
Use the specification app comparison to check data sources, variant behavior, comparison plans, and free-plan limits before installation.
Show the specifications for the selected variant
Start with the TableFlow variant guide, then check each option in your storefront theme.