Sourceable vs. Procurable OOS Rate

Vendor Central exposes two out-of-stock metrics that are often confused with each other: Sourceable OOS Rate and Procurable OOS Rate. They share the same formula but measure availability from different perspectives.

The core distinction

Both metrics are calculated the same way:

OOS Rate = OOS glance views ÷ total glance views

The difference is whose availability is being measured:

In plain terms: Procurable = anyone can fulfill it. Sourceable = you specifically can fulfill it.

Sourceable OOS is the more operationally meaningful metric for vendors, because it isolates your own availability as the binding constraint — independent of whether 3P sellers or other sources have stock.

Important: Sourceable OOS does not include Buy Box losses

Sourceable OOS measures physical stock unavailability only. It does not capture glance views where you lost the Buy Box to a third-party seller while you had stock. Those are separate lost-revenue events that were historically tracked by the (now deprecated) Lost Buy Box metric.

How to find these metrics in Vendor Central

Both metrics are in Reports > Retail Analytics > Inventory, under the Manufacturing distributor view.

• Procurable OOS (procurable_product_oos) — available at weekly and monthly granularity. Not available at daily grain.
• Sourceable OOS — only appears when you select a time frame longer than one week. It will not show up for daily or single-week selections.

Why you can't re-aggregate OOS rate from ARA exports

A common mistake is to try to reconstruct a portfolio-level OOS rate by multiplying the ASIN-level OOS rate by Featured Offer Page Views (FOPV):

❌  Procurable OOS Rate × Featured Offer Page Views = OOS Page Views

This produces an understated result (e.g. 12.5% when ARA shows 18.5%) because FOPV uses the wrong denominator.

Featured Offer Page Views only count page views where a featured offer existed — by definition, if the product is OOS, there is no featured offer, so those page views are excluded from FOPV entirely. You end up dividing OOS page views by a number that structurally excludes the very events you're trying to measure.

The correct denominator is total glance views — all page views regardless of offer status. ARA uses this internally but does not expose it in downloadable reports.

The correct aggregation formula:

✅  Portfolio OOS Rate = SUM(OOS glance views per ASIN) ÷ SUM(total glance views per ASIN)

Since total glance views are not available in ARA exports, accurate re-aggregation from downloaded data is not currently possible. The most reliable approach is to use ASIN-level OOS rates as Amazon reports them, or request ASIN-level OOS data directly from your Amazon retail contact.

Ordering codes and Sourceable OOS accuracy

If your account uses multiple ordering codes (e.g. a local warehouse code and a Direct Fulfilment code), both need to reflect accurate availability for Sourceable OOS to be reliable.

If a Direct Fulfilment code shows availability but there is no physical stock to ship, the ASIN will still count as sourceable OOS — inflating the rate and making your availability position appear worse than it is. Keeping both codes current gives you the most accurate read on true OOS exposure.

Summary

Related pages

• Retail Analytics Inventory
• Manufacturing View vs. Sourcing View