Understanding Listing Error 90235: Date Attribute Cannot Be Set to the Past
Error 90235 blocks a listing when a date attribute such as LaunchDate, SaleStartDate, SaleEndDate, OfferStartDate or ReleaseDate is set earlier than the current UTC date (e.g., 2023‑01‑01 when today is 2024‑07‑13). The check runs on flat‑file uploads, SP‑API feeds and manual edits, rejecting the record or entire batch until the date is corrected.
Overview
Error 90235 appears when a seller tries to set a date‑based attribute on a product listing to a day that has already passed. The validation runs during flat‑file uploads, API feeds, or manual edits, and it can stall a listing’s activation, which matters for time‑sensitive launches and promotions.
Key Points
- Error trigger — The system blocks any attempt to assign a past date to fields that must stay current or future, such as a launch date set to January 1 2023 when today is July 2024.
- Affected workflows — The validation fires across all entry points: bulk flat‑file submissions, SP‑API inventory feeds, and on‑screen edits in Seller Central where a date field is present.
- Typical date attributes — Commonly checked fields include LaunchDate, SaleStartDate, SaleEndDate, OfferStartDate, and ReleaseDate. Each of these must reference today’s date or a later one.
- Root causes — Sellers often copy older templates, reuse exported spreadsheets, or reactivate dormant listings without updating the embedded dates, leading to the past‑date condition.
- Quick fix — Replace the offending date with today’s calendar date or a future date that aligns with the promotion schedule, then resubmit only the affected rows or listings.
How This Error Occurs
- Date validation step — When Amazon receives a listing payload, it scans every date‑type attribute; if it finds a value earlier than the current UTC date, it flags the record and returns error 90235. Example: a spreadsheet row lists “SaleEndDate = 2023‑11‑15” on a submission dated 2024‑03‑01, triggering the error.
- Error message generation — The response includes the exact attribute name, phrased as “Attribute ‘{attribute_name}’ must not be changed to a date in the past.” Example: “Attribute ‘LaunchDate’ must not be changed to a date in the past.”
- Rejection of the payload — Amazon rejects the entire batch or the specific record, preventing the listing from going live until the date is corrected.
Analysis & Recommendations
Why This Matters
A past‑date error can halt an entire bulk upload – for example a 5,000‑SKU batch was rejected because ten rows contained outdated sale dates – delaying product launches, promotions and causing inventory to sit idle. Quick correction is needed to keep sales schedules on track.
Key Takeaways
- Error 90235 fires when any date‑type attribute is earlier than today’s UTC date, such as LaunchDate set to 2023‑01‑01.
- The validation runs across flat‑file submissions, SP‑API inventory feeds, and on‑screen edits in Seller Central.
- A single batch of 5,000 SKUs can be fully rejected because just ten rows contain past dates.
- Fixing requires changing the offending date to today’s date (e.g., 2024‑07‑13) or a future date and resubmitting only those rows.
Recommended Actions
- →In Seller Central, open the error report, find the attribute name (e.g., OfferStartDate) and SKU, then edit the date field to today’s date or a fut...
- →Download the affected rows from the flat file, update the date column (LaunchDate, SaleStartDate, etc.) to a valid date, save, and re‑upload via th...
- →Add a pre‑upload check: create a spreadsheet macro or script that scans all date columns and flags any value older than today before submitting any...
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!