Overview

Amazon has upgraded the JSON LISTINGS FEED in the Selling Partner API (SP‑API) by adding an optional includedData field to the feed header. This change pushes post‑submission quality and compliance alerts into the standard processing report, giving sellers immediate visibility into issues that previously required separate dashboard checks. Sellers who upload large batches of listings should care because the new feedback loop can cut remediation time from days to minutes.

Key Points

• includedData field — An optional header element that, when set, expands the processing report to include post‑acceptance problems.
• Post‑validation issue capture — The report now lists compliance flags, data‑quality warnings, and marketplace‑specific gaps discovered after the feed passes the initial syntax check.
• New report schema — Results follow the listings-feed-processing-report-schema-v2.json format, adding sections for “postAcceptanceIssues.”
• Zero breaking changes — Existing integrations that omit the field continue to work exactly as before.
• Cross‑marketplace relevance — Sellers operating in multiple regions receive a unified view of marketplace‑specific compliance alerts within a single feed response.

How the Expanded Reporting Works

1. Submit the bulk feed — A seller packages thousands of product records into a JSON LISTINGS FEED request and includes the optional includedData flag in the header (e.g., "includedData": ["postAcceptanceIssues"]).
2. Initial validation pass — Amazon first checks the payload for structural errors such as missing required attributes or malformed JSON. Any failures are reported in the standard “validationErrors” section, just as before.
3. Post‑acceptance analysis — After the feed clears the first check, Amazon runs deeper checks that evaluate data accuracy, policy compliance, and marketplace‑specific requirements. For example, a product flagged for prohibited battery type or a missing required attribute for EU marketplaces will be captured here.