Overview

Amazon has pushed the retirement of twelve legacy XML and flat‑file listing feeds in the Selling Partner API (SP‑API) from March 31 2025 to June 30 2025. The three‑month extension gives sellers and developers extra time to shift their listing‑management processes to the newer JSON‑based alternatives. After June 30 2025, any integration still relying on the deprecated feed types will cease to function.

Key Points

• New cutoff date — The removal deadline moves from March 31 2025 to June 30 2025, as announced on 26 January 2025.
• Feeds affected — Twelve feed families are impacted, covering product data, inventory, pricing, images, relationship mappings, and flat‑file formats such as invloader and listings data.
• Mandatory migration — Sellers must adopt either the Listings Items API or the JSON_LISTINGS_FEED endpoint in the Feeds API before the June deadline.
• No further extensions — The feeds were first slated for deprecation in September 2024, giving a total notice period of roughly 15 months.
• Testing strongly advised — Amazon recommends sandbox trials and incremental roll‑outs to catch attribute mismatches and required‑field gaps early.

How the Migration Works

1. Choose a migration path —
   Example: A mid‑size seller using the invloader flat‑file to upload 30,000 SKUs can either switch to the Listings Items API for real‑time updates or continue batch processing by submitting a JSON_LISTINGS_FEED.

2. Adopt product type definitions —
   Example: An apparel seller previously sending custom XML tags for “size” must now map those values to the APPAREL product type definition, which specifies required attributes like size and material in a predefined JSON schema.

3. Reformat data to JSON —
   Example: A bulk uploader that once generated a CSV line SKU,Price,Quantity for the legacy feed now builds a JSON object: .