Amazon Sales Stopped Suddenly: How to Tell an Outage From a Listing Problem

Three threads appeared on the Seller Forums in two days in September 2026: anyone experiencing delayed orders in Seller Central today, Amazon sales stuck for the last hour, did Amazon's servers go down again. They appear in the same form every few weeks, and the replies under them divide the same way every time. Most of the sellers are watching a delay in Amazon's order reporting and their sales are fine. A few have a listing that was suppressed that morning, a buy box that moved, or an ad campaign that ran out, and the outage thread is where they went instead of looking.

This is the check we run when a client's orders stop, in the order that finds the cause fastest. It takes about twenty minutes and it has to be done in order, because the first step is the one that tells you whether the rest matter.

When Amazon sales stop suddenly, the first question is whether it is happening to everybody. If the Seller Forums have a fresh thread with sellers across categories describing the same thing, the cause is almost always a delay in Amazon's order reporting, the orders will appear when it catches up, and the right move is to change nothing. If there is no such thread, the cause is in the account, and four checks, made in order, find it.

Look at the listing as a customer would, logged out and on a phone: is it live, is there a buy button, and is the offer that has it yours, at the price you set. Then read the listing's status and the Action Center in the account, account health and the notifications, and the campaign manager for a budget that ran out or a campaign that paused. Most sudden stops are one of those four, and each has its own fix.

The shape of the drop is a clue before any of it. A wall at a particular time points to something that switched off: a listing, an offer, an account or a budget. A drop that is partial and spread through the day points to the market instead, such as a competitor's deal, a rank that slipped or a holiday somewhere.

Write down what each check shows as you go: the time of the last order, the listing's status, who holds the buy box, what account health says and where each campaign's budget stands. If the cause turns out to be a case for Amazon, those notes are the evidence the case needs, and if it was a reporting delay, they are the record that nothing needed changing.

Most sudden stops are noticed hours late, when somebody happens to open the sales graph. A few simple habits mean a stop is seen within the hour, which is often the difference between a fix today and a lost day.

Turn on the notifications that matter. Seller Central's notification preferences let the account send emails for listing problems, account health warnings and policy notices. Send them to an address somebody reads during the day, not only to the account owner.

Know the normal pace. For each of the main products, know roughly how many orders arrive by a given hour on a normal weekday. A quick look at the orders page mid morning against that figure shows a stop long before the end of the day.

Watch the budgets. The campaign manager shows campaigns that went out of budget and when. A campaign that regularly runs out before lunch is a stop that happens every day, whether anybody calls it one or not.

Watch the offer on the best sellers. Who holds the buying position on the products that matter most, checked daily, catches a lost Featured Offer the morning it happens.

Keep one place for the readings. A short daily note of orders by mid morning, budgets, the offer on the top products and any notification. Kept for a few weeks, it shows what normal looks like, which makes an abnormal day obvious.

None of this needs software. It needs one person who looks at the same few things at the same time each day.

Open the Seller Forums and sort by newest. When Amazon's order reporting is delayed or the site is degraded, there is a thread within the hour with dozens of replies from sellers across categories, and Amazon's community managers post in it when the incident is acknowledged. That thread is the fastest status page Amazon has. If it exists and it describes what you are seeing, the cause is Amazon, the orders are almost always there and will appear when reporting catches up, and nothing in the account should be changed until it does.

If there is no such thread, and the forum is discussing its usual subjects, the cause is in the account. A seller who changes prices or relaunches campaigns during a reporting delay makes decisions against data that is not there, and the threads carry more than one story of a price cut that turned a two hour delay into a bad week.

Open the product page as a customer, logged out, on a phone. Is it live, is there a buy button, is it your offer that has it, and is the price what you set. Then open the listing in the account and read its status. Suppressed, inactive, stranded and search suppressed are four different conditions with four different causes, and the account tells you which in the listing's own row and in the Action Center's critical cards. A listing suppressed for a missing attribute or an image rule comes back within hours of the fix; a listing removed for a policy reason does not, and the policy warnings article is the map of those.

