Added to Amalert: Jan 30, 2026
Amazon SP-API Deprecation Deadlines: Key Migrations Sellers Must Complete Before July 2025
Amazon will retire twelve legacy XML/flat‑file feeds on July 31 2025, remove the listCategories operation on March 31 2026, and eliminate Subscribe & Save reports on September 11 2025, while also trimming the competitivePrice field after June 30 2025. Sellers must migrate to the JSON Listings Items API, use searchCatalogItems for category data, and adopt the Finances API or V3 settlement reports to avoid interruptions.
Overview
Amazon has announced a new deprecation timetable for the Selling Partner API (SP‑API). The most critical deadline pushes the shutdown of twelve legacy XML and flat‑file feed types to July 31 2025, while additional removals target catalog, financial, subscription, and pricing endpoints through mid‑2026. Sellers who still rely on these older interfaces must begin migration now to avoid service interruptions that could halt listing, inventory, or pricing updates.
Key Points
- Legacy Feed Cutoff – July 31 2025 — Twelve XML/flat‑file feeds, including POST_PRODUCT_DATA and POST_INVENTORY_AVAILABILITY_DATA, will stop working on this date.
- Catalog API Change – March 31 2026 — The listCategories operation will be retired, ending a common method for category discovery.
- Subscribe & Save Reports – September 11 2025 — GET_FBA_SNS_FORECAST_DATA and GET_FBA_SNS_PERFORMANCE_DATA will disappear with no announced replacements.
- Settlement Report Version 2 – January 25 2026 — Flat‑file and XML V2 settlement reports will be removed, pushing users toward newer formats or the Finances API.
- Pricing API Trim – June 30 2025 — The competitivePrice field inside referencePrices will no longer appear in getCompetitiveSummary responses.
- Migration Window Extension — Amazon delayed the legacy feed deadline by four months, indicating that many sellers still depend on the old feeds.
How the Changes Work
- Legacy Feed Migration — Replace calls to XML/flat‑file feeds with the JSON‑based Listings Items API or the JSON_LISTINGS_FEED type. For example, a seller currently using POST_PRODUCT_PRICING_DATA to update prices must switch to a JSON payload sent via the new endpoint, which validates each attribute individually.
- Catalog Category Update — Shift from the listCategories operation to alternative methods such as the Catalog Items API’s searchCatalogItems or external taxonomy services. A developer who previously fetched category trees via listCategories will now query searchCatalogItems with a keyword filter to retrieve matching categories.
Analysis & Recommendations
Why This Matters
If sellers continue using the deprecated XML feeds, their product listings and inventory updates will stop on July 31 2025, causing loss of sales. The removal of competitivePrice and Subscribe & Save reports removes key data points for repricing engines and subscription forecasting, forcing a redesign of automation before the respective dates.
Key Takeaways
- Twelve legacy XML/flat‑file feeds (e.g., POST_PRODUCT_DATA) will cease on July 31 2025.
- The competitivePrice field in getCompetitiveSummary responses is removed after June 30 2025.
- GET_FBA_SNS_FORECAST_DATA and GET_FBA_SNS_PERFORMANCE_DATA reports retire on September 11 2025 with no direct replacements.
- Settlement report V2 (flat‑file/XML) is removed on January 25 2026; sellers must switch to V3 format or the Finances API.
Recommended Actions
- →Replace all POST_PRODUCT_DATA, POST_INVENTORY_AVAILABILITY_DATA, etc., with JSON Listings Items API calls (endpoint /listings/2021-08-01/items) and...
- →Update category retrieval: replace listCategories calls with Catalog Items API searchCatalogItems (endpoint /catalog/v0/items) and verify results f...
- →Edit pricing scripts to drop the competitivePrice field and rely on the price field; migrate settlement report extraction to GET_FINANCIAL_EVENT_GR...
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!