PREFLIGHT CHECK
Check that rows updating SKU, barcode, weight or inventory include the required Option1 name/value context before import.
🔒 Analysis runs in your browser; the file itself is not sent to BlueprintLab.
| Severity | Row | Column | Issue | Value |
|---|
This unofficial checker covers only rules that can be verified in the browser. Live account settings, remote server state and later service-side validation remain authoritative.
Check that rows updating SKU, barcode, weight or inventory also include the required Option1 name/value context.
URL handle,Title,Option1 name,Option1 value,SKU,Weight value (grams) sample-shirt,Sample Shirt,Size,M,SHIRT-M,250
In Shopify product CSVs, variant-related fields such as SKU and weight depend on Option1 name/value when updating existing products. Importing variant data without the option context can remove existing variants or replace them with a default variant.
This checker finds rows where variant-related values are present but the Option1 context is missing or incomplete.
A new simple product can be created with a default variant and no explicit custom option. That is why completely missing Option1 context is a warning rather than a universal error. A half-filled name/value pair is treated as a structural error.
Making every missing Option1 an error would create false positives for valid new simple products.
The checker looks at SKU, Barcode, Price, Inventory quantity, Weight value (grams), and their legacy Shopify equivalents. Only rows containing those values are evaluated for the dependency.
Product-level edits such as Description or Vendor alone do not trigger this rule.
For an existing product SKU update, export the current product CSV and keep URL handle plus option columns intact while changing only the intended variant fields.
Test on a small set first, especially when external apps depend on variant IDs.