How to Fix Amazon Feed Error 95032: Value Range Mismatch
Error 95032 occurs when paired fields such as MinimumPrice and MaximumPrice, or StartDate and EndDate, are out of logical order. The feed‑processing report lists the exact fields (e.g., “MinimumPrice must be ≤ MaximumPrice”). Adding Excel conditional formatting or IF checks before upload prevents the rejection and keeps listings live.
Overview
Amazon returns error code 95032 when a feed contains a pair of related attribute values that are out of logical order—such as a minimum that exceeds its maximum or an end date that precedes its start date. The rejection stops the affected listings from being created or updated, so sellers must correct the mismatch before the feed can be processed.
Key Points
- Paired‑field validation — Amazon checks every attribute that has a logical counterpart (e.g., MinimumWeight vs MaximumWeight) and rejects the row if the first value is larger than the second.
- Date‑range failures — Supplying an EndDate earlier than the StartDate is the most common trigger, especially for promotions, sales events, or warranty periods.
- Numeric‑range errors — Weight, dimension, price‑tier, or quantity thresholds will also cause 95032 when the lower bound is entered higher than the upper bound.
- Exact field names appear in the report — The feed processing report lists the two offending attributes in the message “the value in [Field A] must be less than or equal to the value in [Field B].”
- No policy penalty — The error is purely a data‑validation issue; it does not affect account health but does block the listing until fixed.
- Prevention is a spreadsheet task — Adding conditional formatting or simple IF formulas to your upload template can automatically flag reversed ranges before the feed is submitted.
How to Resolve Error 95032
- Open the processing report — Download the feed‑processing report from Seller Central, locate the row marked with error 95032, and note the two attribute names shown in the message. Example: “MinimumPrice must be less than or equal to MaximumPrice.”
- Cross‑check source data — Pull the original product specification sheet or manufacturer data for the SKU in question and verify the correct lower‑bound and upper‑bound values. Example: The supplier lists a price range of $12.99–$19.99, but the feed shows $22.00 as the minimum and $18.00 as the maximum.
Analysis & Recommendations
Why This Matters
A 95032 rejection stops the affected SKU from being created or updated, delaying time‑sensitive promotions and reducing visibility in search results. Sellers lose potential revenue until the feed is corrected and resubmitted, making rapid detection essential.
Key Takeaways
- Error 95032 is triggered when a lower‑bound attribute (e.g., MinimumPrice) exceeds its upper‑bound (MaximumPrice).
- Date‑range mismatches like EndDate earlier than StartDate are the most common cause of 95032.
- The processing report includes the exact field names in the message “the value in [Field A] must be less than or equal to the value in [Field B]”.
- Applying Excel conditional formatting that highlights rows where StartDate > EndDate or MinWeight > MaxWeight catches the issue before upload.
Recommended Actions
- →In Seller Central, go to Reports > Feed Processing Reports, download the report, locate rows with error 95032 and note the two offending fields.
- →In the upload spreadsheet, insert an IF formula such as =IF(MinWeight>MaxWeight,"ERROR","OK") in a hidden column and filter for "ERROR" to correct ...
- →Resubmit the corrected feed via Inventory > Add Products via Upload and verify the new processing report shows no 95032 errors.
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!