The buy box is the second thing on that page. An offer that lost the buy box to a reseller at a lower price, or to Amazon itself, keeps its listing live and loses most of its sales in the same hour; the offer count and the buy box owner on the product page say so. The reselling article covers who can appear on a listing and what can be done about it.

Open account health and the case log. A listing deactivated for a performance notification, an account under review, a verification request that has been sitting unanswered for a week: each of these stops sales without changing the product page much, and each shows in the account health page before it shows anywhere else. The notifications inbox and the case log carry the same information a day earlier. Account health and reinstatement is what to do when it is this.

Check the orders page itself while there. An order held as pending, or one showing approval needed, is a payment or address hold rather than a sales problem, and the approval needed article explains those. A morning of pending orders that clear by evening is Amazon's payment processing, not the account.

Between the listing and the advertising sits a cause the checks above can miss: the stock. A product with units in the network can still have nothing a customer can buy.

Available against total. The inventory page separates units that can fill an order today from units that are reserved, inbound or unfulfillable. A product showing a healthy total can have zero available, and the product page then shows it as unavailable or with a delivery date weeks away.

Reserved units. Units being moved between fulfilment centres, or held while orders are processed, count in the total and cannot be sold. A product whose stock is mostly in transfer can stop selling for days while the units move.

Inbound not yet received. A shipment marked delivered to the fulfilment centre is not sellable until it has been checked in. In busy weeks that can take longer than sellers expect, and the product runs dry in the gap.

Merchant fulfilled quantities. For products the seller ships, a quantity of zero sent by an inventory feed, or a stock sync that failed overnight, takes the offer off sale without anything else changing.

A delivery date pushed out. When stock is low or far from the customer, the delivery promise shown can lengthen, and sales fall even though the product is technically available.

Checking the available figure takes a minute, and it explains a share of sudden stops that otherwise look like a listing problem.

For a product whose sales are mostly paid, sales stop when the ads do. Open the campaign manager: has the daily budget run out, is a campaign paused, was a bid rule changed overnight, has a keyword been made negative by mistake. A budget that ran out at ten in the morning looks, from the sales graph, like an outage at ten in the morning. The article on campaigns that spend without converting covers the opposite fault, where the ads run and nothing sells, and the two together account for most sudden drops on advertised products.

Before working through every check for every product, look at which products stopped. The pattern narrows the cause quickly.

Every product at once. When the whole catalogue stops at the same time, the cause sits above any one listing: an Amazon reporting delay, an account level action such as a review or a deactivation, or every campaign hitting a shared budget. Step one and step three come first.

One product alone. When one product stops and the rest carry on, the cause is that listing: a suppression, a lost Featured Offer, a stock problem, or a change to the catalogue page itself. Another contributor can change a listing's title, images or category, and a listing moved into the wrong category can drop out of the searches that sold it.

A family of variations. When every size or colour of one product stops together, check the parent listing. A broken variation relationship can split the family, leave children without a parent page, and scatter the reviews.

One fulfilment route. When only the merchant fulfilled products stop, or only the FBA ones, look at what they share: the shipping settings, the inventory feed, or the stock in the network.

One marketplace. For a seller in several Amazon stores, a stop in one store and not the others points to that store's listings, its account health or its advertising.

Writing down which products stopped, and when, also gives the case its first line if Amazon has to be asked.

A competitor launched a deal. A category page changed. The product's main search term shifted in rank overnight, which the search term report shows tomorrow. Seasonality, the day of the week, a holiday in the buyer's country. None of these are faults, and all of them look like one at eleven in the morning. The tell is that the drop is partial and spread over the day rather than a wall at a time.

What to do in each case is different, and that is the point of doing the check in order. An Amazon incident: wait, and change nothing. A suppressed listing: fix the attribute today. A lost buy box: a price decision, made from the unit economics rather than the panic. An account health notification: the reinstatement work, that day. An ad budget: raise it or accept the cap. For the brands we run, this check is a standing routine in compliance and account health, and the value of it is not the fix. It is the twenty minutes that stop a seller cutting a price to solve a reporting delay.

A listing that stays suppressed, blocked or pulled after the obvious fix is a case to file, which is what listing reinstatement does.