Understanding Error 90175: Future Date Validation in Amazon Listings
On 2026-04-15 Amazon returned error 90175 when a date‑type attribute (e.g., ManufactureDate) was set to the current UTC day or later. The platform only accepts past dates, causing the offending row to be rejected until the date is changed to a prior day such as 2026-04-14.
Overview
On April 15 2026, many sellers encountered Amazon’s validation error 90175 when a date‑type attribute in their product feed was set to the current day or a future date. The platform blocks the submission until the offending date is changed to a past value. Sellers who rely on bulk uploads, the SP‑API, or Seller Central’s listing editor need to recognize and correct this issue to keep listings active.
Key Points
- Trigger condition — The error appears whenever a date field (e.g., manufacture date) equals today’s UTC date or a later date, because Amazon only accepts past dates for those attributes.
- Affected attributes — Commonly impacted fields include ManufactureDate, ReleaseDate, ExpirationDate, and any custom date attribute required by a specific category; the error message always names the exact field.
- Where it shows up — Sellers see the code in flat‑file processing reports, SP‑API feed responses, or the listing‑error dashboard inside Seller Central.
- Typical cause — Using the upload date as a placeholder (e.g., “2026‑04‑15” for a new gadget) or overlooking timezone differences that make a local “yesterday” appear as “today” in Amazon’s UTC system.
- Resolution path — Replace the invalid entry with a confirmed past date (e.g., change 2026‑04‑15 to 2026‑04‑14) or delete the field if it isn’t mandatory for the product’s category.
- Prevention tip — Implement a pre‑submission check that flags any date equal to or later than the current UTC date, ensuring bulk feeds never contain prohibited values.
How Error 90175 Works
- Data submission — When a seller uploads a flat file, sends an SP‑API feed, or edits a listing manually, Amazon’s validation engine scans every column for rule compliance. Example: a seller uploads a CSV containing a Bluetooth speaker with ManufactureDate set to 2026‑04‑15.
- Date rule enforcement — For attributes flagged as “past‑only,” the system compares the supplied value against the current UTC date. If the value is the same day or later, the engine marks the field as invalid.
Analysis & Recommendations
Why This Matters
A single SKU with a future date can halt a batch of 1,200+ products, delaying launches and risking lost sales. Sellers must correct the date or remove the field to resume processing and keep inventory timelines intact.
Key Takeaways
- Error 90175 triggers when any date field equals or exceeds the current UTC date (e.g., 2026-04-15).
- Affected attributes include ManufactureDate, ReleaseDate, ExpirationDate, and custom date fields.
- Only the row with the invalid date is rejected; all other rows in the feed continue processing.
- A pre‑submission check that flags dates >= TODAY() in UTC prevents the error.
Recommended Actions
- →In Seller Central, open the flat‑file or API payload, locate the attribute named in the error (e.g., ManufactureDate), and change the date to a pas...
- →Add a spreadsheet formula (e.g., =IF(A2>=TODAY(),"INVALID","OK")) or script to flag any date >= UTC today before uploading.
- →Update SP‑API integration to run a pre‑flight UTC date validation and abort the request if a future date is detected.
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!