Shopify metaobjects: what they are and what to use them for

Metafields vs. metaobjects: the difference that matters

A metafield is an extra piece of data attached to a specific Shopify resource: a product, a variant, a collection, a customer, an order or the store itself. It covers things like the fabric composition of a garment, the handling time of an order or a product video. The data lives inside that product and only that product.

A metaobject is a content type you define from scratch, with the fields you need, and it exists on its own. An ingredient card, a designer, a physical store, a size chart or an FAQ can all be metaobjects. You create each entry once and link it from the products or collections that need it through a metaobject reference metafield.

The practical rule is simple. If the data belongs to one product only, use a metafield. If the same block of information repeats across many products or has several fields that belong together, use a metaobject and reference it.

How to create them: definitions and entries

First you create the metaobject definition in Settings > Custom data. There you give it a name, choose the fields and their types (single line text, rich text, number, file, image, color, URL, product or metaobject reference, lists of values and so on) and pick which field acts as the display name of each entry.

Then you create the entries, which are the actual records. If your definition is Material, each entry is a different material with its name, description, photo and care instructions. Entries are edited in the admin like any other content, without opening the theme code.

When you define the metaobject you can turn on options such as storefront access, so the theme can read it, or translations for its fields. Plan for this from the start if you sell in several languages.

Use cases that work really well

Metaobjects shine when content repeats or follows a fixed structure. These are the cases we see most often in real stores:

• Size charts by garment type, linked from each product
• Ingredient, material or certification cards with an icon and text
• Designers, brands or manufacturers with a logo, bio and link to their collection
• Reusable FAQ blocks by product family
• A directory of retailers or distributors with address and opening hours
• Banners or notices the team changes without opening the theme editor

Showing them in the theme with dynamic sources

In an Online Store 2.0 theme, metaobject fields can be connected to section and block settings through dynamic sources. In the theme editor you can choose, for example, that a block title pulls the name of the material linked to the product. If the theme is built for it, this takes no Liquid at all.

For more elaborate layouts, such as looping through a list of ingredients with their icons or rendering a size chart with rows and columns, the usual approach is a custom section that reads the metaobject in Liquid. Once it is built, the team only fills in entries and the design stays consistent across the whole store.

Standalone pages from metaobjects

Shopify lets a metaobject definition have its own web page in the store. Each entry gets a URL and is rendered with a metaobject template you design in the theme editor. It is a very clean way to publish a directory of designers, a glossary, recipes or store listings without creating hundreds of pages by hand.

These pages can have their own SEO title and description, and they are included in the store sitemap. Before you turn them on, ask whether that content has search value on its own. If it is only supporting data for the product page, it does not need its own URL.

A complete example: the size chart

Picture a clothing store with four different fits: T-shirts, pants, dresses and coats. What you usually find is a size chart pasted as an image into each product description, sometimes out of date and almost never readable on mobile. Metaobjects solve this in an orderly way.

You create a Size chart definition with a name field, a text field for measuring instructions and a list of rows with each size and its measurements. Then you create four entries, one per fit. On the product you add a reference metafield pointing to that definition and choose the chart that applies. The product page shows the linked chart through a section designed to read well on mobile.

If a measurement for the pants fit changes tomorrow, you edit a single entry and every pair of pants in the store updates at once. The chart can also be translated, it shows as real text instead of an image, and the team needs no developer to maintain it.

The same pattern works for many other things: a care guide by fabric type, an allergen card per recipe or a warranty block by product family. The logic is always the same: define once, create a few entries and reference them from many products.

Common mistakes when planning them

The most frequent mistake is creating metaobjects without a thought-out data model. You end up duplicating fields, mixing types and filling definitions nobody uses. Before you create anything, map out what content you have, what repeats and where it will be referenced from.

Another mistake is storing in rich text what should be separate fields. If you put an entire size chart into a single text field, you lose the benefit of structure and cannot reuse each data point. And if your catalog is very large, check the limits on definitions and entries in the Shopify documentation, because they change over time.