WooCommerce CSV updates: why variation-parent mapping needs a staging test
WooCommerce store operators importing product catalogs can use the built-in CSV importer for bulk updates. A CSV file is not a complete picture of a store: the actual import mappings, existing product records, and WooCommerce version can affect the outcome.
A concrete failure mode observed in testing
Our local synthetic WooCommerce 11.2.1 importer tests, run against SQLite and MariaDB, found that updating an existing variation with a blank Parent field mapped to the parent identifier could detach the variation even when the importer reported success. In the tested cases, omitting or explicitly unmapping Parent avoided the detachment. These results are specific to the tested setup; they are not proof that all WooCommerce versions behave identically.
Before importing a product update
- Export a recent copy of the existing catalog from the same store and make a full backup.
- Identify variation rows and inspect the Parent column. Decide whether it should be mapped, omitted, or explicitly unmapped based on the intended update.
- When changing an existing SKU, verify how the importer identifies that product. Our synthetic update tests found that an unmatched replacement SKU without an existing product ID was skipped.
- Test the import on staging using representative parent and variation records. Inspect actual parent relationships and product attributes afterward, not just the success message.
- Review the final mapping screen and confirm results before touching production.
What the private preflight prototype can and cannot do
WooCommerce CSV Preflight is an offline, read-only research prototype that inspects proposed CSV files and optionally compares them with a recent same-store export. It flags structural problems and conditional risks. It cannot observe a merchant's final column mappings or guarantee the outcome of a live import. Its safe_to_import field remains `null` by design.
The prototype is not published or offered for sale. Paid development remains on hold because free competitors exist and buyer demand is unverified. This article is educational material, not a public tool download.
Sources and evidence boundaries
Official WooCommerce importer instructions: Official WooCommerce importer documentation — describes the built-in workflow and advises backups and test imports.
Internal research: internal WooCommerce CSV Preflight test notes — describes the version-specific synthetic importer trials and limitations. These are our own tests, not an official WooCommerce guarantee.
No live-store import, real merchant outcome, sales, or acquisition traffic is claimed here.