DMSi Agility Automated Shingle Lot Match Check
Every hour, WebRun opens DMSi Agility, checks the lot or run numbers recorded against every shingle bundle staged for an order, logs any order with mixed lots in Google Sheets, and posts a Slack alert to the warehouse team so a mismatched pallet gets swapped before it loads onto the truck.
How do I catch shingle lot or color mismatches before an order ships?
Every hour, WebRun opens DMSi Agility and checks the lot or run numbers recorded against every shingle bundle staged for an order. It logs any order pulling from more than one lot in Google Sheets and posts a Slack alert to the warehouse, so a color-mismatched pallet gets swapped before the truck ever loads.
- Color banding complaints drop because mismatched lots are caught before loading
- Warehouse staff get a specific swap instruction, not a vague reshuffle
- Every staged order is checked hourly, not just at random spot checks
Built for roofing and siding distributors · warehouse and staging teams · branch quality control · will call and shipping staff
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 - check lot numbers on staged bundles
dmsi.com
WebRun opens DMSi Agility to check lot numbers on staged bundles. - Open DMSi Agility and pull the staged order list with bundle lot or run numbers recorded
- Compare the lot numbers across every bundle within the same order and product
- Flag any order where the shingle bundles span more than one lot
Done when Every staged order has its shingle lot numbers checked for a match.
-
2
Google Sheets - log orders with mixed lots
google.com
WebRun opens Google Sheets to log orders with mixed lots. - Log each flagged order with the product, quantity, and the mismatched lot numbers found
- Note which bundles are from which lot so the warehouse knows what to pull instead
- Mark the row resolved once the pull is corrected
Done when Every mixed lot order is logged with the detail needed to fix the pull.
-
3
Slack - alert the warehouse to swap the pull
slack.com
WebRun opens Slack to alert the warehouse to swap the pull. - Post an alert to the warehouse channel for each order with a lot mismatch
- Include the order number, product, and the lot numbers involved
- Ask the team to pull the order again from a single lot before the truck loads
Done when The warehouse has a Slack alert for every order that needs a corrected pull.
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
Why does a shingle lot mismatch matter?
Shingles from different production lots can vary slightly in shade, and mixing lots on one roof shows up as visible color banding once installed. WebRun catches the mismatch while the order is still on the dock, not after it is on the roof.
Does it stop the order from shipping?
No. WebRun only flags the mismatch in Google Sheets and Slack. A person on the warehouse team decides whether to pull the order again from a single lot or ship it as is, for example when the customer has approved a lot variance.
How far back does it check for lot numbers?
It reads the lot or run numbers recorded in DMSi Agility for whatever is currently staged, so it checks every order as it moves into staging, not historical shipments already delivered.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.