Automated Lavu POS Refund Exception Flags
Every morning, WebRun opens Lavu, reads all refunds processed the previous day, checks each against your amount and timing thresholds, logs every refund to Google Sheets, and posts any exceptions to Slack for the manager to review.
How do I automatically flag unusual refunds in Lavu POS each day?
WebRun reads every refund from Lavu each morning, checks each one against your amount and timing rules, logs the full list to a Google Sheet for a complete audit trail, and posts any exception to Slack for the manager. Unusual refunds are caught the next morning rather than discovered at month-end when patterns are harder to trace.
- Unusual refunds flagged the next morning, not at month-end review
- Complete refund audit trail built automatically in Google Sheets
- Manager sees only the exceptions, not every transaction
Built for restaurant managers · hospitality loss-prevention teams · restaurant owners · multi-unit restaurant operators
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
lavu.comin a real browser with your saved login - no setup, no API keys. -
1
Lavu - read all refunds processed yesterday
lavu.com
WebRun opens Lavu to read all refunds processed yesterday. - Open Lavu and navigate to the Refund or Payment Adjustments report for the previous day
- Capture each refund: employee, amount, item or order refunded, time, and reason code
- Flag any refund above the manager-set dollar threshold
- Flag any refund processed after closing hours or outside the allowed refund window
Done when All refunds from yesterday are captured and any exceptions are identified.
-
2
Google Sheets - log all refunds to running audit sheet
google.com
WebRun opens Google Sheets to log all refunds to running audit sheet. - Open the refund audit Google Sheet
- Append a row for each refund with date, employee, amount, reason code, and exception flag
- Mark flagged rows with a highlight so they are easy to spot in the running log
Done when All of yesterday's refunds are logged to the audit sheet with exception flags.
-
3
Slack - post flagged refund exceptions for manager review
slack.com
WebRun opens Slack to post flagged refund exceptions for manager review. - Post a Slack summary: total refund count, total refund value, and count of exceptions
- List each flagged refund with the employee name, amount, reason, and what rule triggered the flag
- If no exceptions are found, post a clean confirmation so the manager knows the check ran
Done when Refund exception flags are posted to Slack for the manager to review and 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
Does it reverse or modify any refunds it finds?
No. WebRun only reads and reports. It posts the flagged list to Slack for the manager to investigate and decide whether any follow-up action is needed.
What triggers a refund exception flag?
You configure the rules during setup: for example, any refund above $50, any refund processed after 11 PM, or any refund with a blank reason code. WebRun applies your rules every morning.
Where can I find the full refund history, not just the exceptions?
Every refund is logged to the Google Sheet each morning, including the ones that did not trigger a flag, so you have a complete audit trail for any time period.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.