Skip to the sample report

WooCommerce · Sample report

Sample report: WooCommerce CSV check

This synthetic catalog shows the two safe fixes and the re-check of the complete result. It contains fictional products and no customer data.

Example content:

Result summary

File: demo-catalog.csv · SHA-256: a9bef6c33dba387123c7703b43e67db3c14042cd22115cb4db6f421d418a5810
Delimiter: , · UTF-8 BOM: no · Tool version 0.2.0, rules checked against WooCommerce 11.1.2
No problems found in the checks we run
366
CSV records
366
Product records
38
Parents (variable)
304
Variations
24
Other products
10
Errors found
10
Errors fixed
0
Errors remaining
0
Warnings after fixes
0
Unsupported scenarios

"Errors found" counts errors in the original file. "Errors fixed" and "Errors remaining" come from the re-check of the corrected data for the whole file. The free part contains only the selected groups (50 of 366 product records); it is not the complete corrected file. These counters refer to the whole processed file.

Next steps

No blocking problems remain after the automatic fixes. This is the published demonstration file: the complete corrected result, its UTF-8 BOM copy and the ZIP of import batches are free to download, no purchase needed. Before importing, test a few products on a staging copy of your store.

Supported scenario: Creating new products with the built-in WooCommerce CSV importer (Products → Import, without "Update existing products"). Parents (variable) and variations (variation) in one file, linked by SKU in the Parent column, local attributes. Passing these checks does not guarantee a successful import into every store.

Free part

Free part: 10 product groups, 50 of 366 product records. This is not the complete catalog; the complete corrected result is free to download as well.

The free part contains only whole product groups (a parent with all of its variations, or a standalone product) that pass all checks after the automatic fixes. It was re-checked before being offered.

Automatic fixes

Value changes: 2. Moved records: 9. These are the changes full processing applies to the whole file.

Value changes

Show the value changes table (2 rows)
Original recordSKUFieldBeforeAfterReason
13000210-S-NAVParent·000210000210Leading/trailing spaces in Parent; without them the value unambiguously points to the parent in record #11.
16000210-L-GREParent000210·000210Leading/trailing spaces in Parent; without them the value unambiguously points to the parent in record #11.

Reordering

