Get a daily warning before Seller Fulfilled Prime metrics cost you the Prime badge

Seller Fulfilled Prime lets you show the Prime badge on orders you ship yourself, and Amazon judges it on a short clock. Each week runs Sunday through Saturday. By the time a notice email arrives, the week is already lost. This recipe watches the same requirements every morning, turns each percentage into a count of misses left this week, and sends the case to whoever can still change the result. It is one page of our automation library, and it covers the US program, where these help pages apply.

Which Seller Fulfilled Prime metrics should trigger an alert, and at what level?

Write this table first. The requirement column comes from Amazon's performance requirements page and program policy (both checked November 6, 2026). The warning levels are our illustrative suggestions, not Amazon's numbers and not a promise of any result. Your team should set its own. "After login" means Amazon describes the source on a public help page, but the data itself sits inside Seller Central, and we could not view it.

Speed lines move, so keep them in a table a person edits rather than in code. The upcoming changes page shows the current 1-day and 2-day lines began July 6, 2026 (checked November 6, 2026). Amazon says on-time delivery and speed minimums are refreshed quarterly, with at least 45 days' notice of an increase. Its performance page also says weekends were temporarily left out of speed evaluation from May 31 to October 17, 2026, a window that has now ended.

Peak season can change the lines too. Amazon's holiday preparation page says it may adjust speed requirements (checked November 6, 2026). Its 2024 forum notice did so from November 24, 2024 through January 4, 2025, which is history, not this year's rule. We found no 2026 holiday numbers on the pages we read on November 6, so look on your dashboard before trusting any warning level in peak.

One more honest limit: eligibility is tracked by size tier, not by SKU. The speed report names the ASINs that pull a tier down, and Amazon's speed improvement page says an item with missing dimensions defaults to standard size (checked November 6, 2026). So a SKU alert means "this item is hurting its tier". Check dimensions on the ones you do not recognize.

Where does the data come from if the dashboard has no API?

From three places, and each covers a different gap. In the SP-API performance report documentation and Amazon's other report pages, we found no Seller Fulfilled Prime dashboard report (checked November 6, 2026). The seller performance report carries account-wide rates and can only be requested. It does not give a Prime view, so it cannot answer the question on its own.

The two downloads. The defects report lists orders that missed an eligibility metric, with promised dates, first scan, carrier, tracking ID, origin zip and an X per metric. The speed report gives page views by ASIN, date and size tier (both checked November 6, 2026). Have a person download them each morning. It takes a couple of minutes, and it is Amazon's own view. We would not script a browser to fetch them: Amazon's Agent Policy bars agents from mimicking human page navigation to hide that they are agents (checked November 6, 2026), and our Agent Policy guide explains why API-based tools are the safer route.

Your own model. The defects report only shows orders that already missed, so you need your own count for what is coming. The Orders API v2026-01-01 model gives a PRIME program value on the order, the deliver-by window, packages with carrier and tracking number, and who canceled each item (checked November 6, 2026). Add carrier scans, and you have an estimate of on-time, tracking and cancellation rates. Our Amazon and Walmart orders to a 3PL recipe already covers pulling those orders and confirming shipments.

What you cannot rebuild. Speed counts what Prime customers saw on the page, so orders cannot recreate it. Compute each share from the download: views at that threshold divided by all views, which is the 5-day-or-less column plus the over-5-days column. Reconcile with the dashboard, and let the dashboard win.

Why can Account Health look fine while Seller Fulfilled Prime is at risk?

Because the lines are tighter, the window is shorter and the late signal is different. A team watching only Account Health may see green while a tier fails. The account-wide lines are from Amazon's Order Performance policy (checked November 6, 2026).

Coming back is not quick either. Amazon's trial page asks for 100 seller-fulfilled packages over 90 days to pre-qualify, then a 4-week trial, and the program policy allows three trial attempts per calendar year (checked November 6, 2026).

How do you turn a weekly percentage into a number your team can act on?

Count misses, not percentages. "93.9%" means little at 9 a.m. on a Thursday; "9 late units left this week" does. Run this per size tier, using a forecast from your recent weeks.

Misses allowed this week = expected weekly count × allowed miss rate, rounded down

