Metafields
Room for every detail.
Fabric composition, care instructions, warehouse references, delivery notes. Define the fields your store needs, fill them in where you already work, and choose where they appear.
Define a field once.
A definition is the reusable setup for one kind of information: what it applies to, the kind of value it takes and the rules that value must follow. Create it in Settings and the field is ready on every product, customer, order or page it applies to.
- Fifteen places to attach it
- Products, variants, customers, orders, order items, cart lines, wishlist lines, collections, categories, pages, blog posts, blog categories, vendors, brands and the store itself.
- 18 value types
- Text, numbers, true or false, dates, URLs, JSON, choices, files, product and variant references, and lists of most of them. Store Admin offers only what the chosen resource supports.
- A handle that stays put
- The namespace and key form the handle themes and integrations use, such as details.care. They, the resource and the type are fixed once the field exists, so saved values keep their meaning.
- Choices with stored values
- Each choice has a label and a stored value, filled in from the label until you change it. Paste a list to add many at once. Renaming a label keeps saved selections; a choice still in use can’t be removed.
- Limits you set
- Set an optional character, value-length or list-size limit, and a sort order for the field. A limit can’t be tightened below values already saved.
- Nothing removed by accident
- A definition can’t be deleted while values still use it. Namespaces starting with app: are reserved for installed apps.
Fill in values where you work.
Product values are edited in the product form, and variants can carry their own. Customer values sit with the customer, order and order-item values with the order. Each value follows its definition’s rules.
- Content and the store
- Values for collections, categories, pages, blog posts, blog categories, vendors, brands and the store itself are edited in Settings > Metafield Values, in Store Admin or the mobile app.
- The right input for each type
- Reference fields open a picker, choice fields show their options and list fields take more than one value. Each input follows the definition’s limits.
- Review before you save
- New and changed values are marked until you save. A cleared value shows Will be removed, with an undo.
- Clearing stays local
- Clearing a field removes that resource’s value only. The definition and values saved elsewhere stay as they are.
- Bulk edits by CSV
- Product exports include product and variant metafield columns, written as Metafield: namespace.key. A Product Update CSV changes them in bulk, and __CLEAR__ removes a value.
- Fields from apps
- Installed apps can add their own fields. Depending on the access the app chose, your team can edit the value, only view it, or not see it in Store Admin.
Speak every store language.
Make a text field translatable and give its value a translation for each language your store has enabled. Choice fields translate the labels shoppers see, never the saved choice.
- Text and lists of text
- Text and list-of-text values can be translated on products, variants, collections, categories, pages, blog content, vendors, brands and the store.
- Choice labels
- For choice fields, translate each label. The stored value is the same in every language, so filters and integrations keep working.
- Always something to show
- When a translation is missing, the base-language value is used.
- Products in Translations
- Product and variant metafields are translated in Translations, alongside the product’s other translatable fields.
- Definition names too
- Translate a definition’s name from the translate button next to it, or in Translations > Metafield names with AI translation and CSV import and export.
- Switching it off
- Turning translation off removes the translations saved for that definition. Store Admin asks you to confirm first.
Put them to work on your storefront.
Every field is for your team until you decide otherwise. Make it visible on the storefront and your theme can use it, and eligible fields can feed search and product filters.
- Your theme decides
- Visible on storefront makes a value available to your theme. It doesn’t appear on a page until the theme shows it.
- Searchable
- Text and choice fields can be included in storefront search, which uses the translated value when one exists for the shopper’s language.
- Product filters
- Product and variant fields with choices, true or false, or numbers can become filters. Add the filter in Products > Filters and choose the label shoppers see.
- Themes bring their own
- A theme declares the fields its sections read. Installing it creates those definitions, or adopts a matching one your store already has.
- Staff-only data
- Customer, order and order-item fields stay in Store Admin. They have no storefront, search or translation options.
- Apps and the API
- Apps can keep their fields private or share them with other authorised apps. Sharing never makes a value public on your storefront.
- Changes in sync
- Subscribed apps with read access receive metafield value changes, filtered to what each app may read.
- Cart line fields
- Cart and wishlist line fields take text, true or false, a date or a single choice, and can be hidden from buyers, read only or buyer editable. In the cart, the field’s name is the label shoppers see.
- When an app is removed
- Its definitions and values are kept for 48 hours. Reinstall the app within that time and the data stays.
