What Amazon's Native Seller Notifications Actually Cover (and Miss)
By Archit Mathur · Published · Last updated
Short answer
Seller Central's notification panel covers orders, returns and claims, account events and emergencies, and most sellers assume that covers everything worth knowing. It doesn't. The order emails exist but arrive and stop without warning, sometimes contradicting their own setting, and offer no filtering; the Selling Partner API publishes no notification type for a fee changing on one ASIN; and nothing fires when a settlement posts for less than you expected.
Every new seller assumes the same thing: Amazon will tell them what they need to know. There is a notification system, it has settings, it sends emails. The assumption is reasonable and it is wrong in a few specific, expensive places, because the system was built to cover different things than the ones that actually cost a seller money.
What Seller Central's notifications actually cover
The notification preferences panel groups everything into sections, each of which can be routed to its own email address and most of which can be switched off individually. Amazon is explicit that the types available to you depend on your selling plan (opens in a new tab), and names four categories as available regardless of plan.
| Category | What Amazon says it sends |
|---|---|
| Order Notifications | Alerts when you receive an order, plus optional FBA order and inbound shipment alerts |
| Returns and Claims Notifications | Return requests on seller-fulfilled orders, and buyer-disputed charges |
| Account Notifications | Business and technical alerts: new features, schedule changes, outages |
| Emergency Notifications | Contact during large-scale events that might affect orders or shipments |
As a list, that reads like coverage: orders, returns, account, emergencies. Every one of them fires on a discrete event, and the three things that most reliably cost a seller money are not discrete events.
The three gaps that actually cost money
Order notifications exist, but not as a signal you can tune
This one is usually overstated. Amazon does send per-order email: the "Sold, Ship Now" merchant notification on seller-fulfilled orders, and FBA order notifications.
The emails arrive. The channel carrying them is not dependable, and the forum record on this is unusually direct. When a seller reported order emails stopping abruptly one morning in May 2026 (opens in a new tab), the Amazon moderator's first suggestion was to re-check the preference and the email address on file, because in their words these can get reset or need re-verifying. That is a notification channel whose own settings are not guaranteed to stay where you put them.
The failure runs in both directions. In April 2026 a seller who had kept Sold, Ship Now switched off for years began receiving the emails again (opens in a new tab) while the setting still read as disabled. An Amazon moderator acknowledged the reports and passed them to the owning team; another seller returned weeks later to say it had stopped and then started once more. Whichever direction it fails in, the lesson is the same: the state of the toggle is not reliable evidence of what the system will do.
And it is all-or-nothing. The category is on or off. There is no filter for a specific SKU, a minimum order value, an item count, or one fulfilment channel but not the other. On a catalogue of any size that forces the same choice every time: every order, or none of them.
No fee-change subscription
This is the clear-cut one, a structural gap rather than an oversight sellers can configure their way around. The Selling Partner API publishes its full notification catalogue (opens in a new tab), roughly two dozen types covering offers, listings, inventory, orders, pricing health and account status. None of them is a fee change on an ASIN. The closest by name is FEE_PROMOTION, which announces a fee discount, not a fee moving.
So a remeasurement that pushes a product into a higher size tier, a category reclassification that changes the referral rate, a surcharge triggered by low inventory: none of them has a notification type to subscribe to. The fee simply changes, and the first evidence is a smaller number in the next settlement.
It is worth being precise about the boundary of that claim, because Amazon has shipped adjacent things and a reader who has used them will otherwise assume this page is out of date. Business Reports gained ASIN Performance Alerts (opens in a new tab), which notify you when there are significant changes in product performance, and Amazon separately introduced Product Performance Spotlight (opens in a new tab), a centralised dashboard for tracking ASIN performance across multiple metrics.
Those are real and they are useful. They are also a different shape of thing. They live on a dashboard rather than arriving on a phone, they detect that a metric moved rather than that a specific fee rate changed on a specific ASIN, and reading them still requires you to go and look. All of the data is in your account somewhere. Nothing pushes it to you at the moment it changes, which is the gap this page is about.
No proactive payout reconciliation
Nothing in the panel fires when a settlement posts for less than you expected, and nothing fires when Amazon moves part of one into an account-level reserve instead of paying it out. The figures are all published in your account, so the information is not hidden. It has to be gone and got. The available events are of the form "a payment happened"; the one that would actually change a decision is "a payment happened for less than it should have," and that is a comparison, not an event.
Why this gap specifically stings
A held payout is not itself announced anywhere in Seller Central's notification system. A seller planning a restock around an expected deposit finds out the reserve grew only when the smaller number lands, by which point the restock decision was already due.
Why the native system is scoped this way
None of this is a design failure so much as a design choice made for a different problem. Seller Central's notifications are built around discrete events with a clear trigger and a clear owner inside Amazon's systems: an order arrives, a return is requested, an outage starts. Where it goes quiet is the comparative facts. A fee recalculating, a reserve growing, a settlement landing light: each of those only means anything relative to a prior state or an expectation, and that comparison is not something an event-notification system computes on its own.
That is also, mechanically, the difference between an event feed and a monitoring system. One tells you something happened. The other tells you something happened that is different from what should have happened, which requires keeping the prior state around and diffing against it, continuously, per seller. Seller Central is the former. The gaps above are exactly the shape of problem the latter is for.
Closing the gap in practice
None of these three gaps require Amazon to change anything. They are closable today, just not by configuring a setting. Comparing fee estimates against their last known values, filtering order events down to the ones worth interrupting someone for, and having the settled figure and its period arrive on their own rather than being looked up are all things something else can do on a schedule.
On the last one, the useful move is getting the settled amount and the period delivered without asking, so the comparison against your own forecast is a thirty-second job rather than a login. The forecast is still yours. Nothing outside your own books knows what you were expecting.
Amazon's native notifications answer "what happened" and leave "is that normal" as homework. The homework is what catches a held payout, a mispriced fee, or a quiet reserve increase before it becomes next month's surprise.
Frequently asked questions
Does Amazon notify me when I make a sale?
Yes, by email: the "Sold, Ship Now" merchant order notification for seller-fulfilled orders, and FBA order notifications. What it is not is a dependable channel. Order emails stopping without warning is a standing forum complaint, an Amazon moderator answering one such report noted the preference itself can get reset or need re-verifying, and in April 2026 sellers reported the opposite failure: the emails switching themselves back on while the setting still showed disabled. It is also all-or-nothing, with no filtering by SKU, order value or fulfilment channel.
Does Amazon tell me when a fee changes on one of my listings?
No, and this is the most clear-cut gap. The Selling Partner API publishes roughly two dozen notification types and none of them is a fee change on an ASIN, whether a remeasurement, a category reclassification or a new surcharge. The closest match by name, FEE_PROMOTION, announces a fee discount rather than a fee change. The only way to catch one is to compare your own fee estimates against their last known values.
Does Amazon tell me when part of my payout is held back?
No. Nothing in the notification preferences panel fires on the event "a settlement posted for less than expected" or "the account-level reserve grew". Amazon publishes the numbers in your account, so the information exists, but surfacing it is a check you run rather than a message you receive.
Which notification categories does Seller Central actually have?
Amazon lists four as available regardless of selling plan: Order Notifications, Returns and Claims Notifications, Account Notifications, and Emergency Notifications. It is explicit that this is only part of the list and that what you see depends on your selling plan; most accounts also have listing, performance, report and deal sections. Each can be routed to its own email address and most can be switched off individually.
Is a third-party alert tool redundant with Seller Central notifications?
They overlap on order and account-health events, where Seller Central genuinely does send something. The gaps are structural rather than a matter of speed: no fee-change subscription at all, no filtering on the order notifications that do exist, and no reconciliation of a settlement against what you expected. Covering those is complementary to the native system, not a duplicate of it.
Sources
- 01Quick Tip: Set and edit Notification preferences (opens in a new tab) — Amazon Seller Forums, Jessica_Amazon_
- 02Notification Type Values (opens in a new tab) — Amazon Selling Partner API developer documentation
- 03Suddenly getting Merchant Order Notifications (Sold, Ship Now) (opens in a new tab) — Amazon Seller Forums, Seller_IlwjJKqpD81nL, 16 April 2026
- 04Not getting order emails since 8:37am EST 5/04/2026 (opens in a new tab) — Amazon Seller Forums, Seller_8gFZInPX0msAL, 5 May 2026
- 05Set Up ASIN Performance Alerts to Proactively Monitor Your Business (opens in a new tab) — Amazon Seller Forums, Indy_Amazon, 30 October 2025
- 06Product Performance Spotlight: Your New Analytics Hub for ASIN Success (opens in a new tab) — Amazon Seller Forums, Michelle_Amazon, 7 October 2025
Get told automatically
Notifcentral pushes a notification when an Amazon settlement posts, carrying the settled amount and the period it covers. Paired with the held funds alert, it closes the loop on Amazon cash flow: you know what is being withheld, and you know when the rest actually arrives.
How payouts alerts work →notifcentral
Fee changes, buy box, listing issues, held funds, reimbursement recovery, payout confirmations - delivered to your phone before any of it costs you money.
Alerts
Compare
Guides
© 2026 Notifcentral