How to Bulk Upload Products to Amazon Seller Central (2026 Guide)

First: are you creating or matching?

Amazon has two fundamentally different jobs that both use uploads:

• Matching an existing ASIN — the product is already in Amazon's catalogue and you're adding your offer (your price, quantity, condition). Minimal data needed: SKU, product ID, price, quantity, condition.
• Creating a new ASIN — the product isn't on Amazon yet and you're building the page: title, bullets, images, brand, all category-required attributes. Much more data, much stricter validation.

Most rejected uploads come from people using a full creation template when they only needed to match an offer. If the ASIN exists, match it — it's faster and can't break anything.

Step 1: Get the right template

1. Seller Central → Catalogue → Add products via upload.
2. Open the Download a spreadsheet tab.
3. Search for your product type. Pick the most specific match — "Home" is not the same template as "Home Storage", and using a too-broad one leaves required attributes missing.
4. Choose your marketplace(s) — a UK file and a European multi-country file are not interchangeable.
5. Download. You get an .xlsm workbook with several tabs.

Templates change. Downloading a fresh one each time you do a big upload avoids the "template version no longer supported" rejection, which is entirely avoidable and extremely annoying.

Understanding the tabs

• Template — where your data goes. Row 1 and 2 are Amazon's headers; your data starts at row 4.
• Data Definitions — what each column means and whether it's required. The single most useful tab and the one everyone ignores.
• Valid Values — the exact accepted strings for dropdown-style fields. Amazon rejects anything not on this list; "Blue" may be valid where "blue" is not.

Step 2: Fill the required columns

Every category differs, but this core set is near-universal:

Leave genuinely optional columns empty rather than guessing. A wrong value fails validation; an empty optional field doesn't.

Step 3: Get product IDs right

This is where most new sellers stall. Amazon validates barcodes against the GS1 database and checks that the number is registered to the brand on the listing.

• Reselling branded goods? Use the manufacturer's EAN/UPC. It's on the packaging.
• Own brand? Buy barcodes from GS1 directly. Cheap barcodes from resale sites are registered to someone else's company prefix and are a leading cause of rejections and later listing removals.
• Handmade or bundle products with no barcode? Apply for a GTIN exemption in Seller Central for your brand + category. Approval lets you list without a product ID.

If you're unclear on how barcodes relate to your internal SKUs, our SKU guide covers the distinction — they are different identifiers doing different jobs, and conflating them causes problems well beyond Amazon.

Step 4: Save and upload without corrupting the file

Two rules that prevent a large share of all failures:

1. Save as "Text (Tab delimited)" (.txt) — not CSV, not XLSX, unless the upload page explicitly asks for the workbook. Amazon's parser expects tab-delimited.
2. Protect your barcodes from your spreadsheet. Excel converts 0501234567890 to a number and drops the leading zero, and may turn long barcodes into scientific notation (5.01235E+12). Format those columns as Text before pasting data in.

Then: Add products via upload → Upload your spreadsheet → choose file → submit. Processing takes anywhere from a minute to some hours depending on file size and queue.

Step 5: Read the processing report properly

Under Monitor upload status, download the processing report for your submission. It gives one row per error with:

• The original row number in your file
• An error code and message
• Whether the row was a warning (accepted with issues) or an error (rejected)

Fix the source spreadsheet, then re-upload only the failed rows. Re-submitting the whole file wastes processing time and can produce confusing duplicate warnings.

Frequent error codes in plain English

• 8541 / product ID not valid — barcode fails GS1 validation or doesn't match the brand.
• 8560 / missing attribute — a category-required field is blank. Check Data Definitions.
• 8008 / not eligible to list — brand gated, category gated, or restricted product. Needs approval, not a file fix.
• 90097 / SKU already exists — duplicate SKU in your account. Change the SKU or use an Update action instead of Create.

Variations (parent/child) without breaking them

Size/colour variations need one parent row and one child row per variant:

• Parent row: parentage = parent, no price, no quantity, no barcode. It exists only to group.
• Child rows: parentage = child, parent_sku pointing at the parent's SKU, relationship_type = variation, plus the variation theme (e.g. SizeColor) and each child's own barcode, price and quantity.

The most common variation failure is a mismatch between the declared variation theme and the attributes actually filled in — declare SizeColor and every child must have both size and colour populated.

After launch: the quantity problem

Bulk upload solves listing creation. It doesn't solve what happens next: those quantities start drifting the moment you sell the same stock anywhere else. If you also sell on eBay, Shopify or your own store, every sale elsewhere makes your Amazon quantity wrong — and Amazon punishes stock-out cancellations hard through your Order Defect Rate.

Re-uploading inventory files on a schedule is the manual answer; real-time sync is the working one. Salync holds one central stock figure and updates Amazon, eBay, Shopify and more within seconds of any sale, so post-launch you stop touching flat files for quantity at all. Free for up to 50 SKUs.