METAFIELDSStructured product data
SELLWRIGHTMost product pages start with everything in the description: specs, materials, care instructions, maybe a size chart pasted in as an image. That works until you need to update the size chart on 200 products, show specs in a tidy table, or let shoppers filter by material. Shopify's metafields and metaobjects store this information as structured data instead, so it is entered once, checked as it is saved, and shown the same way everywhere.
What's the difference between a metafield and a metaobject?
A metafield is an extra field on something Shopify already has; a metaobject is a new type of record you define yourself. Shopify's own examples draw the line clearly: care instructions on a product belong in a metafield, while a size chart, a store location or an ingredient is a metaobject. Most stores use both together. The metaobject holds the record, and a metafield on each product points to the entry that applies.
What belongs in product metafields?
Anything that describes one product and differs from product to product. Good candidates:
- Measurements such as dimensions, weight or volume, which Shopify stores as typed values with units.
- Materials, care instructions or a short list of what's in the box.
- Files such as a manual or a spec sheet.
- Companion or replacement products, using a product reference.
Variants can have metafields too, which suits details that change by size or colour. Keep the description for the selling copy, and move anything a shopper compares between products into fields.
Why create a definition first?
A definition turns a loose value into a proper field. It sets the name, the type and the validation rules, so a weight has to be a weight and a rating has to sit between its minimum and maximum. Shopify then gives editors a typed input in the admin, checks values as they are saved, and supports search and filtering. A metafield without a definition is stored as plain text that can't be validated or searched.
Definitions also make storefront filters possible. Shopify's Search & Discovery app can turn product and variant metafields into filters, such as material or fit, but every metafield filter needs a definition and a supported type: single-line text, numbers, true or false, or metaobject references.
When does a metaobject make more sense?
When the same content applies to many products, or needs several fields of its own. A size chart is the classic case. Build a size chart metaobject with fields for the measurements and a fit note, create one entry per chart, then give each product a metafield that references the right entry. Update a chart once and every product that references it shows the change.
Other good fits are designer or author profiles, ingredient details, warranty terms and FAQs shared across a product line. Metaobject definitions live under Settings > Custom data in the admin and entries under Content > Metaobjects, so your team edits them without touching the theme.
Choose types carefully at the start. If a metafield later moves to an incompatible type, such as from a date to money, its existing values become invalid and have to be cleared or fixed.
How do you show them on product pages?
In a theme that supports dynamic sources, you connect them in the theme editor. Select a section or block setting, click the connect dynamic source icon and choose the metafield. Connect a metaobject reference to a block and Shopify maps its compatible fields to the block's settings, so a text setting takes a text field and an image setting takes an image field.
Two things to check. Which settings accept dynamic sources depends on your theme, and some types, such as lists of product references, need a custom section. For a vintage theme, or anything the editor can't connect, a developer displays the metafield with Liquid.
Where to start
Pick one product type and list everything shoppers ask before they buy. Each answer that differs by product is a metafield; each one shared across many products is a metaobject. Our Shopify stores service sets up the definitions, sections and templates, or send us a product page you'd like to improve.
FAQ
Frequently asked questions
What are category metafields in Shopify?
They are metafields linked to product categories in Shopify's Standard Product Taxonomy, such as clothing size, neckline or sleeve length for shirts. They come with default entries you can use as they are or customise, and you can use them as storefront filters and as dimensions in Shopify's analytics and reports.
Can metaobjects have their own pages on our store?
Yes. If a metaobject definition has storefront access, you can publish each entry as a web page, laid out by a metaobject template you build in the theme editor. That suits designer profiles or ingredient guides, and you choose which fields fill each page's title and meta description for search.
Do apps store data in metafields too?
Yes. Apps can keep their own data in metafields and metaobjects under a reserved namespace, so it can't collide with your custom data or another app's. Some review apps, for example, write ratings to Shopify's standard reviews metafields, which a theme can then display directly from Liquid.
Will metafield filters show on any Shopify theme?
Only if the theme supports filters. You can create product, variant and category metafield filters in the Search & Discovery app on any theme, but customers won't see them unless the theme displays filters. Check your theme's documentation, or ask its developer, before planning a catalogue around them.
Do we need a developer to set up metafields?
Not for the basics. Store owners can create definitions, fill in values and connect them in the theme editor, as long as the theme supports dynamic sources. A developer helps when you need a custom section to display the data, Liquid changes in a vintage theme, or a data model planned across a large catalogue.
