Amazon Error Code Decoder

Why it happens

• You're listing under a brand that isn't in Amazon Brand Registry and you don't have permission to use it
• The brand name doesn't appear (or isn't permanently affixed) on the product/packaging in your images
• Brand on the listing doesn't match the photos exactly (spelling, case, spacing)
• You're using “Generic” incorrectly, or the brand exists in the catalog but isn't tied to you

How to fix it

1. Open the Inventory File / error report and copy the Batch ID next to the 5665 error — you'll need it for the case.
2. Choose your path: with a registered (or pending) trademark, enroll in Amazon Brand Registry — that permanently removes 5665 for your brand. Without one, request permission to use an unregistered brand name.
3. Take real photos (no mockups/renders) showing the brand permanently printed on the product itself and/or packaging — not a sticker or hang-tag.
4. Use the link inside the 5665 message to open the brand authorization application, OR open a case via Help > Get support and attach the images + Batch ID.
5. Make the Brand field match your photos character-for-character (capitalization and spacing), then resubmit once approved.

Copy-paste message for Seller Support

Why it happens

• The product has no brand on it, but you entered a real brand name instead of “Generic”
• You used generic wording Amazon doesn't treat as a valid brand
• You actually want a real brand but haven't been approved for it

How to fix it

1. If the product is genuinely unbranded, recreate the listing via Add a Product and enter exactly “Generic” in Brand Name.
2. Confirm nothing in your images shows a brand/logo that contradicts a Generic listing.
3. If you DO want a real brand, don't use “Generic” — follow the brand-approval link in the error (this becomes the 5665 path).
4. Resubmit after correcting the Brand field.

Copy-paste message for Seller Support

Why it happens

• The Brand Name field was left blank in Add a Product or the flat file
• The brand column was mapped incorrectly in an upload template
• The product is unbranded and needs “Generic” but the field was empty

How to fix it

1. Open the listing/flat file and fill in Brand Name — your approved brand, or “Generic” for a truly unbranded product.
2. If using a flat file, confirm the brand column is mapped correctly and not shifted.
3. Resubmit; if you enter a real brand and then get 5665, follow the brand-approval process for that code.

Copy-paste message for Seller Support

Why it happens

• New ASIN creation for this brand is gated to the brand owner / Brand Registry and approved sellers
• Your Brand Registry account isn't linked to the selling account creating the listing
• You used a UPC/EAN/ASIN/JAN that belongs to a different brand
• Brand name spelling/spacing doesn't match Amazon's records

How to fix it

1. Confirm authorization: if it's your brand, make sure Brand Registry is linked to this selling account and your user role has brand permissions.
2. Check brand spelling, capitalization and spacing match Amazon's records exactly.
3. Verify the product identifier (UPC/EAN) actually belongs to this brand and product — a borrowed/wrong code triggers 5461.
4. If you're an authorized reseller, obtain a Letter of Authorization from the brand owner.
5. Open a case (or follow the application link in the error) requesting permission to create ASINs for the brand, attaching your authorization / Brand Registry proof.

Copy-paste message for Seller Support

Why it happens

• The UPC/EAN isn't a genuine GS1-issued code, or isn't registered to your company in GS1
• The GTIN conflicts with an ASIN already in Amazon's database
• Your GS1-registered company name and Amazon brand name don't match exactly
• Simple data-entry mistake in the identifier

How to fix it

1. At the GS1 “Verified by GS1” lookup, confirm the GTIN is registered and the company/brand name matches your Amazon brand exactly (even “LLC” vs no “LLC” can fail).
2. If you only recently registered the codes with GS1, wait — it can take ~72 hours for Amazon to recognize new GS1 data.
3. Gather your GS1 certificate plus clear photos showing the UPC and brand name on the product/packaging.
4. Open a case requesting to list with your own UPC, attaching the GS1 certificate and (if a reseller) a Letter of Authorization.
5. Once validated, resubmit with the correct GTIN and matching brand name.

Copy-paste message for Seller Support

Why it happens

• Missing or invalid product identifier (UPC/EAN/ISBN), or a non-GS1 code that won't validate
• Required attributes (brand, manufacturer part number, dimensions) are missing
• The brand name doesn't align with the GS1 record tied to the UPC
• The product already exists and should be matched to its ASIN instead of created new

How to fix it

1. Confirm your product identifier is valid and GS1-registered; correct it if missing or wrong.
2. Fill in all required fields — brand, manufacturer part number, product dimensions — so Amazon can create the ASIN.
3. If the product already exists, add your offer to that ASIN rather than creating a new listing.
4. If you sell private-label goods without a barcode, apply for a GTIN exemption, then list using the exemption.
5. If you reached this in error, open a Seller Support case via the contact-us link.

Copy-paste message for Seller Support

Why it happens

