Metafields in Shopify are similar to custom fields in NetSuite. Metafields are used to store additional information about the Shopify resource. The additional information stored in metafields can be almost anything related to a resource. Some examples are specifications, customer comments, additional notes, size charts, downloadable documents, release dates, images, or part numbers. Merchants and other apps can retrieve and edit the data that’s stored in metafields from the Shopify admin.
A metafield includes the following parts:
- Namespace: A container for a group of metafields. Grouping metafields within a namespace prevents your metafields from conflicting with other metafields with the same key name.
- Key: The name for the metafield.
- Type: The type of the data that the metafield stores.
- Value: The data to store in the metafield. The value is always stored as a string, regardless of the metafield’s type.
Metafield Types
The metafield types defines the type of the data that metafield can store. The metafield types have built-in validation. Different metafield types are multi-line text, single-line text, rating, dimension etc.
Creating MetaFields
- From the Shopify Admin go to Settings > Metafields
2. Then we can create metafields for the following:
3. Select any of the part that we want to create the metafield.
4. Click on the Add Definition
5. Then add the metafield definitions.
6.We can also add the content type. If we are select the content type as Text then,
7. Then click on Save button. The meta field is created and it is available with other Customer fields.
Private metafields
Private metafields are similar to other metafields, but they have the following limitations:
- Private metafields are accessible only by the app that created them.
- Private metafields are deleted when the app that created them is uninstalled.
- Private metafields are accessible only from the GraphQL Admin API. They’re not accessible through Liquid or the Storefront API.
- An app can create a maximum of 10 private metafields per resource.
- Private metafields don’t support metafield definitions