I built a small browser-based tool called Catalog Preflight for merchants who are preparing a Shopify product CSV import.
It is meant to catch some of the easy-to-miss CSV problems that can cause products to be skipped, variants to become disconnected, images to go missing, or an update to affect more data than expected.
The current beta checks for things such as:
missing or inconsistent Handles
variant row and SKU problems
obvious Image Src issues
CSV encoding, headers, and field formatting
high-risk row structures that may be skipped or imported incorrectly
The CSV is processed locally in your browser. The file and its product data are not uploaded to a server.
This is an early validation tool, not a Shopify importer. It does not connect to your store, compare the file with your live catalog, test whether a remote image host will allow Shopify to download an image, or guarantee that Shopify will accept every row.
I am looking for a small number of merchants who are already preparing a real Shopify product CSV import. If that describes you, I would appreciate it if you ran the file through the beta before importing and let me know:
Did it find a problem you would otherwise have missed?
Did any warning seem incorrect or unclear?
Were you creating new products or updating existing ones?
You can try it here:
Please do not post or send your CSV. I do not need the file or any product data; feedback about the type of issue is enough.
@EDword — Pre-checking Shopify product CSVs before import saves massive post-import cleanup time, but standard CSV pre-validators often miss “silent image pipeline failure modes” that pass syntax checks.
Three specific image-pipeline blind spots to include in your CSV pre-checker:
Silent WebP Binary Dropping: Standard syntax checkers verify if ‘Image Src’ or ‘Variant Image’ contains a valid HTTP/HTTPS URL string, but they don’t inspect file extension payloads. If URLs point to raw .webp files from supplier CDNs (common with Asian manufacturers), Shopify’s background CSV worker silently skips fetching the image binary without returning an error log. The text attributes pass pre-check, but image slots end up blank on the storefront.
Dynamic Query-String Parameters: Supplier image URLs containing expiring authentication tokens (?auth_key=123...) or dynamic cropping strings pass string validation, but fail HTTP handshakes when Shopify’s worker processes the ingestion queue 10 minutes later.
Variant-Image Coverage in Option Arrays: For multi-variant SKUs (e.g. 1 Color across 4 Sizes), the color image URL MUST be explicitly duplicated across ALL 4 size rows under ‘Variant Image’. Pre-checkers that allow blank cells assuming inheritance cause variant image dissociation on import.
If your workflow identifies WebP or variant-image mapping gaps before publishing, consider normalizing them locally using EasyCatch (a client-side Chrome extension). Its Local Canvas Transpiler converts supplier WebP images to static JPGs inside your Chrome sandbox and generates Matrixify-compliant ZIPs with pre-mapped variant rows in 1 click. 100% Local-First so store catalog data stays completely private.
