ImportFixed

More Fixers · Guide — the fixer itself is not open yet

Amazon upload error codes, in plain words

Amazon answers a failed upload with a number. The number is not the explanation — but a handful of numbers cause most of the pain, and those translate cleanly.

Error 8560 — the product is new and the file is too thin

Amazon’s own wording for 8560 is that the SKU “does not match any ASIN” and creating a new one requires attributes your file is missing — the message names them (often the standard product ID, or the product type, or size/colour). In plain words: Amazon has never seen this product, and your row does not carry enough to build its page. Fix: give the row the attributes named in the message — a valid barcode (UPC/EAN from GS1) is the one that unblocks most 8560s.

Error 13013 — you updated a product that does not exist yet

13013 means the SKU in your price or inventory file is not in Amazon’s catalogue, so there was nothing to update. It happens when the product feed failed earlier (often with an 8560 nobody read), or when the SKU has a typo. Fix: create the product first, confirm it exists, then send the price and inventory.

Error 8541 — your data disagrees with Amazon’s page

8541 is a matching conflict: the barcode you sent belongs to a product already in the catalogue, but your title, brand or other identity details do not match the page that owns it. Amazon trusts its existing page. Fix: align your identity fields with the catalogue page, or use a correct, distinct barcode for a genuinely different product.

The classes without one famous number

  • Missing required attribute. The message names the attribute. Add it for that SKU; category templates differ, so the same product can pass in one category and fail in another.
  • Restricted or approval-needed products. Some categories and brands need approval before any file will be accepted. No spreadsheet fix exists — the approval comes first.
  • Variation problems. Parent and child rows must agree on the variation theme (size, colour, or both) and every child needs its parent SKU spelled identically.

Read the report top to bottom. Amazon processes a file in order, and one early failure (a product never created) manufactures later ones (every price row for it fails too). Fix the first error first.

Questions

Where do I see these errors?

In the processing report Amazon gives you after an upload: Inventory → Add Products via Upload, then the upload status and report. The report names the SKU and the error code for each failed row.

My code is not listed here. What do I do?

Read the sentence Amazon prints beside the code before anything else — the codes group into families (matching problems in the 8500s, missing values in the 9000s and 13000s), and the sentence tells you which family you are in. Amazon’s full explanations live inside Seller Central help, behind the error-code lookup.

When the Amazon upload file fixer opens here, it will read a flat file and translate these codes row by row. Until then, the Shopify CSV Fixer is open and free.