How to Fix Error 99105: ASIN and SKU Mismatch in Amazon Feeds
Error 99105 blocks bulk uploads when a SKU is paired with a UPC/EAN/ASIN that differs from the ASIN Amazon already bound to that SKU. The SKU‑ASIN link is permanent until the SKU is deleted and a 24‑hour purge completes. Fixes include correcting the identifier, deleting the SKU, or waiting 24 hours before re‑assigning it.
Overview
Error 99105 appears when a bulk upload tries to link a seller‑defined SKU to a product identifier that does not match the ASIN Amazon has already associated with that SKU. The mismatch stops the feed from updating the listing, forcing sellers to adjust the identifier or remove the SKU before the next submission. Resolving the error quickly is essential for maintaining smooth bulk‑listing workflows and avoiding delays in inventory or price changes.
Key Points
- Root cause — The feed supplies a UPC, EAN, or ASIN that differs from the ASIN Amazon previously bound to the same SKU.
- Scope of impact — The error can surface in flat‑file uploads, Inventory Loader files, or API‑driven feeds that process many products at once.
- SKU‑ASIN binding rule — Once Amazon maps a SKU to an ASIN, the association cannot be overwritten by simply sending a new product ID; the original link must be cleared first.
- Resolution options — Sellers may (1) correct the product ID, (2) delete the SKU entirely, or (3) delete the SKU, wait 24 hours, then reassign it to a new product.
- No health penalty — The error does not affect account health metrics, but it can stall large‑scale updates and increase manual effort.
How Error 99105 Occurs
- Initial listing creation — When a seller first uploads a product, Amazon reads the supplied identifier (e.g., a UPC) and creates a permanent SKU‑to‑ASIN mapping in its catalog.
- Subsequent feed submission — A later bulk file includes the same SKU but pairs it with a different identifier—perhaps because a spreadsheet row was shifted or an old SKU was repurposed.
- Validation check — Amazon’s intake system compares the incoming identifier with the stored ASIN. If they differ, it rejects the record and returns error 99105.
Example: A seller lists a “Blue Cotton T‑Shirt” using SKU BT001 and UPC 123456789012, which Amazon ties to ASIN B07XYZ. Weeks later, the seller uploads a new file that mistakenly lists SKU BT001 with UPC 987654321098 (the identifier for a “Red Cotton T‑Shirt”). Amazon detects the conflict and blocks the row with error 99105.
Analysis & Recommendations
Why This Matters
When error 99105 appears, the entire feed row is rejected, delaying inventory or price changes for potentially hundreds of items. Although it doesn't affect health metrics, the 24‑hour deletion rule means sellers can lose up to a day of update time if they reuse SKUs incorrectly, impacting sales velocity.
Key Takeaways
- Error 99105 triggers when a SKU's new product ID does not match the ASIN Amazon previously mapped to that SKU.
- SKU‑ASIN bindings are immutable; they can only be cleared by deleting the SKU in Seller Central.
- After deleting a SKU, a 24‑hour wait is required before the same SKU can be reassigned to a different product.
- The error does not impact account health metrics but can stall bulk‑listing workflows.
Recommended Actions
- →In Seller Central, run an Inventory Report, locate each SKU's current ASIN, and verify feed product IDs match before uploading.
- →Delete the mismatched SKU via Inventory > Manage Inventory > Delete, then wait at least 24 hours before re‑uploading the SKU with the new identifier.
- →If the identifier is wrong, edit the feed to replace the UPC/EAN/ASIN with the correct value that matches the existing ASIN, then resubmit the file.
Comments
Join the discussion
Log in or create an account to share your thoughts on this update.
No comments yet. Be the first to share your thoughts!