Overview

Error 90180 is a common feed processing error that Amazon sellers encounter when uploading product listings through flat files or feeds. This error occurs when the data type you've submitted for a specific attribute doesn't match what Amazon's system expects — for example, entering text into a field that requires a numeric value. Understanding how to diagnose and fix this error can save sellers significant time during bulk listing uploads.

Key Points / What Sellers Need to Know

• Data type mismatch is the root cause — Error 90180 fires when the value you've provided for a product attribute is in the wrong format, such as submitting a text string where Amazon expects a number.
• Decimal and unit formatting matters — Values with incorrect decimal places or improperly formatted units (such as weight or dimensions) will trigger this error even if the underlying number is correct.
• Special characters can cause failures — Hidden formatting, currency symbols, or other special characters embedded in your data can make an otherwise valid value unreadable to Amazon's system.
• The feed processing report identifies the problem — Amazon's feed processing summary report will pinpoint the exact attribute and field causing the error, along with the expected data type.
• Resubmission is required after correction — Once you've fixed the formatting issues, you'll need to resubmit the listing feed for the changes to take effect.

How This Error Occurs

Error 90180 typically surfaces during bulk listing operations when sellers upload inventory files, flat files, or use feed-based integrations to create or update product listings. Amazon's catalog system enforces strict data type requirements for every attribute field. When your feed contains a value like "ten" in a field that expects the integer "10," or includes a measurement like "5.123 lbs" in a field that only accepts two decimal places, the system rejects the entry and returns error 90180. The error message itself will reference the specific attribute name, the value you provided, the type Amazon received, and the type it was expecting — giving you a clear trail to follow when troubleshooting.