Update existing WooCommerce products through CSV when you need a controlled change to prices, stock or other supported fields. Preserve stable product IDs or SKUs and import only the columns you intend to change.
IN THIS ARTICLE
01 Prepare a reversible update
Export the affected products first and keep that original file unchanged. Create a working copy containing the matching identifier and the fields being updated. Confirm that IDs belong to this store; IDs from another installation may refer to different products. Check SKUs for uniqueness and spreadsheet formatting changes.
02 Apply a test update
- Back up the database and test a small representative sample on staging.
- Open Products > All Products > Import and upload the working CSV.
- Select Update existing products.
- Review identifier mapping and map only the approved update fields. Ignore unrelated or blank columns whose effect has not been reviewed.
- Run the importer and save the success, skipped and failure report.
- Inspect the changed products and compare them with the original export before running the remaining batches.
Will unmatched rows always be ignored?
Ordinary unmatched product rows are skipped in the update workflow, but current WooCommerce versions can create qualifying new variation rows for an existing variable parent during an update import. Check the installed version and current variation-import rules. Do not use the update checkbox as a blanket guarantee that no new records can be created.
How do I avoid overwriting fresh stock changes?
An export is a snapshot. If customers continue ordering while you edit it, its stock values may become stale. Coordinate with the inventory owner, omit stock when updating unrelated fields, or use a controlled synchronisation process that accounts for live sales. Do not restore yesterday's quantities just to change today's descriptions.
03 Verify and recover narrowly
Check prices, sale dates, tax settings and stock on several affected items, including variations. Confirm a non-targeted product remains unchanged. If values are wrong, correct only the affected fields using the saved export and current business records. A whole-database rollback can lose orders created after the import, so use a targeted recovery plan whenever live transactions have continued.