Rules Engine

The Rules Engine defines what Revnoxa watches for and what happens when it finds a problem. Rules determine when incidents are created, their type and severity, and what automated actions follow.

Rule templates

Revnoxa ships with pre-built templates for the most common incident scenarios. Go to Rules in the sidebar to see all available templates. Activate the ones relevant to your business - you don't need to build rules from scratch.

Available templates: Listing Suppression Detection, Buy Box Hijacker Detection, Out of Stock Alert, Low Stock Alert, Price Mismatch Detection, Advertising ACOS Threshold, Advertising ROAS Degradation, Budget Cap Alert, SLA Breach Escalation.

Customizing thresholds

After activating a template, click on the rule to open the editor. You can adjust the thresholds that control when an incident is created. For example: on Price Mismatch, set the minimum deviation percentage that triggers an alert. On Low Stock, set the inventory quantity that triggers an early warning before you go fully OOS.

Dry-run mode

Before enabling a rule in production, use dry-run mode to preview what incidents it would have created - without actually creating them or sending any notifications. Dry-run results show the incidents that would have fired, the ASINs affected, and the severity levels that would have been assigned.

Use dry-run to validate that your thresholds are right before going live: too sensitive (creating noise) or too loose (missing real problems) are both visible in the dry-run preview.

Enabling and disabling rules

Rules can be toggled on or off at any time. Disabling a rule stops new incidents from being created - it does not close any existing open incidents. Re-enabling a rule resumes detection immediately.