Shopify Bulk Edit via CSV: When to Use It (And When Not To) | AssetScope

Shopify’s CSV export/import is the go-to method for bulk product edits when the native admin falls short. It works — but it carries real risks that most guides gloss over. This article covers the full workflow, the common failure modes, and when a dedicated bulk editor is a safer choice.

How to Export Shopify Products to CSV

Navigate to Products in your Shopify admin, select the products you want to export (or all products), click Export, and choose CSV for Excel or CSV for plain text. Shopify generates the file and emails it to you or provides a download link.

The export includes every product field: title, body HTML, vendor, type, tags, published status, variants with prices, SKUs, barcodes, inventory quantities, images, and SEO fields. A large catalogue can produce a CSV with tens of thousands of rows.

What Fields Are Included in Shopify’s Product CSV

The Shopify product CSV has over 40 columns. Key fields: Handle, Title, Body (HTML), Vendor, Type, Tags, Published, Variant SKU, Variant Price, Variant Compare At Price, Variant Inventory Qty, Image Src, Image Alt Text, SEO Title, SEO Description.

Each variant is a separate row. A product with 5 variants occupies 5 rows in the CSV, with the product-level fields (title, body, tags) only on the first row. This structure is the source of most import errors.

How to Bulk Edit the Shopify Product CSV in Excel or Google Sheets

Open the CSV in Excel or Google Sheets. Use filters to find the products you want to edit. Make your changes — update prices, fix titles, add tags. For percentage price changes, use spreadsheet formulas.

Critical: do not change the Handle column, do not delete rows (this deletes products on import), and do not reorder columns. Save as CSV (not Excel format) when done.

How to Re-Import the CSV to Shopify

Go to Products → Import, upload your edited CSV, and choose whether to overwrite existing products. Shopify matches products by Handle. If a handle in your CSV matches an existing product, the import updates that product. If it doesn’t match, a new product is created.

The import can take 10–30 minutes for large files. During this time, product data is being updated live — customers may see partially-updated products.

Common CSV Import Errors in Shopify (and How to Fix Them)

Encoding errors: CSV files must be UTF-8 encoded. If you edit in Excel and save, Excel may change the encoding, corrupting special characters (accents, em dashes, currency symbols).

HTML in body field: Product descriptions contain HTML. Commas in the HTML can break CSV parsing. Always use the “CSV for Excel” format which handles this correctly.

Missing variant rows: If you delete a variant row from the CSV and reimport, Shopify may delete that variant from the product. This is often unintentional.

Image URL issues: Image Src URLs in the CSV must be publicly accessible. If the URL is broken or returns a 404, the import fails silently for that image.

Tag overwriting: The Tags column replaces the entire tag list on import. If you export, edit only prices, and reimport, the tags from export time overwrite any tags added since the export.

How to Validate Your Shopify CSV Before Importing

Before reimporting any edited CSV, run a validation pass in Google Sheets to catch the errors that will silently corrupt your catalogue. Start by checking for empty required fields: filter the Handle column and flag any blank cells, since a row without a handle will create a new product instead of updating an existing one. Do the same for the Title column — blank titles create ghost products that are invisible in your admin but still indexed by Google.

Next, check for duplicate Handle values within the CSV itself. If two rows share the same handle but have different product-level data (different titles, different body HTML), Shopify will process them in order and the last row wins — silently overwriting the first. Sort by Handle and scan for adjacent duplicates. This catches reimport errors where the same product appears twice because a previous export was merged with a new file.

Check price formatting: the Variant Price and Variant Compare At Price columns must contain plain numbers with no currency symbols, no thousands separators, and a period (not a comma) as the decimal separator. A single malformatted price will cause the entire row to fail silently. Finally, if your CSV contains Image Src URLs, open a few in a browser to confirm they resolve. Broken image URLs fail silently on import — the product is created but the image is missing, and there is no error log to tell you which products were affected.

What You Can’t Bulk Edit via CSV in Shopify

Metafields are not included in the standard product CSV (they require a separate metafield CSV export). Collection membership cannot be managed via the product CSV. Theme references and URL redirects are not part of the product export.

The CSV also cannot perform operations like “add this tag to all products” — it can only set the full tag list per product. For non-destructive tag editing, a dedicated tool is needed.

The Hidden Risks of the CSV Round-Trip

The CSV round-trip has several failure modes that are not obvious until they corrupt your data. The most insidious is data type mutation: Shopify exports tags as a comma-separated string, but certain spreadsheet applications (particularly Excel) will interpret tag values that look like dates or numbers and silently convert them. A tag called “2024” may become “2,024” or a tag like “3-4” may become a date. These corrupted values are reimported without warning.

UTF-8 encoding issues are the second most common failure. Product titles and descriptions containing accented characters, em dashes, or non-Latin scripts will display as garbled text if the CSV is saved in the wrong encoding. Excel on Windows is particularly prone to this — it defaults to ANSI encoding rather than UTF-8. Google Sheets handles UTF-8 correctly and is the safer choice for CSV editing.

There is also a metafield overwrite risk. Shopify’s product CSV does not include metafields, but if you use a separate metafield CSV export and reimport workflow, any metafield not present in the import file may be cleared. The CSV import is not a “merge” operation — it is a full replacement of the fields present in the file. Always verify which fields your import will touch before running it.

When CSV Is the Right Tool (and When It Is Not)

CSV is genuinely the best option in a handful of specific scenarios. Platform migrations from WooCommerce, Magento, or another Shopify store are the most common: you receive a data dump in CSV format and need to import it into a fresh Shopify store. One-time bulk imports of a new product line from a supplier feed are another valid use case — the data arrives as a spreadsheet and needs to be loaded once.

CSV is the wrong tool for routine operational tasks. Changing prices for a seasonal sale, adding or removing tags, updating vendor names, and fixing SEO fields are all operations that should be done with a dedicated bulk editor. The CSV round-trip adds unnecessary risk (encoding, overwriting, import duration) and unnecessary effort (export, edit, validate, reimport) when the same result can be achieved in minutes with an app-based tool that writes directly to the Shopify API.

If you are doing a task more than once, or if the task involves a single field across many products, a dedicated bulk editor is almost always the better choice. Reserve CSV for complex multi-field imports where no single tool covers all the fields you need to change simultaneously.

When to Use CSV vs a Bulk Editing App

Use CSV when: you need to make complex calculated changes across many fields simultaneously, you’re comfortable with spreadsheet formulas, and you have a backup strategy in case the import goes wrong.

Use a bulk editing app when: you need to edit a single field across many products (tags, vendor, prices, SEO), you want non-destructive operations (add a tag without overwriting others), you need formula-based pricing (percentage discounts, rounding), or you want to preview changes before applying.

For most routine bulk editing tasks, a dedicated app like AssetScope is faster and safer than the CSV round-trip. Reserve CSV for complex multi-field edits that no single tool can handle.

See all 15 tools in AssetScope →