12 docs tagged with "metafields"

Yes, except for app-owned metafields, which only the app that created them can access.

Enable the "Filtering for products" option on a definition so products can be searched by its value.

Bulk-edit metafields in a spreadsheet-style grid, with copy-paste support for Excel and Google Sheets.

Export metafields (and metaobjects) to a CSV file for backup, migration, or bulk editing offline.

Bulk-create or update metafields from a CSV file, matching resources by handle, SKU, barcode, or email.

Install the browser extension to manage Shopify metafields directly from the admin panel.

Bulk-delete Shopify metafields, even whole namespaces with auto-generated keys, via CSV export - clear values and re-import with "delete empty metafields" on.

Delete a known metafield (namespace + key) from every filtered resource at once - up to 5 metafields per run, across any number of resources.

Start here - an overview of Metafields Guru and how to create your first metafield.

Usually a mismatched type, namespace, or key between your Liquid code and the metafield.

A custom data field, made of a namespace, key, and value, that Shopify lets you attach to any resource.

Switching to a new theme won't delete metafields, but it might affect your shop’s storefront.