Automated Clover Refund and Void Anomaly Alerts
Every morning, WebRun opens Clover, scans yesterday's refunds and voids for anomalies such as high dollar amounts, after-hours activity, or repeated employee actions, and posts a prioritised flag list to Slack for your review.
How do I automatically detect suspicious refunds and voids in Clover?
WebRun scans your Clover transactions every morning, flags refunds and voids that exceed your dollar threshold, occur after hours, or cluster around a single employee, and posts a prioritised list to Slack. Managers review the list and decide whether to investigate, stopping potential losses before they accumulate.
- Unusual refunds and voids caught before they are missed
- Managers get a daily anomaly list without pulling reports manually
- Pattern detection across employees helps identify training gaps or misconduct
Built for restaurant owners · retail managers · Clover merchants · loss prevention teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.clover.com/dashboardin a real browser with your saved login - no setup, no API keys. -
1
Clover - scan refunds and voids for anomalies
clover.com
WebRun opens Clover to scan refunds and voids for anomalies. - Open Clover Dashboard and navigate to Transactions
- Filter yesterday's transactions to refunds and voids
- Flag any single refund or void above your configured dollar threshold
- Flag any refund or void processed outside normal business hours
- Flag any employee with more than your configured number of voids in the period
Done when All anomalous refunds and voids from yesterday are identified.
-
2
Slack - post the anomaly flag list
slack.com
WebRun opens Slack to post the anomaly flag list. - Build a concise list of flagged transactions with employee name, amount, time, and reason code
- Sort by dollar amount descending
- Post to the manager or owner Slack channel for review
Done when The anomaly list is posted to Slack and ready for manager action.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it automatically reverse or cancel any flagged transactions?
No. WebRun only reads and reports. Every flagged refund or void is posted to Slack for a manager to review and decide whether action is needed. Nothing is reversed automatically.
How do I set the dollar threshold for flagging?
You configure the threshold during setup. Common starting points are any single refund over fifty dollars or any void over twenty-five dollars, but you can choose amounts that fit your business.
What if all refunds yesterday were legitimate?
WebRun posts the list regardless, noting that no anomalies were found. The clean result is itself a useful daily confirmation that nothing unusual occurred.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.