Metafields and product options both add information to a product, so merchants mix them up all the time. The short version: metafields hold facts you set about the product, and options hold choices the customer makes. Once you sort each piece of data into the right bucket, your product pages, filters and order details all get easier to manage.
Metafields are for structured merchant data
A metafield is a custom field you add to a product, variant, collection or customer. You create the definition once under Settings, then Custom data, and fill it in per product. Shoppers never edit it. Typical uses:
- Product specs such as dimensions, material composition and care instructions.
- Related products, upsells and cross-sells, stored as product references.
- SEO metadata, such as a custom social sharing image per product.
- Print specs your team needs, like the required DPI or color profile for the print file.
Options are for customer choice
Options are what the shopper picks or types on the product page. They come in three kinds:
- Variant options such as Size, Color and Material. Each combination is a variant with its own price, SKU and stock.
- Custom inputs such as a name to engrave, an uploaded photo or a gift message. These have no stock, so they are saved on the order as line-item properties, usually through an app.
- Add-ons such as gift wrap or rush production, which may carry a fee.
If you are not sure whether a choice should be a variant or a custom input, our guide on variants vs line-item properties gives a simple test.
Side-by-side
| Metafields | Variant options | Custom inputs (line-item properties) | |
|---|---|---|---|
| Who sets it | You | Shopper picks from your list | Shopper types or uploads |
| Where it lives | Product or variant record | Product's variant table | The order line |
| Has stock or SKU | No | Yes | No |
| Changes per order | No | Yes, from a fixed list | Yes, free-form |
| Example | "Dishwasher safe: Yes" | Size: 15 oz | Name: "Priya" |
Can metafields drive options?
Yes, indirectly. Dynamic sources in Online Store 2.0 themes can pull metafield data into the product page, including the option area. A common example: the color swatch image for each variant comes from a metafield on that variant.
Some options apps also read metafields to decide which option set to show on which product. That is a setup convenience. The choices themselves still behave like options, and the shopper's answers still land on the order. We compare the two approaches in more depth in product options app vs metafields.
Access patterns
- Metafields in Liquid:
{{ product.metafields.custom.field_name }}, or without code through dynamic sources in the theme editor. - Options in Liquid:
{{ product.options }}for the option names,{{ variant.title }}for the selected combination. - Line-item properties: read from the order in the admin, in order notification emails or through the API.
Developers working with the Admin API will find the details in our guide to the metafield API and options.
Worked example: a personalized mug
Here is how we would split the data for an 11 oz and 15 oz photo mug with a custom name:
- Metafields: capacity note, "Dishwasher safe: Yes", care instructions, the print area size in pixels for your team.
- Variant option: Size with values 11 oz and 15 oz, each with its own price and SKU.
- Custom inputs: a text field labeled "Name on mug" with a 15-character limit, and a photo upload. With PIMW Product Personalizer, both are saved on the order line so your print partner sees exactly what to print.
Put the care instructions into a variant option and you get nonsense in your variant table. Put the name into a metafield and every buyer gets the same name. Each bucket has a job.
Common mistakes
- Creating variants for spec data. "Material: Ceramic" on a product that only comes in ceramic is a metafield, not an option.
- Hard-coding specs into descriptions. Metafields let you show them in a consistent block and reuse them in filters.
- Expecting metafields to collect input. They cannot. Use options or an app field for anything the shopper fills in.
- Adding structured data by hand. If you render specs from metafields, you can output them in your product schema too. Our guide to schema markup for personalized products shows how.
Frequently asked questions
What's the difference between metafield and product option?
A metafield is structured data you attach to a product, such as care instructions or dimensions. A product option is a choice the customer makes, such as Size or Color, and it creates variants.
Should I use metafields for size charts?
Yes. Size chart data is reference information you set, not a customer choice. Store it in a metafield and render it in the product template.
Can metafields replace product options?
No. Metafields have no customer-facing choice interface and do not create variants or order data. They solve a different problem.
Do metafields affect SEO?
Only when they are rendered on the page, because then the content can be indexed. You can also feed metafield values into your structured data.
Are metafields visible on the storefront?
Only if you show them through Liquid or dynamic sources in the theme editor. Creating a metafield does not display it automatically.
Can customers edit product metafields?
No. Product metafields are set by you in the admin or through the API. Anything the customer chooses or types belongs in options or line-item properties.
What is the difference between metafields and line-item properties?
Metafields live on the product or variant and stay the same for every order. Line-item properties live on one order line and hold what that customer entered, such as a name or photo.
How many metafields can a product have?
Enough for nearly any store. Shopify sets limits on the number of metafield definitions per resource type, but most merchants never get close to them.
Related reading
Sources & further reading
Primary sources referenced in this article. We link to official platform documentation and standards bodies rather than secondary summaries so you can verify claims directly.
- Shopify.dev: Metafields overview
- Shopify.dev: Metaobjects
- Shopify.dev: Admin GraphQL API reference
- Shopify.dev: productSet mutation
- Shopify.dev: API rate limits
- Shopify Help Center: Product variants
Try it free on Shopify
PIMW Product Personalizer's permanent Free plan includes live preview, custom options, and Cart Transform pricing.
Install PIMW Product Personalizer