Can I use Metafields Guru to edit metafields created with another app?
Yes, except for app-owned metafields, which only the app that created them can access.
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, offline bulk editing, or migration to another store - in Default, Readable, or Migration mode.
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.
Copy metafields, including product, metaobject, and file references, from one Shopify store to another with the Migration export mode in Metafields Guru.
Recommendations for building a CSV file for the Metafields Guru import in the "rows" and "columns" formats - required columns, headers, metafield types, and a short example of each.
Start here - an overview of Metafields Guru and how to create your first metafield.
Which value formats the Metafields Guru CSV import accepts for every Shopify metafield type and list type - with input/output examples, normalization rules, and common pitfalls.
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.