The allowed miss rates follow from Amazon's lines: 6.5% for on-time delivery, 1% for valid tracking and 0.5% for cancellations. Low volume is where this bites. These counts are illustrative, and they use one number for units and packages to keep the table simple.

At the 100-packages-a-month level, a week is about 25 units. One seller cancellation is 4% of that week, so a single stock mistake can be a miss.

Here is one illustrative calculation, not a client result. A standard-size tier ends Wednesday with these counts, and the team forecasts its week from the prior four.

All three rates pass today. The alert still fires, because the late rate has run at 6.1% and must fall to 4.2% for the rest of the week. That gives the operations lead three days to move volume to a better carrier service or lower the daily limit. Treat these as estimates: Amazon's pages do not say exactly how a unit delivered this week but ordered last week is assigned, so compare with the dashboard every Sunday and adjust.

What happens after a first, second or third miss?

The workflow's job is to keep the count and the dates, since Amazon's clock runs per requirement. This is from Amazon's Maintain enrollment page (checked November 6, 2026). The program policy words the third miss more broadly, as enrollment being revoked, so read both if you run several tiers.

Three dates matter. Meeting a requirement for four consecutive weeks after a first or second miss resets it. Appeals are due within 14 calendar days of the notice, Amazon closes one after 4 days without a reply to its request, and you may submit no more than 3 a quarter, not counting ones that overturn a decision. And timing a re-enable has a cost: if you re-enable during the week of the second notice, the entire week counts, with no exemption. Amazon suggests waiting until Sunday 00:00 PST. These exemptions cover only the metric named in the second notice.

A case helps most with the root cause. Amazon's revocation page points on-time misses at carrier scanning and order limits, cancellations at inventory control, tracking at the upload process, and speed at one-day coverage and cut-offs (checked November 6, 2026). Attach the matching checklist to each case, and link a parcel-level problem to our shipping exception alerts, which tell the customer and handle the parcel itself.

What should stay with a person?

Anything that changes what customers see, or what you tell Amazon. Pausing Prime is the clearest case. Amazon's order volume page says disabling takes effect for all products, that page views and orders while disabled are left out of your performance, and that Amazon recommends it for unplanned events such as major weather, labor shortages or equipment failures (checked November 6, 2026). But orders from customers' carts can still arrive and must ship on time. The program policy also says toggling Prime or reducing limits to reduce or evade the weekend requirement is against policy. A rule cannot judge intent, so it never flips this switch.

The same goes for the order limit. Amazon says the limit should reflect your internal capacity to ship, not a sales forecast, and it applies to same-day, one-day and two-day orders, not standard shipping. Lowering it costs sales, so it stays a decision. Buying labels is another: the program policy gives on-time delivery protection when Shipping Settings Automation is on, labels are marked "OTDR Protected" in Amazon Buy Shipping or Veeqo, and you shipped on time. Whether that fits your carrier costs is for your operations lead to weigh, and our carrier rate shopping recipe shows one way to price that choice. If the same offer also loses the Featured Offer, our Buy Box loss alerts recipe tracks that side.

Who builds Seller Fulfilled Prime alerts?

Ecomsellertool builds workflow automation on your own Amazon, carrier and warehouse accounts, and has built on Amazon's seller APIs since 2017. For this recipe, we start with your size tiers and who owns each fix, then connect the reports, orders, carrier scans and one case queue. Send a project brief, or read how our workflow automation service works.

None of our case studies is a Seller Fulfilled Prime project, so here is what we have shipped that is close:

• Operational health on one screen. For Seller7 we helped put order volume, cancel rates, fulfillment health, pending shipments and alerts on one dashboard, pulling from each marketplace's own API and normalizing the data, the same pattern this recipe's weekly counts follow.
• Carriers and routing in one place. Ecom Global was built for 100M+ products, 20+ marketplaces and 13+ carriers, with carrier types, rate cards and routing rules kept together, which is the carrier data a late-delivery case needs.

A wider view of account risk, with drafted responses, is our account health agent. These alerts can sit beside your other order flows on Ecomsellertool Growth OS. You keep your accounts, your data and the custom code we build; the Growth OS base is licensed to you.

Get your Seller Fulfilled Prime alerts built