How to Fix Error 90115: Decimal Place Limits on Product Listings
Error 90115 occurs when numeric values in product feeds exceed Amazon's allowed decimal places. This guide explains the cause, affected attributes, and step-by-step resolution for sellers managing catalog uploads.
Overview
Error 90115 is a common product listing error that Amazon sellers encounter when submitting feed files with numeric values that contain too many decimal places. Whether you're entering prices, weights, or measurements, Amazon enforces strict formatting rules on how precise these numbers can be. Understanding and resolving this error quickly is essential to keeping your listings live and your catalog updates flowing smoothly.
Key Points / What Sellers Need to Know
- Decimal precision is enforced — Amazon's system automatically rejects any numeric attribute value that exceeds the maximum allowed decimal places for that field.
- Prices are limited to two decimal places — A value like $19.999 will trigger this error; it must be rounded to $19.99 or $20.00.
- Weights and measurements have their own limits — Each attribute type has a specific maximum number of decimal places defined in Amazon's product template.
- Feed files are the most common trigger — Sellers using flat file uploads or API-based feed submissions are most likely to encounter this error during bulk catalog updates.
- The fix is straightforward — Correcting the decimal precision in your data and resubmitting the feed resolves the issue in most cases.
Why This Error Occurs
Error 90115 fires when a numeric value in your product feed exceeds the decimal place limit that Amazon has set for that particular attribute. Every product attribute that accepts numeric input has a defined format specification, and the system validates incoming data against these rules during feed processing. For example, if you submit a product weight as 2.4567 pounds but the field only allows two decimal places, your submission will be rejected. This validation exists to maintain data consistency across Amazon's massive catalog and to ensure that pricing, dimensions, and other numeric fields display correctly to customers.
How to Resolve Error 90115
The resolution process starts with identifying which attribute triggered the error. Check your feed processing report for the specific field and value that failed validation. Next, consult the Valid Values tab and the Data Definitions sheet within your product category's flat file template — these documents specify the exact decimal place limits for every numeric attribute. Once you know the correct format, round or truncate your values accordingly. For prices, always use exactly two decimal places. For weights and dimensions, refer to the template specifications for your product category, as these can vary. After correcting the values, save your updated feed file and resubmit it through Seller Central or your preferred API integration.
Analysis & Recommendations
Why This Matters
Decimal formatting errors can silently block bulk listing updates, delaying new products and inventory changes from going live. Sellers managing large catalogs through flat files or API feeds need to understand these validation rules to keep operations running smoothly.
Key Takeaways
- Prices must use exactly two decimal places — no more, no less
- Each product attribute has its own decimal place limit defined in Amazon's category template
- Always consult the Valid Values and Data Definitions sheets in your flat file template before submitting feeds
- Building automated rounding or formatting checks into your workflow prevents this error entirely
Recommended Actions
- →Review your feed processing reports to identify which specific attributes triggered error 90115
- →Download the latest flat file template for your product category and check the decimal place specifications for all numeric fields
- →Add number formatting rules or rounding logic to your spreadsheet templates or feed generation scripts to enforce correct precision before submission
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!