DMSi Agility Automated Order Exception Flags
Every morning, WebRun opens DMSi Agility and scans open orders for exceptions: pricing overrides requiring approval, margins below your threshold, missing delivery or will-call details, and orders held at credit. It posts a categorized exception worklist to Slack and logs every item in Google Sheets for tracking.
How do I automatically flag problem orders in DMSi Agility before they ship?
WebRun scans DMSi Agility every morning for open orders with pricing overrides, margins below your threshold, missing delivery or will-call details, and credit holds. It posts a categorized exception worklist to Slack and logs every item in Google Sheets so your ops team can resolve each issue before the order ships.
- Problem orders are caught and flagged before they reach the shipping dock
- Pricing overrides and low-margin deals get human review every morning
- Credit-hold orders are visible to the team before the customer calls asking for status
Built for lumber dealers · building materials distributors · operations managers · inside sales supervisors
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.dmsi.comin a real browser with your saved login - no setup, no API keys. -
1
DMSi Agility - scan open orders for pricing, margin, and delivery exceptions
dmsi.com
WebRun opens DMSi Agility to scan open orders for pricing, margin, and delivery exceptions. - Open DMSi Agility and navigate to open sales orders
- Flag orders with a manual pricing override applied by a rep
- Flag orders where gross margin is below the company threshold
- Flag orders missing delivery date, delivery address, or will-call confirmation
- Flag orders on credit hold
Done when All exception orders are identified and categorized by exception type.
-
2
Google Sheets - log exception worklist with order details
google.com
WebRun opens Google Sheets to log exception worklist with order details. - Log each exception order as a new row with the order number, customer, exception type, and assigned rep
- Stamp the date and mark resolved rows as closed when the issue is fixed
Done when All exception orders are logged in the worklist tracker with their category.
-
3
Slack - post categorized exception list to ops team
slack.com
WebRun opens Slack to post categorized exception list to ops team. - Post a categorized exception list to the operations Slack channel
- Group by exception type: pricing overrides, low-margin, missing delivery info, credit holds
- Include order number, customer name, and the specific issue for each line
Done when Ops team has today's exception worklist in Slack, grouped by issue type.
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 change or cancel any orders automatically?
No. WebRun only reads and flags. Every exception goes to the Slack worklist for a human to review and resolve. No order is modified, cancelled, or released without your approval.
What margin threshold does it use to flag low-margin orders?
You set the threshold during setup, and WebRun applies it consistently on every run. You can adjust it at any time without changing the automation logic.
What counts as a missing delivery detail?
Orders where the requested delivery date, ship-to address, or will-call confirmation is blank are flagged. Orders that are complete but simply scheduled for a future date are not flagged.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.