A skipped WooCommerce CSV row is not necessarily a failed upload. First check which product the row identifies, whether you selected update mode, and whether the row's product type matches the intended record. Do not remove identifiers just to make the importer accept the file: that can change an update into a creation.
Version note, September 23, 2026: WooCommerce 11.2 is in beta. Its pre-release notes describe additional identifier matching. Use the beta only in an isolated test environment, not as an emergency fix on a live catalog. Older versions and third-party importers can behave differently.
Establish What One Row Should Do
Choose one skipped row, not the entire supplier feed. Write down the intended WooCommerce product ID, its current SKU, product type, and the one value you expected to change. For example, your test might update a synthetic product's description while leaving stock and price unchanged.
Export or inspect that existing record before altering the incoming file. Keep the original CSV intact. If you open a working copy in a spreadsheet, import identifier columns as text and check the saved raw file afterward. A visible leading zero on screen is not proof that the exported value preserved it.
Check the Identifier Precedence
For the 11.2 update path, the documented order is ID, then SKU, then Global Unique ID. The implementation notes explain unmatched identifiers and product-type guards. A nonblank identifier that resolves to no product can be skipped; a mismatched type can be refused.
Do not treat the global identifier as an instruction to override a different ID or SKU. When an ID belongs to another environment, a correct-looking GTIN elsewhere in the same row does not make the row safe. Resolve the contradiction first.
| Question |
What to inspect |
Safe next action |
| Was the file copied from another store? |
Whether its IDs identify the same products here |
Reconcile IDs before importing |
| Does the SKU contain extra whitespace or altered zeros? |
Raw CSV and current product record |
Correct the working copy, not the catalog blindly |
| Is the mapped global identifier blank? |
Mapping screen and raw cell |
Decide whether this is an update or intentional creation |
| Is a variation being matched to its parent? |
Resolved ID, parent relation, and product type |
Separate parent and variation rows |
| Does more than one record share a code? |
Catalog records carrying that identifier |
Resolve ambiguity before relying on automatic matching |
Run a Small, Observable Staging Import
Use synthetic products and a staging snapshot. Include one known matching row, the row that failed, and a deliberately unmatched row. Keep prices and stock out of the test unless those are the fields you are investigating. Record the importer version, update-mode setting, and column mapping before starting.
After importing, record the result for each row and inspect the resolved product. A success total alone cannot tell you whether the intended record changed. Compare the changed field, product count, type, SKU, and parent relationship. Then run the same controlled update again and check for duplicates.
Illustrative diagnostic aid. Record your own results; no customer testing is implied.
If the matching control succeeds but the problem row does not, compare identifiers and types. If every control fails, check the mapping and importer configuration before editing individual product data. Keep imports sequential while investigating; overlapping jobs make it harder to attribute changes to one file.
When to Stop and Repair the Feed
Stop when an identifier resolves to the wrong product, a variation points to the wrong parent, or repeated imports create extra records. Do not compensate by deleting the guard, stripping every SKU, or changing the row type until it passes. Those actions can hide the catalog error you need to fix.
This guide addresses record selection, not a full migration. Once matching is correct, use the product CSV roundtrip checklist to test images, attributes, and other business fields. Keep beta-specific observations separate from results on your current stable version.
If you need help tracing the mapping, ask HandL WP to investigate the import with the row number, sanitized identifiers, expected product ID, and exact importer message. Send a small redacted sample rather than a complete supplier or customer dataset.
Sources checked September 23, 2026. Examples and diagrams are explanatory, not measurements from a customer site.