Overview

On September 25 2024 Amazon will discontinue the LISTINGS_ITEM_ISSUES_CHANGE notification payload version 1.0 for the Selling Partner API. Sellers who still depend on that format must transition to the newer 2023‑12‑13 version, or they will stop receiving essential compliance alerts that protect product visibility.

Key Points

• Deprecation deadline — After 25 September 2024 the 1.0 payload will no longer be sent; any system that only understands the old schema will receive empty bodies or HTTP 400 errors.
• New payload identifier — The replacement is labeled LISTINGS_ITEM_ISSUES_CHANGE 2023‑12‑13 and uses the same endpoint URL but requires a different JSON structure.
• Stricter validation — The 2023‑12‑13 version enforces tighter rules, rejecting notifications that contain unknown issue codes or malformed attribute values, whereas the old version would silently ignore such problems.
• Extra data fields — Two new properties—resolutionDeadline and policyReferenceId—are now included, giving sellers a concrete deadline and a direct link to the relevant policy.
• Breaking backward compatibility — Unlike version 1.0, the new schema does not tolerate unexpected fields; any mismatch triggers a 400 Bad Request, forcing developers to update parsers immediately.
• Suggested migration window — Amazon advises starting the migration at least 60 days before the cut‑off, allowing time to test the new format against existing pipelines and avoid service gaps.

How the Migration Works

1. Obtain the updated schema — Download the 2023‑12‑13 JSON schema from the SP‑API documentation and line‑by‑line compare it with the 1.0 definition. For instance, a notification that previously only carried issueCode and description will now also contain resolutionDeadline.
2. Adapt your webhook listener — Revise the code that ingests notifications so it can map the new fields into your internal data model. If your database table previously had columns and , add (date type) and (string) and modify the INSERT statements accordingly.