• Your product has no GS1 barcode and you haven't been granted a GTIN exemption for that brand + category
• You were approved, but you're listing under a brand or category that doesn't exactly match the approval
• You tried to list within ~30 minutes of approval (the exemption hasn't propagated yet)
• You have the exemption but still lack a separate category-level approval for that product type

How to fix it

1. No barcode? Catalog > Add Products > start a new listing, and at the Product ID step choose “I don't have a Product ID” to request an exemption — or search “Apply for GTIN exemption,” pick the exact category, enter the brand (or “Generic”), and upload 2–9 real product/packaging photos (no mockups, no visible barcodes).
2. After approval, wait at least 30 minutes before listing so the exemption can propagate.
3. List with the brand name and category EXACTLY as in your approval email — any difference in case, spacing, or characters makes Amazon ignore the exemption.
4. If it still errors, check whether the product type also needs a separate category/listing approval and apply for that.
5. If everything matches and it still fails, open a case quoting your exemption approval and the brand + category used.

Copy-paste message for Seller Support

Why it happens

• Product ID has wrong length/format (UPC=12 digits, EAN=13, ISBN=10)
• Product ID isn't a valid GS1 code / fails industry-standard validation
• A required field for the category is missing
• The product ID matches no existing ASIN and a new one wasn't created

How to fix it

1. Verify the product ID length: UPC = 12 digits, EAN = 13 digits, ISBN = 10.
2. Run the code through a UPC/GS1 validation tool to confirm it conforms to standards.
3. Use the correct category template and confirm the Category/Item Type Keyword is right.
4. Fill in all required (bold) fields in the template.
5. If the product ID is correct but new to the catalog, complete all required fields to create a new ASIN, then resubmit.

Copy-paste message for Seller Support

Why it happens

• Editing brand, manufacturer, or UPC/EAN on an existing SKU
• Trying to fix bad data entered when the SKU was created
• Product was rebranded or the manufacturer changed
• The listing was originally created under the wrong SKU

How to fix it

1. Identify exactly which identity attribute (brand, manufacturer, UPC/EAN) you're trying to change.
2. Confirm the correct value and gather supporting docs (brand/GS1 proof).
3. For brand fixes, submit a brand-correction request via Seller Support with documentation.
4. If Amazon won't unlock the attribute, create a NEW listing with a new SKU and the correct identity data.
5. Set the old SKU's quantity to 0 / close it once the new listing is live.

Copy-paste message for Seller Support

Why it happens

• An incorrect or mismatched ASIN was provided as the external product ID
• Submitted attributes conflict with the matched ASIN's key data
• A 'merchant_suggested_asin' value is forcing a bad match
• Wrong identifier copied when matching to an existing listing

How to fix it

1. Switch the external product ID from the ASIN to the correct UPC or EAN and resubmit.
2. Verify the product data (brand, model, key attributes) matches the intended ASIN.
3. If the error persists, remove the 'merchant_suggested_asin' (MSA) field and resubmit.
4. Confirm you're matching to the correct child-level ASIN, not a parent.
5. Re-upload and check the processing report.

Copy-paste message for Seller Support

Why it happens

• Typo or misentry in the ASIN
• ASIN doesn't exist in the catalog (or was deprecated/merged)
• Wrong format (ASINs are 10-character alphanumeric)
• Using an ASIN from a different marketplace

How to fix it

1. Re-check the ASIN for typos; confirm it's a valid 10-character alphanumeric string.
2. Confirm the ASIN exists in the catalog for THIS marketplace.
3. Make sure the ASIN isn't deprecated or merged into another listing.
4. If reselling, verify the correct ASIN with your supplier.
5. Update the listing with the correct ASIN and resubmit.

Copy-paste message for Seller Support

Why it happens

• Your Product ID maps to an existing ASIN and one or more attributes you sent don't match Amazon's accepted values
• You're trying to overwrite core fields (title, brand, manufacturer, product type) that are owned/locked on the detail page
• UPC came from a reseller/non-GS1 source and points to a different product
• A previous contribution to the ASIN conflicts with your current feed

How to fix it

1. Open the live ASIN and compare each attribute against your feed; note exactly which field differs (often Title, Brand, Manufacturer, Product Type, Item Type Keyword).
2. In Seller Central go to Inventory > Manage All Inventory > Search Suppressed and Inactive Listings, open the listing, and use “Accept Amazon's Value” where Amazon's data is correct.
3. If you must change a value because Amazon's is wrong, submit a Partial Update flat file with only SKU, Product Type, Brand, the conflicting attribute, and (if known) the ASIN/Item Type Keyword.
4. If the conflicting value is identical to what Amazon requires (a known glitch that locks editing), open a case with screenshots showing the values match.
5. If your UPC is wrong/hijacked, delete the SKU, wait 24 hours, then relist with a valid GS1 UPC.

Copy-paste message for Seller Support

Why it happens

• Your UPC/EAN or attribute set matches multiple ASINs
• Duplicate or near-duplicate detail pages exist for the same product
• Conflicting identifier data (e.g. one UPC reused across several listings)

How to fix it

1. Identify the exact ASIN you intend to list against by searching your UPC/title in the catalog (Add Products).
2. Submit a Partial Update flat file that includes the specific merchant_suggested_asin (or ASIN / external_product_id) of the correct product plus SKU and Product Type, so Amazon stops guessing.
3. If several duplicate pages exist for one product, open a case to have the duplicates merged into a single ASIN.
4. Re-run your feed and confirm the SKU now attaches to the intended ASIN under Manage All Inventory.

Copy-paste message for Seller Support

Why it happens

• You attempted to add an offer or edit a generic ASIN another seller contributed
• You tried to copy an existing generic detail page into your account
• Generic products aren't allowed to share one detail page across sellers

How to fix it

1. Do not try to appeal 5886/5887 — Amazon does not reverse these; you must create your own listing.
2. Go to Catalog > Add Products > “I'm adding a product not sold on Amazon” and create a brand-new generic listing.
3. Set Brand to “Generic” and supply your own unique identifier (your own UPC/GTIN, or apply for a GTIN exemption).
4. Upload your own images and content so the listing is fully yours.
5. If you instead got 5885 (restricted generic ASIN you haven't contributed to), that one CAN be appealed — open a case with your title, SKU, ASIN, and images proving the item is unbranded.

Copy-paste message for Seller Support

Why it happens

• The UPC/EAN isn't yet verifiable in GS1 / public databases (newly bought codes can take ~30 days to publish)
• The barcode is not a genuine GS1-issued code (resold/recycled UPC)
• Required attributes to create a new ASIN are missing or invalid
• Brand-to-GTIN ownership doesn't line up in Amazon's records

How to fix it

1. Confirm your GTIN is genuinely GS1-issued (check the GS1 “Verified by GS1” / GEPIR lookup and Google the number to see it appears publicly).
2. If newly purchased, allow ~30 days for GS1 to publish it plus time for Amazon to ingest it, then resubmit.
3. Make sure your flat file includes all required attributes for new-ASIN creation (Product Type, Brand, Title, category-required fields).
4. If you're Brand Registered and the code is valid but still rejected, open a case requesting manual verification.
5. Attach your GS1 certificate (showing your company prefix) as proof of ownership.

Copy-paste message for Seller Support

Why it happens

• You entered free text where Amazon expects a value from a fixed list (e.g. Product Type)
• Wrong currency or country code (e.g. “EUR” on a US listing, “Europe” as country of origin)
• Value taken from the wrong category template
• Typo or non-standard formatting in a controlled field

How to fix it

1. Read the error — it names the exact field and the rejected value (e.g. Message/Price/StandardPrice/@currency).
2. Open the correct category flat-file template and go to the “Valid Values” tab to see accepted entries.
3. Replace your value with one of the listed valid values, matching it exactly.
4. Make sure you're using the template that matches your product's category, then re-upload.
5. Confirm the row processed in the upload status report.

Copy-paste message for Seller Support

Why it happens

• A required field (bold in the flat-file template) was left blank
• The value entered isn't an accepted/valid value for that field
• Case-sensitive value typed in the wrong case (valid values are case-sensitive)
• Column headers don't match the current Amazon template

How to fix it

1. Open the processing report and note the SKU plus the exact field name listed as missing/invalid.
2. Download the current category template from Seller Central > Inventory File Templates.
3. In the template's 'Data Definitions' tab, confirm which fields are required (bold headers).
4. In the 'Valid Values' tab, copy the exact accepted value for that field (watch capitalization).
5. Enter the value for the affected SKU, verify headers match the template exactly, and re-upload.

Copy-paste message for Seller Support

Why it happens

• The SKU doesn't exist in your inventory
• The SKU was previously deleted or is inactive
• Typo / mismatch in the SKU value in the upload
• The SKU wasn't included in the file you intended to update

How to fix it

1. Double-check the SKU spelling against Manage Inventory for any typo or extra space.
2. In Manage Inventory, confirm whether the SKU exists and its status (active/inactive/deleted).
3. If it never existed, submit it as a NEW listing with full required data (not an update).
4. If it was deleted/inactive, relist or reactivate it before sending updates.
5. Resubmit the corrected file and confirm sync between your tool and Amazon.

Copy-paste message for Seller Support

Why it happens

• Attempting to change ConditionType on a SKU with active inventory
• The submitted condition conflicts with the existing catalog condition
• Trying to switch condition without first removing the live offer
• Inconsistent condition values between uploads

How to fix it

1. First match the ConditionType in your file to your last submission so it stops conflicting.
2. Set the quantity to 0 and submit to remove the active offer.
3. After the offer clears, update the ConditionType to the desired value.
4. Correct the quantity back to the real stock level.
5. Resubmit and confirm the new condition in Manage Inventory.

Copy-paste message for Seller Support

Why it happens

• Attempting to update/reactivate a SKU that was previously deleted
• Relisting without the proper re-creation process after deletion
• The SKU still maps to a removed catalog record
• Re-uploading an old SKU value that Amazon retired

How to fix it

1. Stop trying to edit the deleted SKU directly.
2. Create a fresh listing for the product using a NEW, unique SKU.
3. Populate all required product data on the new SKU and upload it.
4. Confirm the new SKU goes live in Manage Inventory.
5. If you specifically need the original SKU restored, open a Seller Support case.

Copy-paste message for Seller Support

Why it happens

• Feed attempts to send a new item_classification for an existing SKU
• The attribute is immutable once the SKU is created
• Listing was originally classified incorrectly
• Template/category change pushed a conflicting classification

How to fix it

1. Remove any item_classification value/change from your feed for that SKU.
2. Re-upload the corrected file without touching item_classification.
3. If the product genuinely needs a different classification, create a new listing under a new SKU.
4. Add data-validation in your feed process to avoid sending immutable fields.
5. If reclassification of the existing SKU is essential, open a Seller Support case.

Copy-paste message for Seller Support

Why it happens

• Attempting to edit a protected attribute (e.g. customer_return_policy)
• You're not an authorized selling partner for that attribute/brand
• Amazon locks certain attributes for compliance/consistency
• A bulk file is pushing a value into a protected field

How to fix it

1. Identify the protected attribute named in the error (e.g. customer_return_policy).
2. Remove that attribute from your upload so you're not attempting to change it.
3. Re-upload the file without the protected field.
4. If you legitimately need to set it, confirm whether you're an authorized seller/brand owner for that attribute.
5. If authorized but still blocked, open a case requesting the update with justification.

Copy-paste message for Seller Support

Why it happens

• Item Form contradicts the Unit Count Type (e.g. powder + fluid ounces)
• Wrong dropdown option selected for form or unit
• Copied attributes that don't fit this product
• Liquid measured by weight or solid measured by volume

How to fix it

1. Determine the product's true physical form (powder, liquid, capsule, etc.).
2. Set 'Item Form' to the matching value.
3. Set 'Unit Count Type' to a compatible unit (Ounce/Gram for powder, Fl Oz for liquid).
4. Cross-check against a comparable competitor listing or the spec sheet.
5. Choose values from the template dropdowns (don't free-type) and resubmit.

Copy-paste message for Seller Support

Why it happens

• Condition value is misspelled or non-standard
• Using a value Amazon doesn't recognize for the field
• Wrong case/format for the condition string
• Free-typed condition instead of an approved option

How to fix it

1. Replace the ConditionType with an Amazon-accepted value (e.g. New, Refurbished, UsedLikeNew) appropriate to your category.
2. Match the exact spelling/case Amazon expects.
3. Confirm your account/category is approved to sell that condition (Used/Refurbished gating).
4. Resubmit the file and check the processing report.

Copy-paste message for Seller Support

Why it happens

• The department (or another required attribute) column is empty
• You used an outdated or wrong category template that omits the field
• A required attribute for that product type wasn't mapped from your data source

How to fix it

1. Download your Processing Report (Monitor Upload Status) to see which SKU and field triggered 90001.
2. Download the current category template and open Data Definitions to confirm required fields.
3. Fill in the 'department' (or named) field with a valid value from the Valid Values tab.
4. Re-check every other required field in the same row, then re-upload.

Copy-paste message for Seller Support

Why it happens

• Unsupported/non-standard characters in titles, bullets or description
• Wrong file encoding so special/accented characters get corrupted
• Copy-paste from Word/Docs bringing in 'smart quotes' or hidden control characters

How to fix it

1. Open the Processing Report and note the line/SKU and the flagged character position.
2. Remove or replace the invalid character in that field (retype rather than paste).
3. Save the file as UTF-8 so special characters are encoded correctly.
4. Re-upload; since it's a warning the offer may already be live, but cleaning it prevents garbled text.

Copy-paste message for Seller Support

Why it happens

• The whole file was saved in the wrong character encoding (not UTF-8)
• Large amounts of pasted text carried hidden/non-standard characters
• A database export used a different code page than Amazon expects

How to fix it

1. Re-save your source file explicitly as UTF-8 (Excel: 'CSV UTF-8'; text editor: encoding UTF-8).
2. Strip non-printable/control characters and replace smart quotes, em dashes and accented characters from copy-paste.
3. Re-upload and open the Processing Report to confirm the warning is gone.
4. Validate encoding before each upload so rows aren't silently dropped.

Copy-paste message for Seller Support

Why it happens

• Quantity contains non-numeric characters, decimals or a negative number
• Quantity sent alongside a fulfillment setting that conflicts with it
• The SKU is FBA but a merchant-fulfilled quantity was supplied (or vice versa)

How to fix it

1. In the Processing Report, locate the SKU and look at the inventory/quantity column.
2. Make sure quantity is a whole number with no symbols, spaces or decimals.
3. Confirm the fulfillment channel matches the data (don't push a merchant quantity to an FBA SKU).
4. Correct the conflicting field and re-upload, then verify the count in Manage Inventory.

Copy-paste message for Seller Support

Why it happens

• The required attribute (e.g. target_gender) is blank
• An outdated template that doesn't include the now-required field
• The field exists but the value isn't on Amazon's accepted list

How to fix it

1. Open the Processing Report and note the SKU and exact attribute named.
2. Download the latest category template; for target_gender use valid values such as Male, Female, Unisex, Boys or Girls.
3. Enter the value in the correct column (required fields are often highlighted).
4. Re-upload and confirm the SKU clears.

Copy-paste message for Seller Support

Why it happens

• Description copied from a website/another channel that uses HTML
• Tags like <br>, <p>, <table> or escaped codes present in the text
• A feed/integration didn't strip HTML before sending the description

How to fix it

1. Identify the flagged SKU in the Processing Report.
2. Remove all HTML tags and escaped HTML codes, keeping plain text only.
3. If you need line breaks, use Amazon's allowed methods rather than raw HTML.
4. Re-upload and confirm the description saves and displays correctly.

Copy-paste message for Seller Support

Why it happens

• Title longer than the category limit (commonly 50-200 characters)
• Keyword stuffing or details that belong in bullets crammed into the title
• Duplicated brand/size text inflating the count

How to fix it

1. Note the SKU and the attribute (usually item_name) flagged.
2. Check the maximum character count for that attribute in Data Definitions.
3. Shorten the title to fit, leading with brand + core product and moving extra details to bullets.
4. Re-upload and confirm the title is accepted.

Copy-paste message for Seller Support

Why it happens

• A category-required field such as Brand or Manufacturer is blank
• Using an old template that no longer matches current required fields
• Data wasn't mapped from your source into the required column

How to fix it

1. Read the 99001 message; it states the exact required field (e.g. Brand).
2. Download the latest category template and check Data Definitions for required attributes.
3. Populate the named field(s) with valid values from the Valid Values tab.
4. Re-upload only after every mandatory attribute is filled, then confirm the SKU processes.

Copy-paste message for Seller Support

Why it happens

• HTML tags or escaped HTML codes in the description/title
• Carriage return, line break or tab characters embedded in the text
• Text pasted from another source carrying disallowed control characters

How to fix it

1. Identify the SKU and field flagged by 99038.
2. Remove all HTML tags/escape codes and any tabs or line breaks (spaces are allowed, returns aren't).
3. Re-type the cleaned text in plain form and confirm it matches accepted values.
4. Re-upload and confirm the field now saves.

Copy-paste message for Seller Support

Why it happens

• The specific attribute named in the message is blank for that SKU
• Required field wasn't mapped from your data feed
• Template missing a field that is now required for the product type

How to fix it

1. Read the 99040/99041 message; it names the exact empty attribute.
2. Look up that attribute's accepted values in the template's Valid Values tab.
3. Enter a valid value in the correct column for the flagged SKU.
4. Re-upload and confirm the SKU clears.

Copy-paste message for Seller Support

Why it happens

• The item_type field is blank in your file
• You used a generic template without setting the product-type keyword
• Data source didn't map a value into item_type

How to fix it

1. Find the flagged SKU in the Processing Report.
2. Use the Product Classifier, or the category Browse Tree Guide, to find the correct item_type.
3. Enter that exact item_type keyword in the row.
4. Re-upload and confirm the product is classified and accepted.

Copy-paste message for Seller Support

Why it happens

• item_type contains a typo or an outdated keyword
• A made-up or guessed product-type value was used
• The keyword belongs to a different category than the template

How to fix it

1. Identify the SKU flagged with 99043.
2. Use the Product Classifier or Browse Tree Guide to look up the exact valid item_type.
3. Replace the invalid value with the correct keyword (copy it exactly).
4. Re-upload and confirm the listing is accepted.

Copy-paste message for Seller Support

Why it happens

• Listing a product with an item_type from a different category than the template
• Using a generic/inventory-loader file for a product that needs a category-specific template
• Wrong template downloaded for the product type

How to fix it

1. Find the SKU flagged with 99044.
2. Use the Product Classifier / Browse Tree Guide to confirm both the correct item_type AND the correct Inventory File for the product.
3. Move the SKU into the matching category template, or change item_type to one valid for the template.
4. Re-upload using the correct template and confirm acceptance.

Copy-paste message for Seller Support

Why it happens

• No image file actually resides at the URL provided
• The URL is an HTML redirect instead of a direct path to the image
• The host server was unavailable or timed out when Amazon tried to fetch it

How to fix it

1. Paste the image URL into a browser; if no image appears, replace it with a valid direct URL.
2. If it loads, check the address bar; if it differs from your URL, your link is a redirect — use the final direct URL.
3. Ensure the image host is publicly accessible and stable (no login, no hotlink protection).
4. Re-upload the feed with the corrected, direct image URL and confirm the image attaches.

Copy-paste message for Seller Support

Why it happens

• Image resolution is below the category's minimum pixel requirement
• A thumbnail or compressed image was supplied instead of a full-size one
• Image was downscaled before hosting

How to fix it

1. Check the minimum image size for your category (Amazon recommends at least 1000 px on the longest side to enable zoom).
2. Replace the image with a higher-resolution version meeting the pixel minimum named in the error.
3. Host the larger image at a direct, public URL.
4. Re-upload the feed with the new image URL and confirm it's accepted.

Copy-paste message for Seller Support

Why it happens

• Missing or non-compliant main image, title, bullets, or description
• Missing a required category attribute (e.g. color, size, type)
• Price set too high or too low against Amazon's reference price
• Restricted keyword or prohibited claim in the listing text

How to fix it

1. In Manage All Inventory, click the 'Search Suppressed and Inactive Listings' tab (or Fix Your Products).
2. Open each suppressed SKU and read the exact reason in the 'Issue Description' column.
3. Supply the missing field: compliant main image (pure white, 1000+ px), title under 200 characters, 1-5 bullets, a description, and any missing attribute like color or size.
4. Remove banned words / unverifiable claims ('best seller', 'FDA approved', 'cure').
5. Click Save and finish. Suppression usually clears within a few hours to 24 hours once the data passes.

Copy-paste message for Seller Support

Why it happens

• Title exceeds 200 characters (or the category cap)
• Prohibited special characters such as ! $ ? _ { } ^ unless part of the brand
• A word repeated more than twice, or promotional/claim words in the title
• Title doesn't follow the category's required structure

How to fix it

1. Rewrite the title to under 200 characters (aim 80-150 for mobile).
2. Remove banned special characters; keep only hyphens, colons and standard brackets unless a symbol is part of your brand.
3. Don't repeat any single word more than twice; strip promo terms like 'best', 'sale', 'free shipping'.
4. Lead with Brand + core product + key attribute so it reads naturally.
5. Save; if Amazon locked/auto-edited the title, submit the corrected version and open a case if it doesn't update.

Copy-paste message for Seller Support

Why it happens

• Background is not pure white (RGB 255,255,255) — off-white, grey or textured fails
• Product fills less than 85% of the frame
• Main image contains text, logos, watermarks, props, or inset images
• Image is below 1000 px on the longest side, or shows packaging/multiple items not allowed as MAIN

How to fix it

1. Edit the main image to a true pure-white (255,255,255) background with no shadows bleeding to the edges.
2. Crop so the actual product fills 85% or more of the frame.
3. Remove all text, logos, watermarks, badges, props and inset images from the MAIN slot.
4. Export at 1000+ px (1600+ recommended) on the longest side so zoom works.
5. Replace the MAIN image in Manage Inventory > Edit > Images; suppression typically clears within hours.

Copy-paste message for Seller Support

Why it happens

• No bullet points (key product features) populated
• No product description, or it duplicates the title/bullets (which Amazon strips)
• Bullets contain promotional language, pricing, or shipping claims
• Content exceeds field limits (255 chars per bullet, 2000 chars description)

How to fix it

1. Add up to five factual bullets, each leading with a real feature/benefit, max 255 chars, no promo/price/shipping language.
2. Add a description up to 2000 chars that doesn't just repeat the title or bullets.
3. Remove restricted words, excessive symbols and unverifiable claims from all content fields.
4. Brand-registered sellers can add A+ Content, but the standard fields must still be filled.
5. Save via Manage Inventory; check the Listing Quality Dashboard to confirm the alert cleared.

Copy-paste message for Seller Support

Why it happens

• A category-required attribute (color, size, material, quantity) is empty
• The value submitted isn't valid for that category
• Attribute conflicts with the variation theme for parent/child listings
• Listing was created with a partial or wrong-category template

How to fix it

1. In Manage All Inventory, use the Listing Quality Dashboard (Improve Listing Quality) to see which attribute is missing.
2. Click the alert on the SKU and complete the required attribute using a value from the category's Valid Values list.
3. For variations, make sure the attribute matches the variation theme and parent/child share the same theme.
4. If many SKUs are affected, fill the required columns in the category flat file and re-upload.
5. Save and confirm the incomplete-listing alert clears.

Copy-paste message for Seller Support

Why it happens

• Incomplete listing: missing attributes Amazon wants added
• Restricted-claim or compliance language detected in content
• Image or content quality below Amazon's threshold
• Listing at risk of suppression if left unaddressed

How to fix it

1. Go to Manage All Inventory > Listing Quality Dashboard (or Inventory > Improve Listing Quality).
2. Filter by recommendation type and sort by sales / page views to fix highest-impact listings first.
3. For each alert, add the recommended attribute or fix the flagged content/image.
4. Resolve any 'restricted claim' alerts by removing the offending wording.
5. Re-check after 24 hours to confirm alerts cleared and the listing is no longer at suppression risk.

Copy-paste message for Seller Support

Why it happens

• Product policy / compliance violation on the ASIN (restricted product, claims, safety)
• Suspected IP or copyright issue, or inaccurate product information
• Catalog/data quality problem or duplicate-ASIN merge
• A temporary, regional system removal or review

How to fix it

1. Check Performance Notifications and Account Health > Product Policy Compliance for the exact reason and any 'Submit Appeal' button.
2. If it's a policy violation, fix the root cause (remove the offending claim, supply compliance docs, correct the data).
3. Submit an appeal/Plan of Action with root cause, corrective action, and preventive measures.
4. If removed in error or by a catalog glitch, open a case with the ASIN and evidence the listing is accurate and compliant.
5. Allow ~24-48 hours after approval for the page to be reinstated.

Copy-paste message for Seller Support

Why it happens

• The variation theme (e.g. SizeColor) or required theme attributes are missing on parent or child
• Parent SKU has a Product ID set (parents must NOT have a UPC/identifier)
• Child SKU is already linked to a different parent
• Parent and child don't share the same variation theme

How to fix it

1. For each CHILD: set the parent SKU (parentage = child), relationship type = Variation, the variation theme, and every theme attribute (e.g. Color Name, Size Name).
2. For the PARENT: leave Product ID blank, set parentage = parent, set the same variation theme, leave price/quantity blank.
3. Confirm parent and child use the exact same variation theme valid for that category.
4. If a child is already attached elsewhere, x-delete the old relationship first (see error 8032), wait for processing, then resubmit.
5. Re-upload via the category flat file or the Variation Wizard (Manage Inventory > Add a Variation) and verify the family built.

Copy-paste message for Seller Support

Why it happens

• The child SKU is still linked to its original/old parent
• You re-uploaded a variation file without removing the previous relationship
• The same child was accidentally placed under two parents

How to fix it

1. Decide which relationship to remove. To detach one child, submit an Update/Delete (x-delete on the parentage field) for that child SKU; to dissolve the whole family, x-delete the parent SKU.
2. Wait for the feed to finish (allow up to 24–48 hours) and confirm in the Variation Wizard that the child is no longer linked.
3. Submit a new variation file assigning the child to the intended parent with the correct theme and theme attributes.
4. Verify the child now sits under the new parent in Manage All Inventory.

Copy-paste message for Seller Support

Why it happens

• The theme isn't supported for that category (each category allows specific themes)
• Typo or wrong format in the variation_theme value
• Parent and children use mismatched themes
• The theme was deprecated/retired by Amazon

How to fix it

1. Download the current flat-file template for your exact category and open the “Valid Values” / Data Definitions tab to see allowed variation themes.
2. Pick a supported theme and enter it identically on the parent and every child (watch casing/typos).
3. If the theme was deprecated, delete the parent ASIN, remove parentage from children, create a new parent with a currently valid theme, then reattach.
4. Re-upload and confirm the family builds without error.

Copy-paste message for Seller Support

Why it happens

• Brand (or another family-level attribute) differs between parent and children
• Minor inconsistencies: “RED” vs “Red”, “colour” vs “color”, extra spaces/punctuation
• A genuinely unrelated SKU was placed in the family
• Different feeds populated the attribute differently over time

How to fix it

1. From the error detail, identify the attribute and the differing values across SKUs (the message usually names it, e.g. brand).
2. Pick the single correct value and apply it identically to the parent and ALL children — exact spelling, spacing, capitalization.
3. Submit a Partial Update flat file with SKU, Product Type, and the corrected attribute for every SKU in the family.
4. If one SKU truly doesn't belong (different brand/product), remove it from the family instead of forcing consistency.
5. Reprocess and confirm the family is intact.

Copy-paste message for Seller Support

Why it happens

• Typo or mismatch in the Parent SKU value on child rows
• The parent row was never created, or failed with its own error
• The referenced SKU wasn't set with Parentage = 'parent'
• A value was put in the Parent SKU column for a row that is itself the parent

How to fix it

1. In your flat file, confirm the parent row has Parentage = 'parent' and Relationship Type blank on that row.
2. Confirm every child row's 'Parent SKU' exactly matches the parent's SKU (no typos/spaces).
3. Make sure the parent row has NO value in its own Parent SKU column.
4. Check earlier reports for any error that blocked the parent from being created and fix it first.
5. Upload the parent first, let it create, then upload the children.

Copy-paste message for Seller Support

Why it happens

• Parent SKU is missing or set up incorrectly
• Child attributes (size, color, etc.) are inconsistent or incomplete
• Relationship type isn't set to parent-child
• Variation theme isn't supported for that category

How to fix it

1. Check Amazon's supported variation themes for your exact category.
2. Confirm the parent SKU exists, has Parentage = 'parent', and is used only to group children.
3. Ensure every child has complete, consistent variation attributes matching the theme.
4. Set Relationship Type correctly on child rows (e.g. 'variation').
5. Fix typos in SKUs/attributes and resubmit via flat file.

Copy-paste message for Seller Support

Why it happens

• An incorrect ASIN was provided as the external product ID
• The product ID points to a parent ASIN instead of the specific child
• Parentage is set to 'child' but the matched ASIN is a parent
• Wrong identifier copied when matching to an existing listing

How to fix it

1. Re-submit the SKU using a child-level identifier (the specific UPC/EAN for that variant) instead of the parent ASIN.
2. Or paste the correct matching child ASIN as the external product ID.
3. If you intend this SKU to be the parent, change Parentage to 'parent' and resubmit.
4. If switching parentage is rejected, delete the SKU and recreate it with the correct Parentage.
5. Confirm parents map to parent ASINs and children map to child ASINs before re-uploading.

Copy-paste message for Seller Support

Why it happens

• Inconsistent parentage data entered across marketplaces
• A sync/update changed the role in one marketplace
• Manual listing mistakes assigned the SKU different roles
• Cross-marketplace tools pushed conflicting Parentage values

How to fix it

1. Decide the single correct role for the SKU: parent OR child.
2. Check the parent-child setup for that SKU in each affected marketplace.
3. Identify the marketplace(s) where the parentage is wrong.
4. Resubmit the SKU with the SAME 'Parentage' value in every marketplace.
5. If a SKU is truly meant to differ, use distinct SKUs per role instead of reusing one.

Copy-paste message for Seller Support

Why it happens

• The brand is gated/Brand Registry protected and you're not authorized
• You're not associated with the brand owner
• New ASIN/variation creation for this brand is restricted to authorized sellers
• Brand requires approval before relationship creation

How to fix it

1. Confirm whether the brand is in Brand Registry and whether you're authorized to create listings for it.
2. If an equivalent listing exists, add your offer to the existing ASIN instead of creating a new variation.
3. If you're the brand owner/authorized, ensure your account is linked to the brand in Brand Registry.
4. If you have permission, ask the brand owner to add you as an authorized seller/contributor.
5. Open a case to get the specific reason and required authorization for this brand.

Copy-paste message for Seller Support

Why it happens

• The color/color_name field is blank for the SKU
• Product is in a category (apparel, home, accessories) where color is mandatory
• Color is needed as a variation attribute but wasn't provided on the child

How to fix it

1. Identify the SKU flagged with 90220 in the Processing Report.
2. Confirm in Data Definitions that color is required for this product type.
3. Add a valid color value (and color_map if requested); for variations, supply it on each child.
4. Re-upload and verify the SKU clears.

Copy-paste message for Seller Support

Why it happens

• Merging unrelated products to consolidate reviews or ratings
• Calling something a 'size' or 'color' when the real difference is scent, bundle quantity, or a different product
• Adding a new or poorly-rated item as a child of a popular listing to gain its visibility
• Using variations to bypass brand gating or to launch deceptively

How to fix it

1. Split out any children that aren't genuine variations into their own standalone listings immediately.
2. Keep only true variations under the parent — items identical except for an approved attribute (size, color, count, flavor where allowed).
3. Correct any mislabeled variation themes so the attribute reflects the actual difference.
4. If you received a warning, submit an appeal/Plan of Action: root cause, the corrections made, and preventive process.
5. Audit remaining parent listings to ensure no other non-compliant relationships exist.

Copy-paste message for Seller Support

Why it happens

• Your price is well above the item's historical/market range (high pricing error)
• Your price is far below recent prices, tripping the low-price guardrail
• No Minimum/Maximum price set, so Amazon has no boundaries to validate against
• Legitimate edge cases (collectible/scarce items) the algorithm reads as overpriced

How to fix it

1. Go to Seller Central > Pricing > Pricing Health (or Fix Price Alerts) to see the flagged listings.
2. Double-check the price isn't a typo; correct it if it is.
3. Set a Minimum and Maximum price on the SKU so your intended price falls inside the range — this is the step that usually makes reactivation stick (Manage All Inventory Min/Max columns, or the price alerts page).
4. Click “Reactivate” / confirm the price to tell Amazon it isn't a mistake.
5. If it deactivates again within minutes, make a small price tweak and/or open a case to manually confirm the price (escalate to a supervisor if needed).
6. For a genuinely high-value/collectible item, explain the scarcity in the case so support can clear the guardrail.

Copy-paste message for Seller Support

Why it happens

• Standard Price submitted as 0 or 0.00 (blank/zero price)
• A required numeric field like shipping weight left at 0
• Decimal/format issue that resolved to a value under the 0.01 floor
• Mapping error from a feed tool that zeroed out the price

How to fix it

1. Locate the field named in the error (e.g. Message/Price/StandardPrice) and the offending value (e.g. 0.00).
2. Enter a valid price of at least 0.01 (in practice your real selling price) and ensure other numeric fields like shipping weight are above 0.
3. Use a plain decimal point and no currency symbol in the price field.
4. Re-upload and confirm the SKU is now active with the correct price.
5. If a feed/repricer zeroed the price, fix the mapping so it never sends 0.

Copy-paste message for Seller Support

Why it happens

• Price set above the category's allowed ceiling
• Extra digit / decimal error inflating the price
• Repricer or feed pushed a price beyond the limit
• Currency or unit mismatch making the value look too large

How to fix it

1. Check the price in the error against a sane retail value and correct any typo (a misplaced decimal is the usual culprit).
2. Lower the Standard Price to within Amazon's allowed range for the category and re-upload.
3. If your legitimately high price is blocked, also set a Maximum price under Pricing so Amazon's guardrails recognize it.
4. If the genuine market price truly exceeds Amazon's ceiling, open a case to request a higher price cap for that ASIN.
5. Confirm the listing goes active after the price is accepted.

Copy-paste message for Seller Support

Why it happens

• Wrong decimal separator for the marketplace (comma vs period)
• Currency symbol, thousands separator or letters mixed into the number
• A price/weight field in a format the category doesn't accept

How to fix it

1. From the Processing Report, find the SKU and the numeric field flagged.
2. Open Data Definitions to confirm the required number format for that marketplace.
3. Re-enter the value as a plain number with the correct decimal mark and no currency symbol or thousands separator.
4. Re-upload and confirm the value is accepted.

Copy-paste message for Seller Support

Why it happens

• Sale price provided without sale_from_date and sale_end_date (or vice versa)
• Date format is wrong (e.g. DD/MM/YYYY instead of the required format)
• product_id given without product_id_type, or parentage without variation theme

How to fix it

1. Find the flagged SKU and identify which grouped fields are involved.
2. Populate every field in that conditional group (e.g. all three sale fields) with valid values.
3. Confirm dates use Amazon's accepted format and paired fields like product_id/product_id_type are both present.
4. Re-upload and verify the record is accepted.

Copy-paste message for Seller Support

Why it happens

• The SKU is still Merchant-Fulfilled, not converted to FBA
• The SKU/listing is missing or has no FNSKU
• Catalog data is out of sync with the API after a recent change
• The item is in a category that must be labeled (grocery, health/beauty, media) and isn't

How to fix it

1. Open the listing and switch the offer to “Fulfilled by Amazon” (Convert to FBA).
2. Wait several minutes for Amazon to generate the FNSKU, then run Get FNSKU / Print Labels.
3. Confirm the SKU exactly matches the active listing — fix any typo and resave.
4. If you just made changes, wait up to 24 hours for catalog/API sync before retrying.
5. If it still fails after 24 hours, open a Seller Support case.

Copy-paste message for Seller Support

Why it happens

• Product may contain liquids, sprays, batteries, flammables, or chemicals
• Dangerous Goods questionnaire hasn't been completed
• Safety Data Sheet (SDS) is missing or doesn't match listing attributes
• Common for cosmetics, cleaners, supplements, electronics with batteries

How to fix it

1. Go to Seller Central > Inventory > Manage All Inventory and find the ASIN/SKU.
2. Open the Manage Dangerous Goods Classification tool (or click “Provide Dangerous Goods Information”).
3. Complete the Dangerous Goods questionnaire honestly (liquids, batteries, flammables, ingredients).
4. If requested, upload a Safety Data Sheet (SDS) that matches your listing's weight, dimensions, and ingredients.
5. Submit and wait — many clear in a few hours; SDS-based reviews typically take 3–5 business days.
6. Don't create the inbound shipment until the classification shows cleared.

Copy-paste message for Seller Support

Why it happens

• Product is consumable/topical (supplements, food, cosmetics) or a cleaner Amazon classifies as expirable
• Expiration date wasn't entered during shipment step 1
• Listing isn't flagged as expirable, or the date format is wrong
• Remaining shelf life is under Amazon's minimum (typically must exceed ~105 days at receipt)

How to fix it

1. In the shipment workflow, go back to Step 1 and enter the expiration date for each flagged SKU.
2. Use the accepted format (MM-DD-YYYY or MM-YYYY) and print it on the unit label in human-readable text.
3. Make sure the listing is marked expirable (Product Details or Safety & Compliance / Excel template).
4. Confirm remaining shelf life is greater than ~105 days — Amazon won't accept short-dated stock.
5. Regenerate the FNSKU labels and resubmit the shipment.

Copy-paste message for Seller Support

Why it happens

• Product can melt/deteriorate above ~155°F (chocolate, gummies, wax-based items, some supplements)
• Amazon FCs aren't temperature-controlled for standard inventory
• Seasonal block runs roughly April 15 through mid-October each year
• Amazon won't take liability for products arriving melted

How to fix it

1. Send meltable inventory only in the open window — in 2025, FBA shipment creation reopened Sept 22, 2025 and order fulfillment resumed Oct 13, 2025.
2. Before the spring cutoff (around April 15), draw down or remove meltable stock from FCs to avoid disposal.
3. Check and set automated removal settings so SKUs don't default to disposal/liquidation.
4. During the blocked window, fulfill meltables via FBM (Merchant-Fulfilled), which has no seasonal restriction.
5. Confirm your ASIN's meltable classification in Seller Central if you believe it's miscategorized.

Copy-paste message for Seller Support

Why it happens

• Restock limits are capped per storage type (and applied at ASIN level in 2025)
• Capacity is calculated in cubic feet from projected sales (~5 months) and history
• A low IPI score reduces your storage limit
• Too much slow-moving or excess inventory already at FCs

How to fix it

1. Check Inventory > Inventory Planning > Capacity Monitor / Restock Limits for your current limit and usage.
2. Cancel redundant or stale open/working shipments to free up your limit.
3. Reduce on-hand stock via removal orders or liquidation of slow movers.
4. Improve your IPI (sell-through, fix stranded inventory, reduce aged stock) to lift storage limits over time.
5. For temporary extra space (Prime Day/Q4), reserve it through Capacity Manager — note you pay for reserved space whether used or not.

Copy-paste message for Seller Support

Why it happens

• FNSKU label on the unit doesn't match the product inside
• Case-pack units weren't individually labeled (only the outer case was)
• Warehouse staff scanned similar-looking cartons under one FNSKU
• Labels printed from the wrong SKU or an old listing

How to fix it

1. Label every individual unit with the correct FNSKU — including each unit inside case packs, not just the outer box.
2. Reprint FNSKU labels from the exact SKU in the active shipment, and verify the barcode matches the product.
3. Keep proof: shipment ID, item-label PDF, box content, carrier tracking/photos.
4. If units were received under a wrong FNSKU, file a case with that evidence and request reconciliation/reimbursement.
5. Escalate via the Reconcile tab on the shipment if quantities received don't match what you sent.

Copy-paste message for Seller Support

Why it happens

• Cubiscan measures the item as it arrives — air in poly bags or shifted packaging reads larger
• Soft/bagged items commonly measure 0.5–2 inches bigger than the seller's listed dims
• Listing dimensions/weight are outdated or were estimated
• A single re-measure can bump the product across a size-tier threshold

How to fix it

1. Compare your listed package dimensions/weight against Amazon's measured values (FBA fee preview / Manage Inventory).
2. Re-measure and re-weigh the packaged unit accurately and update the listing if your data was wrong.
3. Open a case requesting a Cubiscan remeasurement (allowed up to twice per 60 days per SKU).
4. If the remeasure confirms you're right, request reimbursement of overcharged FBA fees — you have 90 days from the date the fee was charged.
5. Attach photos of the packaged item next to a ruler/scale as evidence.

Copy-paste message for Seller Support

Why it happens

• The listing was closed, deleted, or suppressed, detaching it from the FBA inventory
• A pricing error or policy issue made the ASIN inactive
• A competitor or catalog change broke the ASIN-to-inventory link
• Missing details or a compliance hold deactivated the offer

How to fix it

1. Go to Manage FBA Inventory (or Fix Stranded Inventory) to see stranded SKUs and the reason for each.
2. For a closed listing, relist/reactivate the offer; for a deleted listing, recreate the SKU matching the ASIN.
3. If suppressed for price, set a reasonable min/max price; if for content/compliance, fix the underlying issue.
4. If you can't relist, create a removal/disposal order before Amazon auto-disposes (after ~30 days).
5. Confirm the units move back to 'fulfillable' once the listing is active.

Copy-paste message for Seller Support

Why it happens

• The category is restricted (e.g. Grocery, Topicals, Supplements, Toys at Q4, Automotive)
• The brand is brand-gated and requires authorization
• Your account metrics or selling history don't yet meet the bar for that category
• Amazon wants to verify product authenticity and your supply chain

How to fix it

1. Go to Seller Central > Catalog > Add Products and search the ASIN/UPC.
2. Click “Show limitations” (older UI: “Listing limitations apply”) to see the exact restriction.
3. Click “Apply to sell” / “Request Approval” to open the application — some categories auto-approve with no documents.
4. If documents are requested, upload invoices from an authorized distributor (dated within 180 days), a Letter of Authorization if branded, product/packaging photos, and any compliance certificates.
5. Submit during business hours and monitor your Case Log; decisions typically take 24 hours to 7 days.
6. If there's no “Apply to sell” button at all, Amazon isn't accepting new sellers in that category right now — sourcing from the brand and getting an LOA is usually the only path.

Copy-paste message for Seller Support

Why it happens

• Product is in a gated/restricted category or sub-category
• Brand requires approval (brand gating)
• The condition you're listing (e.g. Used, Collectible) is restricted for that ASIN
• Amazon is controlling who can sell to protect authenticity

How to fix it

1. In Catalog > Add Products, search the ASIN and click “Show limitations” (formerly “Listing limitations apply”).
2. Read the specific reason shown (category approval, brand approval, or condition restriction).
3. Click “Apply to sell” / “Request Approval” and complete the questionnaire.
4. Attach the exact documents requested — usually authorized-distributor invoices within 180 days, plus LOA/compliance docs if prompted.
5. Submit and track the decision in your Case Log.

Copy-paste message for Seller Support

Why it happens

• Supplier can't be verified (no website/phone, or not a recognized distributor)
• Your name/address on the invoice doesn't match your Seller Central account exactly
• Invoice is older than the accepted window (commonly within 180 days; some teams want 30–90)
• Quantity too low, or it's a retail receipt rather than a B2B wholesale invoice

How to fix it

1. Get a true B2B invoice from an authorized distributor or the brand — not a retail receipt or marketplace order.
2. Confirm the invoice shows the supplier's full legal name, physical address, phone, and website.
3. Make sure YOUR business name and address match your Seller Central registration character-for-character.
4. Buy enough units (commonly 10+ per product) and ensure the invoice is recent (within 180 days, ideally under 90).
5. Add a Letter of Authorization from the brand/manufacturer if you source directly.
6. Re-submit through the same approval case — don't spam new applications with the same rejected docs.

Copy-paste message for Seller Support

Why it happens

• ASIN/brand restricted to approved sellers
• Category gating applies to the product
• Account doesn't meet the listing criteria for this item

How to fix it

1. Search the ASIN in Catalog > Add Products and click “Show limitations”.
2. Click “Apply to sell” to start the approval application.
3. Upload the requested invoices/authorization/compliance documents.
4. Submit and monitor the case for the decision.

Copy-paste message for Seller Support

Why it happens

• Category is gated and your account lacks approval
• Product type maps to a restricted category
• Approval application not yet completed for that category

How to fix it

1. Go to Seller Central > Catalog > Add a Product.
2. Search the product and click “Listing limitations apply” / “Show limitations”.
3. Complete the category approval application and attach required documents.
4. Resubmit your product data after approval is granted.

Copy-paste message for Seller Support

Why it happens

• The product or category requires Amazon approval before listing
• Item is gated due to counterfeit risk, safety, or high complaint rate
• Product was recalled by the manufacturer
• Your account isn't yet approved to sell this specific item

How to fix it

1. In Seller Central, go to Catalog > Add a Product and search for the item.
2. Click the 'Listing Limitations Apply' / 'Show Limitations' link next to the item.
3. Click 'Request Approval' and complete the application (upload invoices/docs if requested).
4. Track status under Add a Product > 'Manage your selling applications'.
5. Once approved, re-upload the SKU. If no approval path appears, open a case to learn why it's restricted.

Copy-paste message for Seller Support

Why it happens

• Listing implies it kills/repels/controls pests or germs ('kills mosquitoes', 'antibacterial') without EPA registration
• Product is a pesticide device making efficacy claims it can't legally make
• Disinfectant/sanitizer claims without required registration
• Even non-pesticide goods caught by the keyword scanner (e.g. 'anti-mosquito')

How to fix it

1. Read the listing as the scanner does and remove every pest-control / germ-killing claim from title, bullets, description, and images.
2. If your product is genuinely an EPA-registered pesticide, add the EPA registration number and required marking.
3. If it was a false flag (no pesticide claims), prepare a brief explanation plus the product's labeling/spec sheet.
4. Appeal via Account Health > Product Policy Compliance with the corrected listing and/or documentation.
5. Re-submit, confirm reinstatement, and keep claims off the listing going forward.

Copy-paste message for Seller Support

Why it happens

• Item is on Amazon's restricted/prohibited list for your marketplace
• Selling a restricted item without the required approval/permit
• Listing makes claims or has attributes that push it into a restricted category
• Repeated restricted-product violations triggering Code of Conduct action

How to fix it

1. Immediately close or delete all affected restricted-product listings so they're no longer active.
2. Read the Restricted Products policy for the category to confirm whether the item is prohibited or just needs approval.
3. If approval is possible, apply through the proper program with required documentation/permits; if prohibited, don't relist.
4. Submit a single holistic appeal/Plan of Action covering all removed ASINs.
5. Audit your catalog for any other restricted items before they're flagged.

Copy-paste message for Seller Support

Why it happens

• Section 3 is the umbrella Amazon cites for many serious issues (suspected fraud, policy abuse, linked accounts, repeated violations)
• The notice usually names the specific policy violated, but the wording can feel vague
• Often triggered automatically with limited human review
• Funds are commonly held for a 90-day settlement period after deactivation

How to fix it

1. Read the deactivation notice in Performance Notifications and identify the EXACT policy/reason cited — do not guess.
2. Build a Plan of Action (POA) in three parts: root cause, immediate corrective actions, and long-term preventive measures (facts, not apologies).
3. Gather supporting evidence (invoices, supplier letters, IDs, photos) proving the specific issue is resolved.
4. Go to Account Health, click “Submit appeal” next to the deactivation, attach your POA and documents.
5. If denied, do NOT spam re-appeals — each weak appeal hurts you; revise the POA to address the precise gap before resubmitting.

Copy-paste message for Seller Support

Why it happens

• Unresolved policy violations, suspected IP infringement, or product-condition complaints accumulating on Account Health
• Performance metrics (ODR, Late Shipment, etc.) breaching targets
• A single “critical” violation can drop AHR to zero and trigger deactivation within ~72 hours if unresolved
• 2025–2026 enforcement is more proactive — more issues flagged automatically

How to fix it

1. Open Account Health and list every flagged violation pulling your score down.
2. For each item, click “Appeal” (or resolve it) and supply the requested corrective action or documentation.
3. Where a POA is requested, submit the 3-part format (root cause, corrective action, preventive measures) with supporting invoices/photos.
4. Resolve issues within the grace period shown (often 72 hours for critical items) — don't wait.
5. Re-check the page in 24–48 hours to confirm the violation cleared and the score recovered.

Copy-paste message for Seller Support

Why it happens

• ODR combines three signals: negative feedback, A-to-z Guarantee claims, and service chargebacks
• Calculated over a rolling 60-day window, so a bad stretch lingers
• Spikes in returns/claims (often seasonal or a single bad SKU) push it over 1%
• Buy Box eligibility also requires ODR below 1%

How to fix it

1. In Account Health, open the ODR breakdown and identify which component (feedback, A-to-z, chargebacks) is driving it.
2. Address open A-to-z claims promptly and resolve buyer issues before they escalate.
3. Pull problem ASINs or fix the underlying cause (item quality, packaging, shipping speed).
4. Request removal of eligible improper negative feedback via the feedback tools.
5. If Amazon requests action or deactivates the account, click “Submit appeal” with a POA documenting cause and corrective/preventive steps.

Copy-paste message for Seller Support

Why it happens

• Orders not confirmed as shipped by the expected ship date over a 10-day and 30-day window
• Handling time set too short for your real fulfillment speed
• Confirming shipment late (even if the package actually went out on time)
• Applies to seller-fulfilled (FBM) orders, not FBA

How to fix it

1. Open Account Health and review which orders were counted late.
2. Increase your handling time to realistic levels for each SKU.
3. Confirm shipment in Seller Central at the moment you dispatch, with valid tracking.
4. Use carriers/integrations that auto-confirm and upload tracking to avoid manual lag.
5. Keep LSR under 4% (target under 2%); the metric recovers as the late-order window rolls forward.

Copy-paste message for Seller Support

Why it happens

• Tracking numbers missing, invalid, or not from a recognized/integrated carrier
• Measured per category over a rolling 30-day window
• Using untracked shipping methods on tracked-required orders
• Manually keyed tracking the carrier can't confirm

How to fix it

1. Identify the affected category and which orders lacked valid tracking in Account Health.
2. Ship every seller-fulfilled order with a trackable service from a recognized carrier.
3. Enter the tracking number and select the correct carrier exactly so Amazon can validate it.
4. Use a carrier integration / Buy Shipping so valid tracking uploads automatically.
5. If listings were deactivated, fix the process then submit an appeal for category reinstatement.

Copy-paste message for Seller Support

Why it happens

• Name/address on documents don't exactly match your Seller Central profile
• Low-resolution, cropped, black-and-white, or screenshot images instead of full original documents
• Expired ID or a document older than allowed (bank statements typically must be under 180 days)
• Amazon's notice often says “we can't verify the documents” without a specific reason

How to fix it

1. Make every detail (legal name, address) on your documents match your Seller Central profile exactly.
2. Re-upload full-page, color, high-resolution scans/PDFs of original documents — no crops or photos of a screen.
3. Use a currently valid, signed photo ID and a bank statement/document within the required date window.
4. Submit through the verification workflow; re-upload corrected files rather than the same rejected ones.
5. If repeatedly rejected with no reason, open a case and ask Seller Support to specify exactly which document and field failed.

Copy-paste message for Seller Support

Why it happens

• Name/address on the bill doesn't match the registered Seller Central address
• Bill is older than 90 days or the provider type isn't accepted (internet bills are often rejected for address)
• Document is cropped, blurry, or a partial screenshot
• No utility bill exists in the business's name at that address

How to fix it

1. Provide a recent (within 90 days) bill for an accepted utility — gas, electricity, water, mobile/fixed phone — in the registered name and address.
2. Upload the complete document in color and high resolution so name, address, and date are clearly visible.
3. If no utility bill is in your name, substitute an accepted alternative such as a bank statement or government-issued document showing the same address.
4. Ensure the address matches your Seller Central profile character-for-character (update the profile first if needed).
5. Resubmit through the verification workflow; open a case if Amazon won't state the rejection reason.

Copy-paste message for Seller Support

Why it happens

• Standard step in new-seller registration and many re-verifications
• Document images alone were insufficient or flagged
• Amazon needs to match a live person to the submitted ID
• Common after address/identity checks during onboarding

How to fix it

1. Book the appointment (instant or scheduled 2–7 business days out) from the verification prompt in Seller Central.
2. Have the ORIGINAL documents physically on hand: valid signed photo ID and any requested business/bank document (bank statement under ~180 days).
3. Use a device with a working front camera/mic — iOS via Safari, all others via Chrome — in a quiet, well-lit space.
4. On the call, show both sides of each document clearly when asked; answer questions about your business directly.
5. Wait up to ~3 business days for the result email; if it fails, review which document the agent flagged and rebook.

Copy-paste message for Seller Support

Why it happens

• Shared identifiers: IP address, device, bank account, address, name, or other data tied to another account
• Operating from a shared space, shared 3PL, or a relative's/colleague's setup
• A connected account was suspended, so Amazon deactivates all linked ones as a precaution
• Multiple accounts without an approved legitimate business reason

How to fix it

1. Determine which account Amazon believes you're linked to (the notice or your own audit of shared identifiers).
2. If the link is mistaken, gather evidence your operation is independent: separate business license, tax ID, bank account, address, and product lines.
3. If you have a legitimate need for multiple accounts, document the business justification and any approval.
4. Write a POA explaining the source of the perceived link and how your accounts operate independently.
5. Submit the appeal via Account Health with all supporting documents; expect a high bar and avoid weak repeat appeals.

Copy-paste message for Seller Support

Why it happens

• Indicators suggest you're not established in the marketplace country for VAT
• VAT number doesn't match your legal business name in Seller Central
• VAT ID expired, invalid, or not issued by the applicable tax authority
• Failure to respond to a VAT/establishment verification request

How to fix it

1. In Settings > Account Info (or the Performance Notification link), find the VAT/establishment verification request.
2. Confirm the VAT number registered exactly matches your legal business name; correct any mismatch.
3. Upload the requested documents (VAT certificate / proof of registration / establishment evidence) before the deadline (often 60 days).
4. Use a VAT number issued by the correct tax authority for that marketplace.
5. Submit and monitor notifications — once establishment is confirmed, held disbursements are usually released within ~24 hours.

Copy-paste message for Seller Support

Why it happens

• Routine 'Verify your bank account information' request
• You added or changed the deposit/charge method (triggers a security hold)
• Bank statement on file is missing required elements or is too old
• Mismatch between account holder name and your Seller Central legal name

How to fix it

1. Go to Settings > Account Info > Payment Information > Deposit Methods > Manage Deposit Methods, find the account and click Verify.
2. Upload a bank statement showing the bank logo, account holder's name, and account number, dated within 180 days (full scan/photo, not a screenshot; you may redact transactions).
3. Make sure the account holder name matches your Seller Central legal entity name.
4. If you just changed bank details, expect a multi-day security hold before transfers resume — this is normal.
5. Submit and monitor Performance Notifications; disbursements resume once verification passes.

Copy-paste message for Seller Support

Why it happens

• Amazon can't verify the product came from an authorized/verifiable supplier
• Invoices missing required fields (supplier business name, full address, contact, exact SKUs, quantities, dates)
• Retail receipts, marketplace (e.g. eBay) receipts, or altered/incomplete documents are typically rejected
• Investigators may phone the supplier — unanswered or generic voicemail can sink the appeal

How to fix it

1. Pull genuine supplier invoices covering the requested period (commonly the last 365 days) that match the exact ASIN/SKU and quantities sold.
2. Confirm each invoice shows the supplier's business name, full physical address, working phone/email, product details, quantities, and prices.
3. Use only verifiable, authorized suppliers — avoid retail/marketplace receipts; verify the supplier will answer Amazon's call.
4. Write a POA: root cause (sourcing/documentation gap), corrective action, and preventive sourcing controls.
5. Submit the appeal with invoices and any authorization letters via Account Health for the affected ASINs.

Copy-paste message for Seller Support

Why it happens

• Returned/commingled units resold without inspection
• Damaged or worn outer packaging (item can be new but the box isn't)
• Inadequate quality-control checks before shipping
• Supplier sent sub-new or open-box stock

How to fix it

1. Investigate the real cause (commingled returns, packaging damage, QC gap) — do NOT just blame the buyer.
2. Write a POA focused on CONDITION control: segregate returns, inspect every unit, add tamper-evident seals, retrain staff.
3. Attach evidence: inspection photos, updated SOPs, and training materials.
4. For FBA, consider removing/relabeling affected inventory and stop commingling (use labeled stock).
5. Submit the appeal via Account Health addressing condition (not sourcing), and request listing/account reinstatement.

Copy-paste message for Seller Support

Why it happens

• Missing/invalid UN 38.3 test summary or Safety Data Sheet (SDS)
• Battery-safety questionnaire not completed, or answers incomplete/conflicting (required on FBM battery listings since July 28, 2025)
• Documents have wrong model, missing signatures/lab identity, missing sections, or are expired/generic templates
• Enforcement deadline of Dec 31, 2025, with enforcement from Jan 1, 2026

How to fix it

1. Complete the battery-safety compliance questions accurately when creating/editing the listing.
2. Obtain a current, product-specific UN 38.3 test summary and SDS from the manufacturer/lab.
3. Verify the documents show the correct model, all required sections, lab identity, and signatures — not a generic template.
4. Upload the documents through the listing's compliance / “Manage Your Compliance” workflow.
5. If still blocked, open a case referencing the exact ASIN and the specific document Amazon is requesting.

Copy-paste message for Seller Support

Why it happens

• No CPC on file for a product intended for children 12 and under
• CPC not backed by testing from a CPSC-recognized (accredited) laboratory
• Certificate missing required elements (product identity, each applicable safety rule, importer info, records contact)
• Amazon has intensified checks on CPC authenticity; falsified/incomplete certificates risk removal or suspension

How to fix it

1. Have the product tested by a CPSC-recognized lab for every applicable children's safety rule.
2. Issue a CPC that identifies the product, lists each applicable rule, names the importer/manufacturer, and gives the records-contact details.
3. Attach the supporting test reports and required labeling information.
4. Upload the CPC and test reports through the product's compliance workflow / Manage Your Compliance.
5. If removed, submit an appeal with the complete, lab-backed CPC and any additional documentation Amazon requests.

Copy-paste message for Seller Support

Why it happens

• No EU Responsible Person appointed (mandatory for non-EU sellers selling to EU consumers since Dec 13, 2024)
• Missing safety information, warnings, manufacturer details, or required labeling
• Applies to virtually all non-food consumer products sold in the EU
• Non-compliant listings are removed/deactivated by Amazon

How to fix it

1. Appoint an EU-based Responsible Person for your products (a person/entity established in the EU).
2. Add the Responsible Person's name and contact details, plus manufacturer info, to your listings and product/labeling.
3. Provide the required safety documentation, warnings, and images for each product.
4. Enter this information in the GPSR/compliance fields in Seller Central (it appears on the detail page within ~24 hours).
5. If listings were deactivated, complete the compliance fields then request reinstatement.

Copy-paste message for Seller Support

Why it happens

• A brand/rights holder submitted an infringement notice via Amazon's Report a Violation tool
• Genuine authenticity issue, OR a mistaken/abusive complaint against legitimate product
• Copyright issues in images/text, or trademark use the rights owner disputes
• Counterfeit flag where Amazon couldn't confirm the goods are genuine

How to fix it

1. Read the notice to see the complaint type (counterfeit vs trademark vs copyright) and the complainant/ASIN.
2. If the product is genuine, gather proof: authorized-supplier invoices, authorization/licensing letters, and (if enrolled) Transparency/Brand Registry evidence.
3. The strongest resolution is a retraction — contact the complainant and ask them to withdraw the complaint to Amazon.
4. If the complaint is valid, remove the infringing element and write a POA addressing root cause and prevention.
5. Submit your appeal (with invoices/authorization or the retraction) through Account Health for the affected ASIN.

Copy-paste message for Seller Support

Why it happens

• Orders shipped in another retailer's packaging or with their invoice/packing slip
• Buying from another online store that ships directly to your customer
• Not being identified as the seller of record or not handling returns/customer service
• Late shipments or quality complaints from an uncontrolled third-party supplier

How to fix it

1. Stop sourcing from retail sites that ship in their own branding; switch to a wholesale/manufacturer supplier who drop-ships under YOUR brand.
2. Ensure all packing slips, invoices and packaging show only your business as seller of record.
3. Take full ownership of returns, refunds and customer service for every order.
4. Gather proof: a supplier agreement showing they ship under your name, plus fulfillment records.
5. Submit a Plan of Action with root cause, the corrective change of supplier/process, and preventive controls.

Copy-paste message for Seller Support

Why it happens

• Using search-find-buy, 'super URLs', two-step URLs, funnels, or treasure-hunt schemes
• Placing or paying for non-authentic orders to fake demand
• Click farms adding products to cart to trigger badges or rank
• Making sales-rank claims (e.g. '#1 best seller') in titles or descriptions

How to fix it

1. Immediately stop any third-party rank/launch service, search-find-buy campaign, or URL-funnel scheme and cancel related contracts.
2. Remove any sales-rank or '#1 best seller' claims from your listings.
3. Identify the root cause (e.g. an agency that ran search-find-buy) and document when it started and ended.
4. Submit an appeal/Plan of Action: root cause, corrective action, and preventive measures (only compliant promotions going forward).
5. Keep evidence (invoices, cancellation emails) showing the activity has stopped.

Copy-paste message for Seller Support

Why it happens

• Offering refunds, discounts, free products, or gift cards in exchange for a review
• Reviews from family, friends, employees, or your own related accounts
• Product inserts that incentivize or steer to positive ratings
• Asking buyers to revise or remove a negative review

How to fix it

1. Stop all incentivized-review activity: remove any insert offering rewards for reviews and end any review services.
2. Switch to compliant methods only: Amazon's 'Request a Review' button, Vine, or neutral follow-ups that don't ask for positive reviews.
3. Identify the root cause (insert card, agency, family reviews) and document removal.
4. Submit a Plan of Action: root cause, corrective action (inserts pulled, service cancelled), preventive measures.
5. Don't try to delete legitimate negative reviews; focus the appeal on demonstrating you understand the policy.

Copy-paste message for Seller Support