PREFLIGHT CHECK
Check regular/sale prices, weight and dimensions for plain numeric values before WooCommerce import.
🔒 Analysis runs in your browser; the file itself is not sent to BlueprintLab.
| Severity | Row | Column | Issue | Value |
|---|
This unofficial checker covers only rules that can be verified in the browser. Live account settings, remote server state and later service-side validation remain authoritative.
Check regular/sale prices, weight and dimensions for plain numeric values before WooCommerce import.
Type,SKU,Name,Regular price,Sale price,Weight (kg),Length (cm),Width (cm),Height (cm) simple,SKU001,Sample Product,1200,1000,0.5,20,10,5
WooCommerce fields such as Regular price, Sale price, Weight, Length, Width, and Height expect numeric cell values. Currency symbols or unit text such as `¥1200` or `500g` should not be embedded in those cells.
This checker finds the relevant columns and points to cells containing non-numeric text.
Headers such as Weight (kg) or Length (cm) reflect the WooCommerce store’s unit settings. Put `0.5` in Weight (kg), not `0.5 kg`.
When moving a CSV between stores, verify that the destination store uses the same units as the source.
Both values can be perfectly valid numbers, so this is not a parsing error. But a Sale price higher than Regular price is often worth reviewing because it reverses the usual pricing intent.
The checker separates “can WooCommerce parse this?” from a small amount of “does this look intentional?” review.
If an old system exports `20cm` and `10cm`, remove the unit text and align the numeric values with the destination WooCommerce unit settings. Do the same for price fields instead of importing formatted currency strings.
Run a small import first and confirm the displayed price, weight, and dimensions before applying it to the full catalog.