Amazon Error 8566: Fix SKU Does Not Match ASIN

Error 8566 stops your flat file upload with a clear message: "The SKU provided does not match the ASIN specified." In plain terms, the SKU you are trying to use is already tied to a different ASIN in Amazon's system, and Amazon will not let you reassign it.

This guide explains why 8566 happens, how to identify the conflicting mapping, and how to fix it. It also covers SKU naming practices that prevent the problem from recurring.

What error 8566 actually means

Every SKU in your Seller Central account is permanently bound to a single ASIN. Once Amazon records that binding, it treats it as fixed. If you submit a flat file row where the SKU points to ASIN B, but Amazon already has that SKU mapped to ASIN A, the row is rejected with error 8566.

This is a hard rejection. Amazon will not process the row at all. The rest of your upload may succeed, but every row containing the conflicting SKU will fail.

Common causes

In practice, 8566 comes down to one of three situations:

• Reusing a SKU from a previous listing. You listed a product months ago under SKU "WIDGET-001", then deleted that listing. Later, you try to use "WIDGET-001" for an entirely different product with a different ASIN. Amazon still holds the original SKU-to-ASIN mapping internally, even though the listing no longer appears in your inventory.
• Typo in the ASIN field. Your SKU is correct, but the ASIN column in your flat file contains a transposed character or a copy-paste error. Amazon looks up the SKU, finds it already points to the real ASIN, and rejects the row because the ASIN you submitted does not match.
• Variation child SKU already in use. You are building a parent-child variation family, and one of the child SKUs is already assigned to a standalone listing or to a different parent. Amazon will not move a SKU from one ASIN to another, even within the same account.

How to find the existing SKU-to-ASIN mapping

Before you can fix the error, you need to know which ASIN your SKU is currently linked to. The fastest way is to pull a Category Listings Report:

1. In Seller Central, go to Inventory, then Inventory Reports.
2. Select "Category Listings Report" (or "All Listings Report" if you want every product type in one file).
3. Request and download the report.
4. Open it in a spreadsheet application and filter the seller-sku column for the SKU that triggered 8566.
5. The asin1 column shows the ASIN that SKU is currently bound to.

If the SKU does not appear in your listings report at all, it may have been deleted but the mapping is still retained by Amazon. In that case, the SKU is effectively unusable for any other ASIN.

Fixing error 8566

Option 1: Use a new SKU

The simplest fix. Replace the conflicting SKU in your flat file with a new, unique SKU that has never been used in your account. Upload the file again. This works immediately and requires no support case.

This is the right choice when you do not need to preserve the original SKU for operational reasons (warehouse labels, ERP mappings, or order management integrations).

Option 2: Delete the old SKU first

If you need that specific SKU freed up, delete the existing listing that holds it:

1. Find the SKU in your Seller Central inventory (or in the listings report you pulled earlier).
2. Delete the listing. You can do this through the Seller Central UI or by submitting a flat file with the "Delete" action for that SKU.
3. Wait. Amazon does not release SKU-to-ASIN mappings instantly. In some cases the mapping clears within 24 hours; in others it can persist for weeks.
4. Resubmit your flat file. If the mapping has cleared, the row will process. If not, you will get 8566 again and will need to either wait longer or use a new SKU.

Because of the unpredictable delay, this option is less reliable than simply choosing a new SKU. Use it only when preserving the exact SKU string matters to your operations.

Option 3: Correct the ASIN

If the problem is a typo in your ASIN field rather than a genuine SKU conflict, the fix is straightforward. Look up the correct ASIN for the product, update the flat file, and resubmit. No waiting, no support case.

Double-check the ASIN character by character. ASINs are ten characters, start with "B0" for most products, and contain only uppercase letters and digits. A single transposed character will trigger 8566.

Why Amazon does not let you reassign SKUs

Amazon treats the SKU-to-ASIN binding as a permanent record for a reason. Order history, FBA shipments, returns, and financial reports all reference the SKU. If sellers could freely reassign SKUs from one product to another, historical records would become ambiguous. A return filed under SKU "WIDGET-001" would no longer clearly indicate which product the customer received.

This is also why deleted SKUs are not immediately available for reuse. Amazon retains the mapping to preserve the integrity of past transactions.

SKU naming conventions that prevent collisions

Good SKU hygiene eliminates most 8566 errors before they happen. A few principles:

• Include the ASIN or a product identifier in the SKU. A pattern like "B0EXAMPLE1-BLK-M" (ASIN + colour + size) makes accidental reuse obvious because the ASIN is right there in the SKU string.
• Never recycle SKUs. Once a SKU has been used, treat it as spent. Even if you delete the listing, create a new SKU for any replacement product.
• Use a consistent prefix per brand or product line. This makes it easy to search your listings report and spot duplicates. For example, "VF-" for one brand and "SH-" for another.
• Avoid generic SKUs. Short codes like "001", "TEST", or "SAMPLE" are easily reused by accident, especially in accounts managed by multiple people.
• Document your scheme. Keep a simple reference that everyone on your team can follow. Inconsistency across team members is the most common source of SKU collisions in multi-user accounts.

Catching SKU conflicts before upload

You can avoid 8566 entirely by checking your flat file against your current listings before submitting it to Amazon. Pull a fresh All Listings Report, compare the SKUs in your upload against the report, and flag any SKU that already appears with a different ASIN.

Our flat file monitor automates this check by tracking your processing reports and surfacing recurring errors, including 8566, so you can fix the root cause rather than re-uploading and hoping for the best.

For a broader view of flat file errors and how they relate to each other, the flat file errors guide covers the most common error codes alongside 8566, including 8541 (catalogue conflict), 8572 (UPC-brand mismatch), and others.