6 export shapes · 9 real files
What your supplier's file does on the way in.
A Magento export and a Wix export break in completely different places, and neither of them breaks where you would look first. These pages describe the shapes we have actually run — what to expect, what goes wrong, and what the engine does about it.
2 files measured
A Shopify export, going back into Shopify
The shape people assume is safe. Two products whose titles slugify to one handle merge into one, and the import reports success.
1 file measured
A WooCommerce export, going into Shopify
Two grammars that disagree about what a variant is. Woo points a child row at a parent SKU; Shopify groups by a handle that repeats.
1 file measured
A Magento export, going into Shopify
A workbook that says it has forty rows and physically contains eight thousand. Most tools read the declaration.
1 file measured
A Wix catalog export, going into Shopify
Row types encoded in a column, and descriptions with line breaks inside them. A line-based parser splits one product into several.
1 file measured
A B2B linesheet, going into Shopify
Six hundred columns, most of them empty, and a header row written for a human buyer rather than for an importer.
3 files measured
An ERP export or a plain price list
Non-Latin headers, a European decimal comma, and identifiers a spreadsheet has already turned into numbers.
Why there are only 6
The same reason there are only fourteen import error pages: a shape earns a page when we have run a real file of that shape through the engine, and not before. A test in our own build cross-checks every figure on these pages against the corpus record it came from, so a page cannot quietly describe a file we never opened.
The alternative is the one everybody else publishes — a page per platform name from a list, describing failures nobody observed. Those pages rank, and they are wrong, and being wrong is the one thing this product cannot afford.
Nothing here quotes a cell. These are real supplier catalogues holding real buying prices, so what we publish is shape and column convention: how many rows, how many columns, what the header set looks like, and what broke.
The corpus behind them
- 21 real supplier files
- 5 to 614 columns wide, six source platforms, Latin and Cyrillic. The engine is re-run against all of them on every change.
- 4 defects they found
- That 140 passing hand-written tests did not. Two of them severe, and both are described on the pages above.
- 9 cited here
- Every figure on a page names the file it was measured on, and the file is listed in our published corpus record.
Or just run the file.
The Pre-Flight Report reads your file and names what will break, whatever shape it arrived in. Free, no account, about a minute.
Check a file free