Shopify CSV header mapping rules for import files

What this guide explains

Learn how CSV header mapping works before using a Shopify import mapper.

• Header mapping should happen before row cleanup when the source file is not already Shopify-shaped.
• Product, inventory, and customer imports need different target fields, so one generic mapping is not enough.
• Consent fields should only be mapped when the source file has explicit consent data.

Map meaning, not just header spelling

Supplier and legacy exports often use labels such as Name, ID, Status, or Quantity for different concepts. Inspect several real values before assigning a source column. A reliable mapping states which source field owns the target, what transformation is needed, and what should happen when the source is blank.

• Separate product, inventory, and customer templates before mapping.
• Check whether identifiers are product-level, variant-level, or location-level.
• Keep unmapped source columns in a review list instead of dropping them silently.

Treat consent and destructive defaults as blockers

Marketing consent cannot be inferred from the presence of an email or phone number. Likewise, a missing stock value should not automatically become zero, and a missing status should not be guessed. Leave uncertain fields unmapped or route them to an exception report until the business rule is confirmed.

• Map consent only from explicit source evidence.
• Document value conversions such as yes/no to accepted target values.
• Test a small import and compare the resulting records with the source.

Sources and further reading

• Shopify Help Center: CSV files — Official CSV structure, encoding, spreadsheet editing, and import guidance.