Get an alert when you lose the Amazon Buy Box, with the likely cause attached
Updated · By Ecomsellertool editorial team
To automate Amazon Buy Box loss alerts, subscribe to the ANY_OFFER_CHANGED and PRICING_HEALTH notifications, check whether your seller ID still holds a winning offer, re-check after a short wait so rotation does not page anyone, then match the loss to its likely cause: stock, price, delivery or a new seller. Rules rank and route each alert. A person decides price changes.
- Amazon's ANY_OFFER_CHANGED fires on a change to the top 20 offers by condition, the external price, or the Buy Box winner or price, only for items where you have an active offer (checked November 5, 2026).
- Each offer in the payload can carry IsBuyBoxWinner, and Amazon says there can be up to two winners per ASIN at once: one eligible for Prime and one not.
- With aggregation set to FiveMinutes, 50 price updates on one ASIN in 5 minutes produce two notifications: the first event and the final state.
- The PRICING_HEALTH notification is sent when an offer cannot be the Featured Offer because of an uncompetitive price.
- Amazon Ads says Sponsored Products and Display campaigns get 0 impressions when the advertised ASIN or SKU does not hold the Featured Offer, even when the campaign shows Delivering (help page updated October 16, 2026).
- getFeaturedOfferExpectedPriceBatch takes up to 40 requests per call at a default rate of 0.033 requests per second, and Amazon says the featured offer is not guaranteed at that price.
The step map: who runs each step
Trigger: An Amazon offer-change or pricing-health notification on one of your ASINs, plus a daily read of Featured Offer percentage per ASIN.
| Step | What happens | Who runs it |
|---|---|---|
| 1 | ANY_OFFER_CHANGED, PRICING_HEALTH, inventory and listing-status notifications arrive in a queue, with offer changes aggregated per ASIN over 5 or 10 minutes. | Rule |
| 2 | Each offer change is checked for your seller ID on an offer marked IsBuyBoxWinner, in the condition you sell, and the result is compared with the last known state for that ASIN. | Rule |
| 3 | A loss waits for the re-check: the next notification or a scheduled pricing call must agree before anyone is alerted. A loss that clears is logged with its length and closed. | Rule |
| 4 | A confirmed loss is matched to the rule table using stock, listing status, Pricing Health, seller ID, price gap and shipping time, and the featured offer expected price is fetched for the SKU. | Rule |
| 5 | Margin at risk per day is computed for the SKU, and the case goes out now or in the daily digest, to the owner the rule table names. | Rule |
| 6 | A person decides the fix: change a price or a minimum price, send stock, change a delivery setting, fix the listing, or leave the offer as it is. | Person |
| 7 | The case stays open until a later check shows your seller ID back on a winning offer, and the daily Featured Offer percentage shows whether the fix held. | Rule |
6 rule steps · 0 AI model steps · 1 person step. A rule follows fixed logic you approve; an AI model handles messy input and its output is checked by rules; a person makes the calls listed below.
What stays with a person
- Any price change, and any change to a minimum price, outside the limits you already approved in a repricer
- Whether to give up margin at all when the expected price sits below the SKU's floor
- What to do about an unknown seller on your listing, under your own policy
- Air freight or other paid fixes for a stock-driven loss
- Changes to the rule table, the margin floors and the alert threshold
Which tools can run it
- Pricing Health and Business Reports checked by hand each morning, for a few ASINs
- A repricing or monitoring app that has its own Buy Box alerts, with its own rules and fees
- A workflow tool such as Zapier, Make or n8n behind a small function that reads the Amazon notification queue and posts to Slack
- Custom code on your accounts, for state per ASIN, the re-check, the cause match and one case queue with stock and margin beside it
Systems it connects
- Amazon SP-API (Notifications, Product Pricing, Reports)
- Amazon SQS queue for notifications
- Margin floors and contribution margin per SKU
- Inventory or planning data for stock and inbound
- Authorized-reseller list with seller IDs
- Slack, email or a ticket queue for cases
Build size: Medium
Reading the notification is simple; the work is keeping state per ASIN, not alerting on rotation, and putting stock, margin and listing status on the same case.
Picture a Tuesday morning (an illustrative example). Sales on your best ASIN are down by a third and nobody knows why until someone opens the listing. Another seller has held the Buy Box since last night, or your stock ran out at a fulfillment center, or Amazon stopped featuring your offer because of a price outside the site. Each has a different owner and a different fix. This recipe turns Amazon's offer notifications into one case with the likely cause attached, sent to the person who can act on it. It is one page of our automation library.
Amazon now calls the Buy Box the Featured Offer, while its notification fields still say BuyBox. This page uses both names for the same thing. For what the Featured Offer is and how Amazon chooses it, read our Buy Box glossary page. This recipe is about the build: which signals to read and what each one should do.
Which signals should trigger a Buy Box alert, and who gets each one?
Write this table before you connect anything. The first two columns come from Amazon's data, using the fields in its notification type values (checked November 5, 2026). The other three are starting rules we suggest, for your team to change. A row fires only after the re-check in the next section.
| # | What the data shows | Likely meaning | What the rule does | Who acts |
|---|---|---|---|---|
| 1 | Change type Featured Offer, and your seller ID is no longer on an offer marked IsBuyBoxWinner | You lost it, cause not yet known | Runs rows 2-8 against the case, fetches the expected price, opens a case | Amazon account manager |
| 2 | Row 1, and FBA_INVENTORY_AVAILABILITY_CHANGES shows Fulfillable at 0 (or your merchant-fulfilled quantity is 0) | Out of stock | Attaches inbound quantities and days of cover; alert now | Inventory owner |
| 3 | PRICING_HEALTH arrives for the offer | Your total price is uncompetitive, so the offer cannot be featured | Attaches your landed price, the Buy Box price and the room to your floor (see the formula) | Pricing owner |
| 4 | Change type External: the CompetitivePriceThreshold moved below your landed price | A price outside Amazon moved, and row 3 may follow | Logs it; daily digest unless row 3 follows | Pricing owner |
| 5 | The winning offer's seller ID is not on your reseller list | A new or unknown seller holds it | Records seller ID, price and fulfillment; hands off to the MAP and seller monitoring recipe | Brand protection owner |
| 6 | Another seller wins, your landed price is equal or lower, and their ShippingTime is shorter or their offer is Prime | Delivery promise, not price | Attaches both shipping times; daily digest | Operations owner |
| 7 | LISTINGS_ITEM_STATUS_CHANGE shows a buyability change, or LISTINGS_ITEM_ISSUES_CHANGE shows a new issue | A listing problem, not a competitor | Pulls the listing's issues; alert now | Catalog owner |
| 8 | No offer is marked as the winner on your own brand's ASIN | Nobody is featured | Checks stock and Pricing Health; alert now | Amazon account manager |
| 9 | The lost SKU is in an active Sponsored Products or Display campaign | Those ads stop serving | Adds the campaign and daily budget to the case and copies the ads owner | Ads owner |
| 10 | Your seller ID is back on a winning offer | Rotation or a fix that worked | Closes the case and logs how long the loss lasted | Nobody (rule) |
Three of these need a note. Row 8 is real even for a sole seller: Amazon Ads' help page says Amazon may not assign the Featured Offer if the product fails low-price standards or has insufficient inventory, even when you are the only seller (updated October 16, 2026; checked November 5, 2026). Row 9 follows from the same page: Sponsored Products and Display campaigns get 0 impressions when the advertised ASIN or SKU does not hold the Featured Offer, while Sponsored Brands keeps serving as long as the product is available to buy. Our inventory-aware ad spend page covers the stock side of the same problem.
Row 6 needs care in how you word the alert. Amazon's Featured Offer help page says fulfillment method and the Prime badge are not considered when all other factors are equal, while faster offers and specific delivery promises are more likely to be featured (checked November 5, 2026). So tell the owner that delivery may be the cause. Amazon does not publish its ranking, so no rule can say for certain.
How do you stop false alarms when the Buy Box rotates?
An alert on every lost event trains your team to ignore it. Amazon's help page says that when no single offer is clearly better, the Featured Offer can be a rotation of the best offers, and that customers can see different featured offers by shipping location or Prime membership. So use three layers before anyone is paged.
Aggregation. The Notifications API model offers FiveMinutes or TenMinutes per marketplace and ASIN (checked November 5, 2026). Amazon's own example: with FiveMinutes, 50 price updates on one ASIN in 5 minutes produce two notifications, the first event and the final state 5 minutes later. The 48 in between are dropped. One catch: Amazon says eventFilter and filterExpression cannot be used together, and filterExpression does not aggregate. So use eventFilter for this notification.
The re-check. Treat the first lost event as a suspicion. Alert only when the next notification still shows you without a winning offer, or when a scheduled pricing call agrees after your chosen wait (we would start at 15 minutes). Amazon says there can be up to two winners per ASIN, one eligible for Prime and one not, so check every offer marked as a winner, not the first one you find.
The daily number. The Sales and Traffic report gives buyBoxPercentage by date and ASIN (checked November 5, 2026). Amazon calculates this share as page views where your offer is featured divided by total page views, so it shows what a single notification cannot: how much of the day you held it. A case that keeps opening and closing on a steady 60% is rotation to review weekly, not an emergency.
Which losses are worth an alert right now?
Rank by money. Otherwise a slow SKU gets the same page as your best seller. We use two numbers, both estimates from your own data.
Margin at risk per day = average daily units × contribution margin per unit
Room to match = featured offer expected price − margin floor
The expected price comes from getFeaturedOfferExpectedPriceBatch: up to 40 requests per call at a default rate of 0.033 requests per second, so about one call every 30 seconds (checked November 5, 2026). It returns the listing price, before applicable promotions, at or below which your offer can expect to be featured. Amazon says that is not guaranteed, since competing offers can change. The result has a status: VALID_FOEP, NO_COMPETING_OFFER, OFFER_NOT_ELIGIBLE, OFFER_NOT_FOUND or ASIN_NOT_ELIGIBLE. A status other than VALID_FOEP gives you no price to compare, and that is itself a clue for the case.
Here is how the numbers work for three illustrative SKUs, with an instant-alert threshold of $150 a day. Set your own: it should be the margin that justifies interrupting someone. Each figure is an example, not a client result.
| SKU | Daily units | Margin per unit | Margin at risk per day | Alert | Expected price | Floor | Room | Next step for the person |
|---|---|---|---|---|---|---|---|---|
| A | 40 | $9.00 | $360 | Now | $23.49 | $21.50 | +$1.99 | A match is possible; decide whether to give up that margin |
| B | 6 | $12.00 | $72 | Digest | $31.00 | $33.25 | −$2.25 | Do not match; look at cost, delivery or the other seller |
| C | 110 | $1.50 | $165 | Now | None (OFFER_NOT_ELIGIBLE) | $14.00 | Not known | Check stock, listing and Pricing Health first |
Row B is why the alert should carry the floor. Without it, the quick reaction to a lost Buy Box is a price cut, and a cut below the floor loses money on every order it wins.
What can the automation fix, and what stays with a person?
The automation collects, ranks, routes and closes cases. It does not move prices by itself. Amazon's Pricing Health page says it may deactivate an offer when it detects a potential pricing error, for example when your offer price is lower than the minimum price you set, and that one-click matching can also lower your minimum price (checked November 5, 2026). That is a good reason to keep minimum prices under a person's control. The same page says the pricing-opportunities download does not yet include offers deactivated for potential pricing errors, so a report on that file alone would miss them. Have someone look at that part of the page too.
If you want prices to move without a person, do it inside limits you set. Amazon's help page points sellers to Automate Pricing, which adjusts prices in real time within the parameters you choose, and a third-party or custom repricer does the same with its own rules. An alert still earns its place next to a repricer, because a repricer cannot send stock, fix a listing or decide about a stranger on your ASIN. When several SKUs sit on one ASIN, remember that the notification is by ASIN while ads serve by SKU: Amazon Ads says only the SKU holding the Featured Offer can serve them.
Who builds Buy Box alerts for Amazon brands?
Ecomsellertool builds workflow automation on your own marketplace accounts. We have built software on Amazon's seller APIs since 2017 and shipped 50+ tools for 100+ teams. For this recipe we start with your top ASINs, your margin floors and who owns each fix, then connect the notifications, the re-check and one case queue. Send a project brief below, or read how our workflow automation service works.
The building blocks are work we have shipped:
- Seller alerts for Amazon accounts. For AccountDr we built rule-based automation that sends push and email notifications for suppressed Buy Box, hijackers, listing faults and other account events, the same kinds of signal as rows 1, 5 and 7.
- Price rules against the Buy Box. For the repricer we built, rule-based automation, each offer is repriced by rule against the Buy Box or the lowest price, so a seller can compete without holding a price below margin.
A wider view of account health, with drafted case responses, is our account health agent. Margin and stock can sit beside these cases 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 Buy Box alerts built
Send us your top ASINs and who should get each alert
Describe the workflow you want automated. We reply with a written plan: scope, timeline and a fixed price.
Frequently asked questions
How do I get notified when I lose the Buy Box on Amazon?
The Selling Partner API has no notification named for a lost Buy Box, so you build the alert from ANY_OFFER_CHANGED. Subscribe through the Selling Partner API, read the offers in each notification, and alert when your seller ID is no longer on an offer marked IsBuyBoxWinner and a re-check agrees. Pricing Health in Seller Central shows the pricing side by hand.
Why does my Buy Box keep switching on and off?
Amazon says that when no single offer is clearly more attractive, the Featured Offer can rotate among the best offers. Customers can also see different featured offers depending on their shipping location or Prime membership. So a single lost event may not be a real loss. Watch Featured Offer percentage per ASIN over days before you change a price.
Does ANY_OFFER_CHANGED tell me why I lost the Buy Box?
No. It says what changed: the offer change type, the top 20 offers for that condition, their prices, shipping times and winner flags. The cause comes from comparing those with your stock, listing status, Pricing Health and delivery settings, which is the job of the rule table on this page.
Should the alert change my price automatically?
Not by itself. If you want price changes without a person, set them inside limits you chose, with a minimum price, in Amazon's Automate Pricing or another repricer. The alert exists for what a repricer cannot see: a stockout, a listing fault, a new seller, or an expected price below your margin floor.
What does it cost me to lose the Buy Box while ads are running?
Amazon Ads says Sponsored Products and Display campaigns get 0 impressions when the advertised ASIN or SKU does not hold the Featured Offer, even if the campaign shows Delivering. Sponsored Brands keeps serving while the product is available to buy. So you lose those impressions as well as the orders on your own offer.
Can I get these alerts for ASINs I do not sell?
Not through this notification. Amazon says you only receive ANY_OFFER_CHANGED for items where you have an active offer, and you cannot subscribe for others. For an ASIN where your offer has gone inactive, a scheduled pricing call is the fallback, within its rate limits.
