A field vs. a thing
A metafield extends something Shopify already has: a product gets a "Care" field, a collection gets a "Season" field. A metaobject is its own entity, with its own fields, that products link to. "Brand" is the clearest example: instead of typing your brand's name and story into every product, you create one "Acme Outdoor" brand entry with a logo, a story and a founded-in year, and every product in that brand links to it.
Where this pays off
- Brands and designers — one entry, linked from every product that belongs to it. Update the story once.
- Authors or contributors — a bio and photo reused across a catalog of books or courses.
- Size guides — one guide per fit category, linked from every product that shares it, instead of a size chart copied onto each one.
- Care instruction sets — "Hand wash cold" written once, linked from every product that needs it.
Change the shared entry, and every product that links to it updates. That's the opposite of a size chart pasted into fifty product descriptions, each one slightly different by the third edit.
Metaobjects move with your products
Content entries — Shopify's name for metaobjects in the admin — are one of the types a clone copies into staging, along with the products that link to them, so a staging store you build from doesn't end up with broken links to entries that were never copied.
If you're typing the same paragraph into more than a handful of products, it's probably a metaobject waiting to happen, not a metafield.
Build it once, link it everywhere.
Join the waitlist: 50% off your first yearRead next: Metafields · Why we built a Table field