Overview

Error 99108 appears when a seller’s feed lists a product identifier—such as a UPC, EAN, ISBN, or GTIN—that does not match the identifier Amazon has already linked to the ASIN in the submission. The mismatch stops the row from being processed, delaying the product’s appearance or update on the marketplace. Sellers who rely on bulk uploads need to understand why the error occurs and how to prevent it to keep inventory flowing.

Key Points

• Identifier mismatch — The error triggers when the barcode number in the feed differs from the standard ID Amazon stores for the referenced ASIN, for example submitting UPC 123456789012 for ASIN B07XYZ while Amazon’s catalog shows UPC 987654321098.
• Feed rejection — Any row with this conflict is rejected, meaning the product will not go live or receive the intended update until the data aligns.
• Two correction routes — Sellers can either change the product ID in the file to match Amazon’s record, or replace the ASIN with the one that correctly corresponds to the supplied ID.
• Bulk‑upload vulnerability — A single typo or outdated GTIN in a flat‑file or API batch can halt processing of that row, potentially affecting dozens or hundreds of items in the same submission.
• No health penalty — The error does not affect account health metrics, but it does stall sales opportunities while the feed is corrected.

How Error 99108 Happens

1. Data submission — The seller uploads a file (flat‑file, XML, or JSON) containing ASINs paired with product identifiers.
2. Amazon catalog cross‑check — Amazon’s system retrieves the standard ID linked to each ASIN from its master catalog.
3. Mismatch detection — If the identifier in the seller’s row differs, the system flags the entry as Error 99108 and excludes it from processing.

Example: A vendor uploads a spreadsheet with 200 rows. Row 57 lists ASIN B08ABC123 and UPC 111222333444. Amazon’s catalog shows that ASIN B08ABC123 is tied to UPC 555666777888. Because the numbers do not match, Amazon returns Error 99108 for row 57, while the remaining 199 rows continue to process.