Overview

Amazon has expanded the FEED_PROCESSING_FINISHED and REPORT_PROCESSING_FINISHED webhook events to include submissions that originate from Vendor Central. A new accountId attribute now appears in every payload, identifying the specific selling‑partner that triggered the feed or report. Sellers and vendors need to adjust their webhook listeners to capture this extra field, otherwise they risk missing critical processing signals.

Key Points

• Vendor‑originated feeds now supported — The two notifications are emitted for both Marketplace and Vendor Central submissions, giving vendors the same instant feedback previously reserved for sellers.
• New accountId field added — Each JSON message carries a unique partner identifier (e.g., “A1X2Y3Z4W5”) that tells the receiver which account initiated the request.
• Schema remains backward compatible — Existing elements such as feedId, reportId, processingStatus are unchanged, so older parsers will still function if they simply ignore the new property.
• Delivery timing unchanged — Amazon continues to push the notification within seconds of the processing job finishing, preserving the low‑latency automation many sellers rely on.
• Retry behavior for missing accountId — If a payload arrives without the new field (as can happen with legacy integrations), Amazon will attempt delivery up to three times before marking the message undeliverable.

How the Updated Notifications Work

1. Submission — A seller or vendor uploads a feed (price, inventory, etc.) or requests a report (sales, fulfillment) through the SP‑API. Example: A vendor sends a 10,000‑row price‑update file via the createFeedDocument call, specifying their Vendor Central credentials.
2. Processing — Amazon validates the file, applies business rules, and runs the job on its internal pipeline. Example: The system detects 12 rows with malformed SKUs but completes the remaining 9,988 rows in 45 seconds, marking the overall status as WARNING.
3. Notification dispatch — When the job ends, Amazon posts a FEED_PROCESSING_FINISHED or REPORT_PROCESSING_FINISHED message to the webhook URL registered in the developer profile. The payload now includes: