Reports
How to generate weekly and monthly reports, what each metric means, and how to export data for your team or clients.
Revnoxa generates structured reports summarizing your revenue incident activity, team performance, and marketplace health. Reports are available on-screen and as CSV or PDF exports.
Generating a report
Go to Reports in the sidebar and click "Generate Report." Select the period - Weekly (last 7 days) or Monthly (last 30 days) - and click Generate. The report appears in your history within seconds. You can generate as many reports as you need and keep the full history.
What the report includes
Revenue at Risk - total estimated daily revenue impact of all open incidents at the time of report generation. A decreasing trend means your team is closing incidents faster than new ones appear.
Revenue Recovered - total revenue protected through incidents resolved during the report period. This is your team's measurable business impact.
SLA Compliance Rate - percentage of incidents acknowledged and resolved within their defined time windows. Above 90% is considered strong performance.
Incidents by Type - breakdown of how many incidents were created, by type (suppression, OOS, hijacker, price mismatch, etc.). Useful for identifying which problems are most frequent in your catalog.
Time to Detect - average time between an incident starting and Revnoxa detecting it.
Time to Resolve - average time from detection to resolution.
Automation Rate - percentage of remediation actions executed automatically without manual steps. A rising automation rate means your team is spending less time on repetitive actions.
Month-over-Month Comparison - the monthly report includes a comparison to the prior month, showing whether revenue protection, SLA compliance, and resolution speed are improving.
Exporting reports
Click Export on any report to download it as a CSV (for Excel or Google Sheets analysis) or as a formatted PDF (for sharing with leadership or clients). The CSV export includes one row per incident with all fields: ASIN, type, severity, detected at, resolved at, revenue impact, resolution details, and team member who resolved it.