Alerts inbox
Every alert here was raised by a rule on the Automations page, not by a person watching a dashboard. Each one carries the dollar figure at stake and, where a deadline applies, the date after which the money is gone.
Total alerts
186
Trailing 30 days
Unactioned
76
Status new
Critical open
53
Needs a name against it
Exposure open
$1.6M
Sum of unactioned impact
Acknowledged
53
Owner assigned
Resolved
25
Closed out
Emails delivered
169
Digest sends
Median time to ack
4.2h
Critical alerts
53 critical alerts have no owner carrying $643,942 of exposure. Critical means one of three things: a claim window closing, a PO acknowledgement clock running out, or a node that will refuse inbound freight. All three are cheap to fix today and expensive to fix next week.
Alert volume by ruleTrailing 30 days, ranked by dollar impact
| Rule | Alerts | $ impact | |
|---|---|---|---|
| Buy box loss on a top-200 ASIN | 22 | $2.2M | Filter |
| Listing suppressed or main image missing | 20 | $915K | Filter |
| Chargeback dispute deadline inside 7 days | 26 | $343K | Filter |
| Vendor PO acknowledgement SLA at risk | 18 | $206K | Filter |
| Reimbursement window expiring | 30 | $182K | Filter |
| Stockout imminent: under 10 days, no inbound | 46 | $137K | Filter |
| FC capacity breach: warehouse overfill risk | 7 | $26K | Filter |
| Overstock: days of supply above ceiling | 17 | $16K | Filter |
By severityAll statuses
Alert queue0 of 186 alerts
No alerts match these filters.
In the live build an alert also carries a one-click action: acknowledge, assign, snooze with a reason, or open the underlying Amazon case. Acknowledgement writes to Supabase and stops the digest from re-sending, which is what keeps a daily email from becoming background noise. Coverage of the rule set and the 93% of rules currently enabled is on Automations.