Revenue Signals

Revenue signals are the data streams Revnoxa pulls from your connected Amazon accounts to detect incidents. Understanding what's monitored helps you interpret incidents and configure detection rules more effectively.

What Revnoxa monitors

Listing status - whether each ASIN is active, suppressed, or in a degraded state. Suppression events are detected as quickly as possible after they occur on Amazon's side.

Pricing - the live price on each ASIN compared to your expected price range. Price changes are monitored continuously.

Inventory - stock levels and fulfillment availability across Amazon's network. Revnoxa tracks both total inventory quantity and whether that inventory is actually fulfillable.

Buy Box offers - who holds the Buy Box for each ASIN, at what price, and whether there are new unauthorized sellers listing against your ASINs.

Advertising metrics - campaign spend, sales attributed, impressions, clicks, conversion rate, ACOS, and ROAS - pulled daily from the Amazon Advertising API (requires separate Advertising credentials).

FBA dimensions - the dimensions and weight Amazon has on file for each ASIN, compared against your expected values.

How data gets into Revnoxa

Revnoxa combines two data collection approaches. Scheduled polling retrieves current state for key signals at defined intervals - listing status, pricing, inventory, and Buy Box data. Report ingestion requests Amazon's own aggregated reports for bulk historical data like sales velocity, which is used for revenue impact estimation.

Revenue impact estimation

Every incident includes an estimated revenue impact per day. This is derived from the ASIN's recent sales performance and the nature of the incident - a fully suppressed listing with zero sales is estimated differently from a listing that still sells but has lost the Buy Box to a competitor. Impact estimates drive severity classification, ensuring your team always works the highest-value problems first.