1. Your product CSV
The legacy-format file from BigCommerce's Export, a supplier feed, or your own spreadsheet, saved as CSV.
Choose a file or paste the text, then click Check file.
Result
Products
| Line | SKU or name | Name | SKU rows | Images |
|---|
Safe fixes
The model, and what it leaves out
- Item Type decides the row's job: Product, SKU (one option combination of the product above it), Rule or Image. A SKU row belongs to the Product row above it, and that product must name an Option Set.
- Option values: a SKU row's Product Name lists its options as
[RB]Size=Medium; two SKU rows under one product cannot share a combination. - Product Code/SKU is unique across the store, so a repeat inside the file is an error, and so are SKUs Excel rewrote to scientific notation.
- Plain numbers: Price, Cost Price, Retail Price, Sale Price, weight and size are digits and a decimal point, with no currency symbol, unit or thousands separator. Current Stock Level is a whole number.
- Flags such as Allow Purchases?, Product Visible? and Free Shipping are a capital Y or N; Product Type is P or D.
- Images: Product Image File addresses must be reachable web addresses, with one image marked Y as the thumbnail.
- Barcodes: codes of 8, 12, 13 or 14 digits are checked, because marketplaces and Google Merchant Center reject a wrong check digit.
- Safe fixes change only delimiter, header and Item Type capitals, stray spaces, P/D and Y/N flags, price and weight formatting. It never changes the characters of a name, description, SKU, barcode, stock, category or image address.
- Not checked: that BigCommerce will accept the file today, whether categories, brands and option sets exist, the newer product import template, custom-field syntax, that image URLs are reachable, and anything BigCommerce changes in its importer. Import two or three products first.
Common questions
Why did my BigCommerce product CSV import fail or create the wrong products?
The usual causes are an Item Type that is not Product, SKU, Rule or Image, SKU rows with no Option Set on their product, a repeated Product Code/SKU, prices with a currency symbol or a decimal comma, a blank price, an unquoted comma in Category or Search Keywords that shifts every later cell, image addresses with spaces or local paths, and an Excel save that turned SKUs or barcodes into scientific notation. This tool tests each of them and names the line.
How do I check a BigCommerce product CSV before importing it?
Paste the file or drop it onto this page. It reads the header against the import template, attaches each SKU row to the product above it, and lists every problem with its line number, grouped as errors, warnings and notes. Nothing is uploaded.
Why does BigCommerce reject my SKU rows or create no variants?
A SKU row belongs to the Product row above it, and the product has to name an Option Set. The SKU row's Product Name lists its option values as [RB]Name=Value. A SKU row above its product, a product with no Option Set, an option value with no equals sign, or two SKU rows with the same combination all fail. The tool checks each of them.
Why is my BigCommerce CSV semicolon-separated?
Excel in many European and Latin American locales saves CSV with semicolons because the comma is the decimal separator. The importer expects commas. This tool detects the delimiter and, with Apply safe fixes, rewrites the file with commas.
What does Apply safe fixes change?
Only things with one reasonable reading: the delimiter, header capitalisation, Item Type capitalisation, stray spaces around Item Type, Product ID, SKU, barcode and image addresses, Physical or Digital to P or D, yes/no or true/false to Y or N in the flag columns, decimal commas in weights, and prices like $1,299.00 to 1299.00. It never changes the characters of a name, description, SKU, barcode, stock, category or image address.
Is it safe to put my product catalogue into a web page?
The page runs in your browser, the file is read locally and nothing is uploaded; a test in the code asserts there are no network calls. Your own policies still decide what you may open in a browser.
What does this not check?
Whether BigCommerce will accept the file today, whether categories, brands and option sets already exist in the store, the newer product import template and its variant columns, custom-field syntax, whether image URLs are reachable, and anything BigCommerce changes in its importer. A clean result is not a promise of success: import a few products first.