Skip to main content
Card class: Cross-ChannelCategory: Shipping & Courier
ASINs at risk of losing the Prime badge - sortable table with current OTD vs SFP threshold. Each row = a Buy Box loss waiting to happen.

At a glance

Per-ASIN view of Prime-promised on-time delivery rate, joined to Amazon listing data. Each row is one ASIN with current 30-day Prime OTD; sorted ascending so worst-performing rises to top. Rows below 99% are at SFP eligibility risk; rows below 96% are likely candidates for badge revocation. The card is the per-product diagnostic that goes underneath the seller-account-wide SFP eligibility number.
What it countsGROUP BY amazon_prime_shipping.shipment.asin COMPUTE otd_pct WHERE otd_pct < 99 JOIN amazon.listing ON asin over rolling 30 days. ASINs with sufficient sample (typically >20 shipments in 30D) included; low-volume ASINs filtered out for noise.
Required Amazon siblinghas_amazon_sibling. Card requires an Amazon connector (Seller Central or Vendor Central) for the listing-side data join.
Why ASIN-level mattersAmazon’s SFP eligibility scoring is at the seller-account level, but listing-level performance varies materially. A heavy SKU shipping from a single warehouse to East Coast may run 99.5%; a rural-customer-skewed SKU may run 96%. Account-wide dilution masks this; the per-ASIN view exposes it.
Buy Box loss correlationBelow 99% Prime OTD on an ASIN, Amazon’s Buy Box algorithm starts deprioritising the listing within 7 to 14 days. Each ASIN row in the table is a future Buy Box loss; the card surfaces them before the loss happens.
Service level scopePrime-eligible 1-Day / 2-Day / Same-Day.
Time window30D
Alert triggerany ASIN <99% OTD. Card alerts on the existence of any below-threshold ASIN; the table content is the diagnostic.
Rolesowner, operations, marketing

Calculation

Calculated automatically from your Amazon Prime Shipping (SFP) data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

Worked example

A US small-appliance merchant. Reading at 09:00 ET on 12 Mar 26 for the trailing 30 days.
ASINListingPrime shipments (30D)Prime OTDBuy Box risk
B07XYZ1234Kitchen blender, $8938094.2%High - dropping out of Buy Box, est. 32% of shipments to rural ZIPs via USPS Priority
B07ABC5678Coffee grinder, $7222095.8%High - similar rural-USPS profile
B08DEF9012Stand mixer, $18914597.1%Medium - on warning list
B07GHI3456Hand mixer, $4551098.9%Medium - just below 99%
B07JKL7890Food scale, $2572099.4%OK
(38 ASINs above 99% OTD, omitted)OK
Account-wide Prime OTD: 96.3% (matches amazon_prime_sfp_otd_sla). Five things to notice:
  1. Two ASINs (B07XYZ1234 and B07ABC5678) account for ~70% of the seller-account-wide miss volume. Concentration matters: fixing two SKUs lifts the whole account toward 99%.
  2. Both worst-performing ASINs share the rural-USPS-Priority cohort. The fix is product-level: opt these ASINs out of Prime eligibility for rural ZIPs (in Seller Central → ASIN-level Prime settings if available, or globally for the seller account). Customers in those ZIPs see the listing without Prime; conversion drops on those orders but the account-wide Prime badge is preserved.
  3. B08DEF9012 (stand mixer) at 97.1% is the medium-risk SKU. Larger / heavier items run higher exception rates and are more carrier-mis-handled. Consider double-walled packaging or signature-required upgrades for this cohort.
  4. B07GHI3456 (hand mixer) at 98.9% is on the cusp. One bad week pushes it below 99%; pre-emptive monitoring required.
  5. The 38 ASINs above 99% are doing fine. Account-wide remediation should focus on the 4 problematic ASINs, not blanket-tighten all SKUs. The card surfaces the actionable cohort.

Sibling cards merchants should reference together

Per-ASIN view connects to listing-side data and Buy Box dynamics. Pair with these:
CardWhy pair it with SFP Eligibility by ASINWhat the combination tells you
SFP On-Time Delivery vs 99% ThresholdAccount-wide SFP eligibility.This card explains the account-wide number by exposing the ASIN concentration.
Late-Shipment Buy Box LossThe financial-impact estimate for late-OTD-driven Buy Box loss.Per-ASIN Buy Box loss is a function of per-ASIN Prime OTD; combine for SKU-level revenue at risk.
Prime 1-Day / 2-Day Promise Miss Rate7-day leading indicator.When this card alerts, drill in to identify which ASINs are dragging.
Cross-connector: amazon.buy_box_win_rateDirect Amazon-side metric.Compare per-ASIN Buy Box win rate against this card’s per-ASIN Prime OTD; correlation should be strong.
Cross-connector: amazon.listing_inventoryPer-ASIN inventory.Stock-out + Prime-OTD-risk = double trouble for Buy Box.
Cross-connector: amazon.az_concessionsPer-ASIN Concession costs.High-Concession ASINs typically map to high-Prime-miss ASINs.