Show the reordering table (9 rows)
Original recordSKUOld positionNew positionReason
10TEE-100102Position shifted because variations were moved; relative order is preserved.
2TEE-100-S-W23Variation moved directly after its parent (original record #10).
3TEE-100-S-B34Variation moved directly after its parent (original record #10).
4TEE-100-M-W45Variation moved directly after its parent (original record #10).
5TEE-100-M-B56Variation moved directly after its parent (original record #10).
6TEE-100-L-W67Variation moved directly after its parent (original record #10).
7TEE-100-L-B78Variation moved directly after its parent (original record #10).
8TEE-100-XL-W89Variation moved directly after its parent (original record #10).
9TEE-100-XL-B910Variation moved directly after its parent (original record #10).

After automatic fixes (re-check)

No blocking problems after automatic fixes

After automatic fixes, no blocking problems remain in the supported scenario.

Record numbers below refer to the corrected order; "Original record" is the number in your original file.

Show the remaining problems table (1 row)
LevelCodeRecordOriginal recordFile linesSKUFieldExplanationRecommended action
Info UNKNOWN_COLUMN —— — — Supplier note The column "Supplier note" is not part of the built-in schema, so WooCommerce does not import it by default. Its values are kept unchanged. If it is a custom field, rename the column to "Meta: your_key" (with a space after the colon) or choose "Import as meta data" on the column mapping screen.

Problems in the original file

Show the problems table (11 rows)
LevelCodeRecordFile linesSKUFieldExplanationRecommended action
Error VARIATION_BEFORE_PARENT
auto-fixed in processed result
2 3 TEE-100-S-W Parent The variation (record #2) comes before its parent (record #10). WooCommerce creates a temporary placeholder parent without attributes, and the variation's attributes are lost. Fixed automatically: rows are reordered so the parent comes before its variations.
Error VARIATION_BEFORE_PARENT
auto-fixed in processed result
3 4 TEE-100-S-B Parent The variation (record #3) comes before its parent (record #10). WooCommerce creates a temporary placeholder parent without attributes, and the variation's attributes are lost. Fixed automatically: rows are reordered so the parent comes before its variations.
Error VARIATION_BEFORE_PARENT
auto-fixed in processed result
4 5 TEE-100-M-W Parent The variation (record #4) comes before its parent (record #10). WooCommerce creates a temporary placeholder parent without attributes, and the variation's attributes are lost. Fixed automatically: rows are reordered so the parent comes before its variations.
Error VARIATION_BEFORE_PARENT
auto-fixed in processed result
5 6 TEE-100-M-B Parent The variation (record #5) comes before its parent (record #10). WooCommerce creates a temporary placeholder parent without attributes, and the variation's attributes are lost. Fixed automatically: rows are reordered so the parent comes before its variations.
Error VARIATION_BEFORE_PARENT
auto-fixed in processed result
6 7 TEE-100-L-W Parent The variation (record #6) comes before its parent (record #10). WooCommerce creates a temporary placeholder parent without attributes, and the variation's attributes are lost. Fixed automatically: rows are reordered so the parent comes before its variations.
Error VARIATION_BEFORE_PARENT
auto-fixed in processed result
7 8 TEE-100-L-B Parent The variation (record #7) comes before its parent (record #10). WooCommerce creates a temporary placeholder parent without attributes, and the variation's attributes are lost. Fixed automatically: rows are reordered so the parent comes before its variations.
Error VARIATION_BEFORE_PARENT
auto-fixed in processed result
8 9 TEE-100-XL-W Parent The variation (record #8) comes before its parent (record #10). WooCommerce creates a temporary placeholder parent without attributes, and the variation's attributes are lost. Fixed automatically: rows are reordered so the parent comes before its variations.
Error VARIATION_BEFORE_PARENT
auto-fixed in processed result
9 10 TEE-100-XL-B Parent The variation (record #9) comes before its parent (record #10). WooCommerce creates a temporary placeholder parent without attributes, and the variation's attributes are lost. Fixed automatically: rows are reordered so the parent comes before its variations.
Error PARENT_WHITESPACE
auto-fixed in processed result
13 17 000210-S-NAV Parent Parent " 000210" has leading or trailing spaces and does not exactly match any SKU. Without the spaces it unambiguously points to record #11 ("000210"). Fixed automatically: the spaces are removed from Parent; the parent SKU is not changed.
Error PARENT_WHITESPACE
auto-fixed in processed result
16 20 000210-L-GRE Parent Parent "000210 " has leading or trailing spaces and does not exactly match any SKU. Without the spaces it unambiguously points to record #11 ("000210"). Fixed automatically: the spaces are removed from Parent; the parent SKU is not changed.
Info UNKNOWN_COLUMN — — — Supplier note The column "Supplier note" is not part of the built-in schema, so WooCommerce does not import it by default. Its values are kept unchanged. If it is a custom field, rename the column to "Meta: your_key" (with a space after the colon) or choose "Import as meta data" on the column mapping screen.

What cannot be checked without your store

Show the 7 things to check in your store
  • SKUs that already exist in the store. If a SKU from the file already exists in the store, the built-in importer skips the row unless "Update existing products" is enabled ("A product with this SKU already exists"). The file alone does not contain this information.
  • Global attribute and term settings. Global attributes (Attribute N global = 1) depend on the attributes and terms configured in the store.
  • How the database compares SKUs. Whether SKU lookups are case- and trailing-space-sensitive depends on the MySQL/MariaDB table collation.
  • Plugin and theme conflicts. Plugins can change how rows are parsed through importer hooks (woocommerce_product_importer_*).
  • Server limits. Upload size, PHP memory and execution time limits decide whether the import runs as one file.
  • Images, categories, tags, shipping and tax classes. Image URL availability and the existence of tax classes are not checked.
  • The column mapping screen. Columns can be remapped manually, or a previously saved mapping can be applied.

For Shopify, run the real Check demo. Shopify Check reports findings and leaves the source unchanged.