SHOPIFY PRODUCT METAFIELD EXPORT GUIDE
How to export Shopify metafields to CSV—and find missing columns
Shopify can include defined product metafields in a product CSV export, but the result depends on the field’s owner and the definitions in that exact store. If a column is absent, confirm the definition before inventing a header or moving to a different CSV workflow.
Check exported CSV structureQUICK ANSWER
Define the field for products, export from the target store, and preserve its namespace and key.
The field must be a product metafield for the product CSV workflow.
Use the target store so its current definitions and identifiers appear.
Preserve the complete product.metafields namespace and key.
METAFIELD EXPORT CHECKS
Why a metafield is missing—or unsafe to edit
No metafield columns in the downloaded fileStart with Shopify’s product CSV export for product-owned fields
Shopify supports product metafields in the product CSV import and export workflow. An order, customer, collection, or inventory export describes a different resource and should not be expected to contain product metafield definitions.
Export products from the target Shopify store. Open the actual CSV file, keep its original header row, and search the headers for product.metafields. before changing the file.
A known custom field is absentThe metafield may not be defined for products in this store
Shopify includes a product metafield in product CSV exports after the product metafield is defined. A label visible in an app, theme, spreadsheet, or another store does not prove that a matching product metafield definition exists here.
In the target store’s custom data settings, confirm that the definition belongs to Products and note its namespace, key, type, and validation rules. Then create a new product export and compare the headers again.
Fabric (product.metafields.custom.fabric)The exported header carries the field’s namespace and key
Shopify identifies a product metafield with product.metafields.<namespace>.<key>. A current export can show a readable name followed by that identifier in parentheses, or the identifier by itself. The readable label can change; the namespace and key identify the field.
Preserve the entire exported header, including punctuation and the identifier in parentheses. Do not shorten it to Fabric, translate it, or reconstruct it from the label alone.
Variant custom fields are missingVariant metafields are not supported in the product CSV workflow
Shopify documents variant metafields as unsupported for product CSV import and export. A field owned by a variant will not become a supported product CSV column by adding variant.metafields to the header.
Use Shopify’s variant bulk editor, add the required metafield columns there, and perform the variant-level bulk edit in that supported workflow. Confirm the definition owner before choosing the export path.
The same field appears in one store but not anotherMetafield definitions and identifiers are store-specific configuration
Two stores can display a metafield with the same name while using different namespaces, keys, types, or validation rules. Copying one store’s exported header into another store does not create or safely map the missing definition.
Export from the store that will receive the final file. Compare its definition with the source store, then deliberately create or map any missing definition before moving values.
Exported values look encoded or unfamiliarThe cells preserve Shopify’s typed value representation
Metafields can store text, numbers, dates, colors, measurements, money, lists, product references, metaobject references, and other supported types. Reference values can use resource GIDs or handles, and supported list values use Shopify’s documented CSV representation.
Keep an untouched export as the format reference. Check the metafield definition before converting values, removing identifiers, changing separators, or letting spreadsheet software reinterpret dates and long IDs.
The export will be edited and imported againA valid export can still become an unsafe overwrite file
Shopify matches existing products by URL handle during product CSV updates. A blank included non-required column can clear the matching value when overwrite is enabled, while an omitted column preserves the existing value. Variant-related fields also depend on their option columns.
Keep URL handle, Title, the exact metafield header, and any dependent fields required by the columns you edit. Remove unrelated columns instead of leaving unintended blanks, test one product, and read Shopify’s preview before overwriting the full catalog.
KNOW THE BOUNDARY
What can be checked outside the Shopify admin?
Merch Preflight checks locally
- Recognizable product metafield header patterns
- Malformed product metafield identifiers
- Unsupported variant metafield columns in a product CSV
- CSV structure, product handles, and common dependencies
Shopify and your store must check
- Whether the metafield definition exists and owns the resource
- The field type, validation rules, and app configuration
- Whether reference records exist in the target store
- The export contents and final re-import result
Your product names, metafield values, SKUs, and supplier data stay in this browser.
FIVE-MINUTE CHECK
Before you edit a Shopify metafield export
- 1Confirm the resource owner
Use the product CSV only for fields defined on Products.
- 2Export from the target store
Obtain its current namespaces, keys, types, handles, and values.
- 3Keep an untouched copy
Use it to restore headers and compare value representations.
- 4Edit one explicit field
Preserve the exact header and use a value that matches the definition.
- 5Preview one product
Confirm the handle, field, blanks, and overwrite result before scaling up.
FAQ
Shopify metafield CSV export questions
Can Shopify export product metafields to CSV?
Yes. After a product metafield is defined, Shopify includes it in product CSV exports. Export from the target store so you get that store’s current namespace, key, type, and values.
Why are metafield columns missing from my product export?
The field might not be defined for Products in that store, might belong to another resource such as a variant, or might exist only in another store. Confirm the definition owner, then create a fresh product export.
What should the exported product metafield header look like?
It identifies the field as product.metafields.<namespace>.<key>. An export can also include the readable name followed by that identifier in parentheses, such as Fabric (product.metafields.custom.fabric).
Can the product CSV export variant metafields?
No. Shopify directs variant metafield bulk edits to its variant bulk editor. Confirm that the field is owned by Variants, then add the metafield columns in that supported workflow.
Can I edit the exported metafield values and import the CSV again?
Yes for supported product metafields, but preserve the exact header, URL handle, Title, field type, and dependent product columns. Test one product and review overwrite behavior before a broad update.
Official references
This guide follows Shopify’s current documentation on product metafields in CSV columns, overwriting product details, and metafield definitions and values. Shopify can change its templates and workflows; the target store’s current definitions, export, bulk editor, preview, and final result remain the authority.