Use the current column contract
Shopify’s CSV guide describes product import and export structure, variant rows and publicly accessible image URLs. It also warns that some included and omitted columns interact, giving an example where missing option columns alongside SKU can remove a variant option. Use the current official specification for the exact columns involved. AMZ12’s process below is independent operational guidance, not a tested import service.
A spreadsheet can look tidy while expressing an unintended catalog change. Begin by describing the desired result in one sentence, such as updating approved descriptions for a named group of existing products.
Preserve the starting state
Export the relevant records and keep an untouched copy with the date, store and purpose. Store the working file separately. Note which team owns any connected catalog or fulfillment system so that simultaneous updates do not overwrite each other unexpectedly.
Write a change manifest listing the product references and intended fields. Count products and variants separately. A file with many rows may represent additional images or variations rather than many independent products, so a single row count is a poor acceptance criterion.
Protect identifiers and relationships
Open identifier columns as text where the spreadsheet permits. Check leading zeros, long numeric strings and special characters before saving. Review product handles and option values against the exported baseline rather than rebuilding them from memory.
Keep each product’s related rows together during review. Sorting only part of a sheet can disconnect descriptions, images and variations from their intended product. If several people contribute, consolidate their changes into one controlled file and have one person verify relationships before import.
Use a small revealing batch
Select a simple product, a product with several variants and a product with multiple images. Include one record with punctuation or non-ASCII characters if the catalog uses them. Predict the resulting product details and visible storefront behavior before running the batch.
Check the platform’s import preview and options carefully. Stop on unexpected scope or warnings. The test should answer whether the proposed file structure produces the intended result, not merely whether the upload finishes. These are suggested acceptance steps; AMZ12 has not executed them in your account.
Reconcile data and presentation
Inspect or export the affected records after the small import. Compare intended fields with the manifest and inspect fields that should have stayed stable. Check variation choices, image association and the buyer-facing description on a representative page.
Log any discrepancy with the product reference, expected value and observed value. Resolve the cause before preparing the wider batch. A successful import message confirms processing, but the merchant still needs to confirm that the catalog expresses the approved information and that connected operations have the expected inputs.
Finish with a recovery record
After the wider update, save the final file, manifest, import result and reconciliation notes together. Identify who can decide on a corrective action if a later issue appears. Do not assume that reimporting an old file is always a complete rollback; unrelated changes may have happened since it was exported.
Close the task only after a second reviewer checks the agreed sample and outstanding exceptions have an owner. Controlled catalog work leaves a readable explanation of what changed and why, which is valuable when the next promotion or supplier update arrives.
Official reference: Shopify Help Center: product CSV files. Source checked on 29 October 2026. AMZ12 analysis and suggested checks are independent editorial guidance.