Incidents
Incident types, lifecycle states, severity levels, and how to investigate and resolve incidents effectively.
Incidents are the core operational unit in Revnoxa. Every revenue-impacting event is represented as an incident - a structured record with a type, severity, status, affected ASIN, estimated revenue impact, and a complete timeline of every action taken.
Incident types
Listing Suppression - The listing is no longer buyable. Common causes include missing required attributes, policy violations, catalog data mismatches, and image compliance issues. This is typically the highest-urgency incident type because a suppressed listing generates zero revenue.
Buy Box Hijacker - An unauthorized third-party seller has listed against your branded ASIN and is winning the Buy Box. Revnoxa detects new competing offers, identifies unauthorized sellers, and surfaces them for action.
Out of Stock - Inventory has dropped to zero or fulfillment is blocked. Revnoxa detects both hard OOS (no inventory) and low-stock situations before you fully run out, giving your team time to restock before revenue impact starts.
Price Mismatch - The live price on an ASIN diverges from your expected price beyond your defined threshold. Can indicate a pricing error, an unauthorized seller undercutting you, or a repricing rule gone wrong.
Advertising Inefficiency - A campaign is overspending relative to the revenue it generates, or a high-performing campaign is being budget-capped during peak hours. See the Advertising Efficiency section for details.
SLA Breach - An open incident has exceeded its defined response or resolution time window. Created automatically to escalate incidents that are not being worked.
Incident lifecycle
Detected → the incident is created automatically. Acknowledged → a team member has confirmed and taken ownership. Investigating → root cause analysis is underway. Remediating → a recovery action has been initiated. Pending Approval → the proposed action is waiting for authorization. Resolved → the recovery action has been executed and verified. Closed → the incident is archived.
Every state transition is logged with a timestamp and the name of the team member who acted.
Working an incident
Click any incident to open the detail view. You'll see the incident summary, affected ASIN details, current listing status, the full event timeline, and available actions. The Recommended Action panel at the top suggests the most appropriate next step based on the incident type and current state.
To acknowledge an incident, click "Acknowledge." To add a note for your team, use the note field in the timeline. To propose a remediation action, click the relevant action button - the options shown depend on the incident type and your plan.
Incident detail tabs
Summary - incident overview, impact estimates, and recommended action. Timeline - full chronological log of every event, action, note, and state change. Verification - live verification of whether the fix has taken effect on Amazon. Notifications - history of all alerts sent for this incident.