Overview

Amazon has refreshed Shipping API version 2 to accept Non‑Delivery Report (NDR) feedback from carriers and third‑party logistics providers. The new endpoint lets shippers instantly inform Amazon when a package cannot be delivered and specify the next step—whether to reschedule, attempt delivery again, or return the item to the seller. Sellers using Amazon’s fulfillment services must adapt quickly so their order‑status information stays accurate and automated follow‑up actions fire without delay.

Key Points

• Dedicated NDR endpoint — Version 2 now offers a specific call for submitting non‑delivery reports, delivering real‑time visibility into failed deliveries.
• Three actionable outcomes — The payload can contain one of three directives—Reschedule, Reattempt, or Return to Origin (RTO)—allowing carriers to communicate the intended next move.
• Strict eligibility rules — Only shipments created through the Shipping API and bearing a valid Amazon carrier label qualify for NDR feedback, preventing mismatched or legacy orders from being processed.
• Automatic status synchronization — Once an NDR is accepted, Amazon instantly flips the order’s delivery status to “Non‑Delivered,” eliminating the need for sellers to manually reconcile records.
• Enhanced buyer communication — Prompt NDR reporting enables sellers to send updated delivery windows or refund options faster, which helps protect performance metrics such as late‑shipment rates.
• Integration‑ready webhook — Amazon emits a webhook whenever an NDR is recorded, so any downstream order‑management system can react programmatically without human intervention.

How Shipping API v2 NDR Feedback Works

1. Submit NDR request — The shipper issues a POST to the /v2/ndr/feedback endpoint, including the Amazon shipment ID, a reason code (e.g., “address inaccessible”), and the chosen ndrAction. Example: A logistics partner posts an NDR for order #112‑3344556‑778899, cites “recipient not home,” and selects “Reschedule.”