Reconciling against the vendor’s own dashboard

Where to look in Amazon Seller Central: Seller Central does not natively offer per-ASIN Prime OTD breakdown in a single dashboard view. Closest: Performance → Shipping Performance, drill into individual ASINs via the order-history reports. Most sellers manually export and pivot in spreadsheets. This card is the automated equivalent. Why our number may legitimately differ:
ReasonDirectionWhy
Sample size thresholdEitherCard filters out low-volume ASINs (typically <20 30D shipments) for noise reduction. Manual analysis may include them.
Time zoneBoundaryUK/US merchants typically connect timezone-matched.
Listing-data join freshnessOurs <1 hour behindAmazon listing data refreshes hourly via SP-API.
Cross-connector reconciliation:
CardExpected relationshipWhat causes legitimate divergence
amazon.buy_box_win_ratePer-ASIN Buy Box.Buy Box affected by price, stock, seller rating in addition to Prime OTD.

Known limitations / merchant FAQs

Why ASIN-level when Amazon scores at the seller-account level? Account-wide eligibility is the consequence; ASIN-level Prime performance is the cause. Two ASINs running 90% can drag a 50-ASIN seller account from 99% to 96%. Fixing those two specific ASINs is much cheaper than blanket-tightening operations across all 50. The card shows 4 ASINs at risk; which do we fix first? Sort by total Prime miss volume (Prime shipments × (1 - Prime OTD)). The ASIN contributing the most absolute miss volume gives the largest account-wide lift when fixed. The card sorts by OTD% ascending; for triage purposes, look at the volume column too. ASIN-level Prime opt-out: how does it work? Amazon’s Prime settings allow account-wide opt-out of specific ZIPs. ASIN-level opt-out is more limited but exists for some categories. Check Seller Central → Account Info → Prime Settings → Excluded ZIP Codes, and combine with Inventory → Edit Listing → Prime Eligibility for the per-ASIN view where supported. Low-volume ASINs are filtered; can we see them? Yes by lowering the volume threshold in card settings. Default is >20 30D shipments; lowering to >5 surfaces more ASINs but introduces noise from small-sample variance. An ASIN at 99.5% just dropped to 96%; what happened? Three usual causes. (1) Carrier-mix shift for that ASIN: Amazon rerouted some volume to a different carrier for capacity reasons. (2) Demand shift to rural ZIPs: a regional promotion or marketplace expansion brought in customers from longer-zone destinations. (3) Packaging change: new packaging trim weight or dimension shifts ZIP-rate-card categorisation. Investigate by comparing this period’s destination ZIP profile to last period’s. Buy with Prime ASINs: are they here too? Yes if the Buy with Prime program is connected. Buy with Prime products are tracked separately but pooled into the per-ASIN Prime OTD computation. Does this card include FBA orders? No. FBA-fulfilled orders are managed by Amazon and don’t appear in SFP eligibility scoring. This card is SFP-only (and Buy with Prime where connected). A new ASIN was launched mid-period; weighting? ASIN appears in the table once it has >20 30D shipments. New launches with smaller initial volume may be filtered out for the first few weeks. Track separately during launch ramp. Amazon’s per-ASIN Prime OTD: does Amazon expose this in the API? Limited. Amazon’s SP-API exposes per-order delivery data; the per-ASIN aggregation is the merchant’s responsibility (or Vortex IQ’s, in this card). Amazon’s seller-facing reports include some per-ASIN delivery metrics but not in a real-time dashboard format. During Q4 peak, every ASIN dips; do we triage? Focus on the highest-volume ASINs (the SKUs that dominate revenue). A 95% Prime OTD on a 1,000-shipment-month SKU is more impactful to account-wide eligibility than 95% on a 50-shipment-month SKU. Sort by absolute miss volume (column not shown in worked example but in card UI).

Tracked live in Vortex IQ Nerve Centre

SFP Eligibility Risk by ASIN is one of hundreds of KPI pulses Vortex IQ tracks across Amazon Prime Shipping (SFP) and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.