Overview

Amazon has stopped accepting XML and flat‑file listings feeds through the Feeds API as of today. The legacy format can no longer be used to submit pricing, inventory, relationship, or image data, and no new categories or attributes will be added to the old XML schema. Sellers must migrate to the Selling Partner API (SP‑API) immediately to keep their catalog up‑to‑date and avoid feed rejections.

Key Points

• Deprecation effective immediately — The Feeds API will reject any XML or flat‑file feed submitted from today onward.
• Legacy XML schema frozen — Amazon will not accept extensions or new category nodes in the old XML definition.
• All listing data impacted — Price, quantity, product relationships, and image URLs sent via XML or flat files will no longer be processed.
• SP‑API as the recommended path — Listings Items, Listings Items Restrictions, and Catalog Items endpoints replace the former feed mechanism.
• Urgent migration required — If a seller’s next scheduled feed runs after the change, the submission will be rejected and the listing may become outdated.

How the Change Works

1. Feed submission block — When a seller posts an XML or flat‑file feed to the Feeds API, Amazon returns a 4xx error stating the format is unsupported.

   • Example: A retailer that uploads a daily inventory file containing 5,000 SKUs receives an “Unsupported Feed Type” response, causing the entire update to stop.

2. Legacy XML schema locked — The XSD that defined the old XML structure is archived; Amazon will not process any added elements such as new attribute groups or category‑specific tags.

   • Example: A vendor attempts to include a <BatteryLife> node for a new line of electronics, but the feed is rejected because the schema cannot be extended.

3. SP‑API endpoint activation — Sellers must call and supply a JSON payload that mirrors the data previously sent in XML.