Report retention policy is changing
Effective May 30 2024 Amazon will add a fixed retention schedule to every report generated via the Reports API. The reportDocument now returns a createdAt and an expiresAt timestamp, and files are automatically deleted after the type‑specific window (e.g., daily sales summary ≈ 3 days, monthly inventory ≈ 30 days). Sellers must change download cadence and archive data before expiration.
Overview
Starting May 30 2024, Amazon will enforce a fixed retention schedule for every report file produced through the Reports API. Each report type will now have a predetermined lifespan after which Amazon automatically deletes the file, making it unavailable for download. Sellers who depend on regular data extracts—such as inventory snapshots, price feeds, or fulfillment performance metrics—must revise their download cadence and archival strategy to prevent loss of historical information.
Key Points
- Effective date — The new retention rules become active on May 30 2024, so any report generated on or after that day follows the defined expiration timeline.
- Type‑specific windows — Amazon assigns a distinct retention period to each report category; for example, a daily sales summary may disappear after 3 days, while a monthly inventory report could remain accessible for up to 30 days.
- Metadata exposure — The
reportDocumentobject now returns both acreatedAttimestamp and anexpiresAttimestamp, allowing sellers to see exactly how long a file will be retained. - No per‑report alerts — Amazon does not send individual notifications when a specific report is about to expire; the only source of this information is the documentation of report‑type values.
- Download deadline — If a seller attempts to fetch a report after its
expiresAtmoment, the API responds with aResourceNotFoundException, forcing the seller to request a fresh copy. - Automation impact — Scripts that previously assumed indefinite file availability will start failing once the expiration passes, requiring updates to error‑handling and scheduling logic.
How Report Retention Works
- Submit a report request — The seller invokes the
CreateReportendpoint with a desired report type, such asGET_FBA_INVENTORY_DATA. Amazon queues the request and returns a uniquereportId.
Analysis & Recommendations
Why This Matters
If a script tries to download a report after its expiresAt timestamp, the API returns ResourceNotFoundException, causing data gaps and failed KPI pipelines. With retention windows as short as 3 days, sellers need immediate backups to avoid losing sales or inventory metrics needed for reporting and decision‑making.
Key Takeaways
- Retention policy starts on May 30 2024 for all Reports API files.
- reportDocument now includes expiresAt, enabling visibility of each report's lifespan.
- Daily sales summary reports may disappear after 3 days; monthly inventory reports can stay up to 30 days.
- Downloading after expiresAt triggers ResourceNotFoundException, forcing a new CreateReport request.
Recommended Actions
- →Update your download scripts (e.g., in Seller Central > Developer Central > SP‑API code repo) to read the expiresAt field and alert when less than ...
- →Add a step in the script to copy the streamed file to a secure location (e.g., S3 bucket or on‑prem server) immediately after GetReportDocument suc...
- →Create a cron job in your scheduler (e.g., AWS EventBridge or Linux crontab) that re‑issues CreateReport for short‑lived report types each day befo...
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!