Overview

In early 2024 Amazon added three new performance indicators to the Replenishment API. The metrics—LOST_REVENUE_DUE_TO_OOS, SUBSCRIBER_NON_SUBSCRIBER_AVERAGE_REORDERS, and SUBSCRIBER_NON_SUBSCRIBER_AVERAGE_REVENUE—are now delivered through the getSellingPartnerMetrics call. Sellers who automate inventory planning should start tracking these fields to prevent stock‑outs, fine‑tune subscription tactics, and lift overall profit margins.

Key Points

• LOST_REVENUE_DUE_TO_OOS — Shows the estimated dollar value lost when a SKU is out of stock; a bestseller unavailable for three days might report $4,200 in missed sales.
• SUBSCRIBER_NON_SUBSCRIBER_AVERAGE_REORDERS — Returns the mean number of repeat purchases per customer segment over the past 12 months, such as 2.8 orders for Prime subscribers versus 1.5 for non‑subscribers.
• SUBSCRIBER_NON_SUBSCRIBER_AVERAGE_REVENUE — Calculates the average revenue per order for each segment during the same 12‑month window, for example $38 per subscriber order compared with $27 per non‑subscriber order.
• Single‑Payload Delivery — The new fields appear in the same JSON response as existing replenishment data, eliminating the need for extra endpoint calls.
• Actionable Insight Potential — By linking lost‑revenue numbers to lead‑time and safety‑stock settings, sellers can model how tighter or looser inventory buffers affect the bottom line.

How the Updated Replenishment API Works

1. Request Assembly — The seller issues a GET to /getSellingPartnerMetrics, supplying required authentication headers and optional parameters like marketplaceId and dateRange.
   Example: A US‑based seller requests metrics for 2024‑01‑01 through 2024‑03‑31, attaching AWS IAM credentials and a valid SP‑API access token.

2. Response Composition — Amazon returns a JSON object whose metrics section now contains the three new fields, each populated with numeric values for the selected period.
   Example: The payload includes , , and .