Metafield definitions that reference metaobjects can now be transferred between stores.
🚀 What’s New # Cross-store metafield definitions – validation values for metaobject_reference, list.metaobject_reference, mixed_reference, and list.mixed_reference types now use portable type handles instead of store-specific GIDs. Flexible import format – imports accept both type handles (features) and GID format for backwards compatibility. 🔧 Improvements # Cleaner exports – mixed_reference validations with multiple allowed types now export as comma-separated handles (camera_specs, speaker_specs) instead of JSON arrays.
We’ve added support for article_reference and list.article_reference metafields which Shopify introduced on September 23rd. This will make it easier to link articles in your metafield data.
🚀 What’s New # Article reference metafields – import and export article_reference and list.article_reference metafield types. Handle-based resolution – reference articles using their handles (blog.article_handle) for easier data management.
Importing metafields just got easier. No more guessing metafield types or cluttering your column headers with type specifications.
🔧 Improvements # Metafield type detection – automatically detects types from your Shopify metafield definitions when not specified in column headers. Simplified column headers – use Variant Metafield: custom.color_primary instead of Variant Metafield: custom.color_primary [list.metaobject_reference]. Smart caching – avoids repeated API calls by caching metafield definitions during import runs. Cross-object support – works for products, variants, customers, orders, collections, and all other supported object types.
When exporting metafield and metaobject definitions, we now automatically exclude Shopify-managed definitions that cannot be imported due to API restrictions.
🔧 Improvements # Metafield definition exports – automatically exclude Shopify namespace definitions that cannot be imported. Metaobject definition exports – filter out Shopify-managed definitions by default to prevent import failures. Pre-configured filters – smart defaults are applied when selecting these object types, but can be customized as needed.
We’ve optimized how metafields are discovered during product exports to make the process faster and more reliable.
🔧 Improvements # Metafield discovery – product exports now detect custom metafields more efficiently. Large catalog support – reduced API calls when exporting products with extensive metafield usage.
