AMAZON INVENTORY LOADER CHECK · RUNS IN YOUR BROWSER · NOTHING UPLOADED

Why did Amazon reject my inventory file?

Paste or drop your inventory file and get every problem with its line number before you upload: files that are comma-separated instead of tab-delimited, UPCs that lost their leading zero, UPCs and EANs whose check digit is wrong, SKUs Excel turned into 1.23457E+12, prices like $18.00 or 26,50, negative or fractional quantities, wrong add-delete codes and used items with no condition note. Then apply the safe fixes and download a cleaned tab-delimited file.

The file is read in this browser tab and never leaves your device. Independent of Amazon.com, Inc. Column names, codes and limits are read from memory of Amazon's public inventory file documentation; no Seller Central upload was available when this was built.

1. Your inventory file

A price and quantity or inventory loader file saved as text or CSV, or a sheet exported from a repricer or inventory tool.

Choose a file or paste the text, then click Check file.

The rules, and what they leave out

Common questions

Why was my Amazon inventory file rejected?

The usual causes are a file that is comma-separated or semicolon-separated instead of tab-delimited, a UPC that lost its leading zero in Excel, a UPC or EAN whose check digit is wrong, SKUs or product ids that Excel turned into scientific notation, prices with currency symbols or decimal commas, a quantity that is negative or has a decimal, an add-delete value other than a, d or x, and a used item with no condition note. This tool tests each of them and names the line.

How do I check a UPC or EAN before uploading it?

The last digit of a UPC or EAN is a checksum of the others. This tool recomputes it for every row, so a mistyped digit is reported before Amazon rejects the row. It also spots an 11-digit UPC that is a 12-digit one with its leading zero removed, and only offers the fix when the restored number passes the check.

Does Seller Central want a tab-delimited file?

From memory of Amazon's public documentation, inventory files are tab-delimited text. Excel's CSV save produces commas, and its Unicode Text save produces UTF-16. This tool reports either and converts to tabs.

What does Apply safe fixes change?

Only things with one reasonable reading: the delimiter, header spelling, stray spaces, prices like $1,299.00 to 1299.00, a quantity of 5.0 to 5, add-delete and condition-type capitalisation, and an 11-digit UPC to 12 digits when the check digit confirms the restored zero. It never edits a SKU's characters or a note.

Is it safe to put my inventory 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.

What does this not check?

Whether Amazon will accept the file today, category listing files, restricted products and brand approval, and whether a product id matches your item. A clean result is not a promise of success: upload a few rows first.