Headers
Map common legacy columns
Recognize fields such as Handle, Body (HTML), Variant SKU, Variant Price, Image Src, and current equivalents, then export normalized columns.
Shopify product import preflight
Fix Shopify CSV problems before the import fails.
RowSift cleans common source headers, trims hidden whitespace, generates URL handles, validates prices and inventory fields, and exports a comma-separated UTF-8 CSV for review.
Common Shopify CSV checks
Shopify imports are strict about headers, encoding, required product data, and related variant fields. RowSift focuses on deterministic checks that can be performed safely before upload.
Products
Title and URL handle review
Flag missing product titles and generate safe lowercase URL handles when a source row needs one.
Variants
Price and inventory validation
Normalize simple price formats, require numeric inventory quantities when tracking is enabled, and check deny/continue inventory policy values.
Why Shopify product CSV imports fail
Invalid or missing headers
The first CSV row has to contain recognized product field names. RowSift trims header whitespace and maps a focused set of common old and current Shopify field names before export.
Illegal quotes or encoding problems
Shopify expects UTF-8 CSV data. RowSift surfaces replacement characters and smart quotes so you can review text that may have been damaged by an editor or encoding conversion.
Variant fields without their dependencies
SKU and other variant updates can depend on Option fields. RowSift warns when SKU exists without both Option1 name and Option1 value so the file can be reviewed before an overwrite import.
Large files
Shopify documents a 15 MB maximum for product CSV imports. RowSift blocks larger Shopify product files in the browser so you can split them before upload.
A safer workflow for catalog imports
Do not treat a successful CSV parse as proof that a store import is safe. Use a small test subset first, review changes, keep a backup, then import the final file.
1
Preflight
Run the supplier or export file through RowSift and review all remaining errors and warnings.
2
Test small
Import a small subset before a large catalog change, especially when updating variant options or handles.
3
Import intentionally
Keep the source backup and only enable overwrite behavior when you understand which existing values will be replaced.