Wherefour Automated Order Exception Flagging
Every morning, WebRun opens Wherefour and reviews all open sales orders for exceptions, including orders past their promised ship date, lines with unassigned lots, quantity shortfalls against committed amounts, and orders missing required compliance documentation. It logs every exception with its order details to a Google Sheet for your operations team to triage and resolve.
How do I automatically flag order exceptions in my food manufacturing ERP?
WebRun reviews all open Wherefour sales orders each morning and flags exceptions including late shipments, unassigned lots, quantity shortfalls, and missing compliance documents. Each exception is logged with its details to a Google Sheet, color-coded by severity, so your operations team has a triage-ready list before the production day starts.
- Exceptions are caught before customers notice a problem
- Ops team has a color-coded triage sheet ready before the production day starts
- Resolved exceptions clear automatically so the sheet stays current
Built for food manufacturers · beverage producers · co-packers · operations managers · customer service 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
app.wherefour.comin a real browser with your saved login - no setup, no API keys. -
1
Wherefour - scan open orders for exceptions
wherefour.com
WebRun opens Wherefour to scan open orders for exceptions. - Open Wherefour and navigate to open Sales Orders
- Check each order for the following exception types: past promised ship date, lines with no lot assigned, committed quantity greater than available inventory, and missing certificate of analysis
- Capture order number, customer name, exception type, and affected line details for each flag
- Sort exceptions by severity: past-ship-date orders first, then quantity shortfalls, then missing documentation
Done when All open order exceptions are identified and categorized by type and severity.
-
2
Google Sheets - log flagged exceptions for ops triage
google.com
WebRun opens Google Sheets to log flagged exceptions for ops triage. - Open the designated Order Exceptions Google Sheet
- Append a new timestamped row for each exception with order number, customer, exception type, and details
- Highlight rows for past-ship-date exceptions in red for immediate visibility
- Clear rows from previous runs that are no longer exceptions in Wherefour
Done when The Order Exceptions sheet is updated with today's flags, color-coded by severity, and stale rows are cleared.
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 contact customers if their order is late?
No. WebRun logs exceptions to Google Sheets for your ops team to triage. It never contacts customers. Your team decides when and how to communicate delays.
Which exception types does it check for?
It checks for orders past their promised ship date, order lines with no lot assigned, committed quantities exceeding available inventory, and orders missing required compliance documentation like certificates of analysis.
What happens to rows from yesterday that are no longer exceptions?
Resolved exceptions are automatically cleared from the sheet each morning so the log reflects only current open issues, not historical ones.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.