Why Shopify product CSVs can't update variant metafields — and what to do instead
A supplier sends you a spreadsheet with a part reference for each size of a shirt. You export the product from Shopify to find the matching column. The sizes are there, along with their SKUs and prices. The supplier reference is missing. Before you rename a header or try another import, check where the reference belongs. That determines which editing tool can update it.
Find out who owns the field
A product metafield holds information shared by the whole product. A care instruction might apply to every size of a shirt. A variant metafield holds information for one particular version. If the supplier uses different part references for small and medium, each reference belongs on its own variant. The SKU identifies the variant in this example. The supplier reference is the value you want to store on it.
Shopify’s product CSV supports defined product metafields. Shopify documents a separate limitation for variant metafields. Its product CSV import and export can't carry those values. A variant can appear as a row in the export and its custom field can still be missing. Renaming the column or creating a product metafield with the same name would leave you editing the wrong field. Shopify’s product CSV guide
For a small batch, use the variant bulk editor
- In Shopify admin, open Products, choose the product, then select the individual variants in the Variants section. Choose Bulk edit.
- Open Columns. Show SKU and the variant metafield you want to update. If the field is missing, check its definition under Settings → Metafields and metaobjects → Variants. Confirm the name and type before editing.
- Compare one supplier SKU with the SKU shown in the grid. Enter the supplier reference in the metafield cell on that same row. Keep SKUs as text in your spreadsheet so a leading zero survives.
- Save, then reopen that variant and check the stored value. For the remaining rows, match each SKU again. A spreadsheet sorted by size can be in a different order from the admin grid.
For a handful of references, this gives you a way to finish the job inside Shopify. Shopify’s instructions for editing variants
Work through a supplier file
Download the synthetic supplier CSV. It contains three invented rows. Open it in a text editor or spreadsheet. This is an exercise in matching supplier data. Keep it out of Shopify’s native product importer.
Suppose your store already has a single-line text definition on variants called custom.supplier_reference. Here is how to read each column when reviewing an import.
| CSV column | What to do with it |
|---|---|
| SKU | Find exactly one existing variant. Preserve spelling, spaces and leading zeros when inspecting the source. |
| Vendor Ref | Map this text to the existing variant field custom.supplier_reference. |
| Product Title | Ignore it for this update. Supplier wording can differ from your storefront title. |
| Price | Ignore it too. This job only changes the supplier reference. |
Look at the two rows for DEMO-TEE-M. One proposes REF-242, the other REF-249. If both were processed, which reference would you want on the medium shirt? The file gives you no basis for choosing. Set both rows aside and confirm the intended value with the supplier before preparing a corrected copy. The small shirt, DEMO-TEE-S, has one candidate, REF-241. Even that row needs an exact match in your own catalog before it can be approved.
For repeated files, review the changes by SKU
Keep an untouched copy of each incoming file. Start with a small batch of known SKUs. In a variant metafield importer, choose the destination definition, map the supplier’s reference column and explicitly exclude title and price. Check how the tool treats empty values. A blank could mean the supplier omitted a reference; clearing a stored value would be a different instruction.
Inspect the proposed changes against the current values. Separate missing SKUs, duplicate matches and unchanged values from rows you intend to update. Check which rows the tool would apply if part of the file fails. Before confirming a real import, retain the old values or verify the tool’s restore limits. Afterwards, reopen a changed variant and check its reference against the source.
The right tool depends on the file you receive. Fieldloader starts with an export of one metafield that you edit and return. Shoperize describes mapping supplier columns by SKU and reviewing proposed changes. Compare how each handles your headers, blanks, errors and recovery before choosing a workflow for the next delivery. Fieldloader workflow · Shoperize listing
Would this help with your next file?
VariantSafe is in development. There is no app to install or payment to make here. This is a hypothetical question about a future service that would let you review and apply supplier reference updates by SKU. An answer is neither a preorder nor a commitment.
Would you pay €11.99/month to process your NEXT supplier CSV in the next 30 days?
- A. Yes, I expect another supplier CSV within 30 days
- B. One-time CSV need
- C. No