Whiskey Systems Automated Order Exception Flagging
Every morning, WebRun opens Whiskey Systems, reviews all open sales orders for exceptions such as missing label approvals, invalid shipping addresses, or insufficient finished-goods inventory, logs each problem to a Google Sheet, and posts a triage list to Slack so the team can fix issues before orders ship.
How do I automatically catch problem orders before they ship from my distillery?
WebRun scans all open Whiskey Systems sales orders every morning, flags exceptions like missing label approvals, short inventory, or bad shipping addresses, logs each to a Google Sheet, and posts a ship-date-ranked triage list in Slack so your team can fix problems before anything ships incorrectly.
- Problem orders caught every morning before they reach the shipping dock
- Team works a ranked triage list in Slack rather than hunting for issues manually
- Resolved exceptions are cleared automatically on the next run
Built for distillery operations managers · craft distillery fulfillment teams · head distillers · wholesale account managers
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
app.whiskeysystems.comin a real browser with your saved login - no setup, no API keys. -
1
Whiskey Systems - scan open sales orders for exceptions
whiskeysystems.com
WebRun opens Whiskey Systems to scan open sales orders for exceptions. - Open Whiskey Systems and navigate to the Finished Goods sales-orders view
- Filter for open orders scheduled to ship within the next 5 business days
- Check each order for exceptions: missing label approval, short inventory, unconfirmed shipping address, or missing compliance documentation
- Capture the order number, account name, exception type, and ship date for each flagged order
Done when Every open order with an exception is listed with the exception type and ship date.
-
2
Google Sheets - log order exceptions
google.com
WebRun opens Google Sheets to log order exceptions. - Open the Order Exception Log sheet
- Append each flagged order as a new row with today's date and the exception category
- Mark any order already logged that has since been resolved as cleared
- Sort rows by ship date, most urgent first
Done when The exception log is current and sorted by ship-date urgency.
-
3
Slack - post triage list to the team
slack.com
WebRun opens Slack to post triage list to the team. - Post the exception triage list to the distillery operations channel
- Lead with orders shipping within the next 2 days, then list all remaining exceptions
- Include order number, account name, exception type, and a direct note on what needs fixing
- Link to the full Google Sheet for the complete log
Done when The team has a ranked triage list in Slack with action items for every flagged order.
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 cancel or edit orders automatically?
No. WebRun only flags the exception and reports it. All order edits, holds, or cancellations are carried out by a human after reviewing the triage list.
What counts as an exception?
By default it flags missing label approvals, insufficient finished-goods inventory, unconfirmed shipping addresses, and missing compliance documents. You can add or remove exception types in your run settings.
What if an exception is resolved after the morning run?
The Google Sheet is marked cleared for any resolved orders on the next run. The Slack post is a point-in-time snapshot, so your team should mark items resolved in the sheet as they work through the list.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.