Automated Concrete Ticket Sync
Every few minutes, WebRun opens CommandBatch, reads each newly batched ticket, finds the matching order in Dispatch360, writes a delivery record with mix design, yardage, and batch time, and logs any ticket it could not match to a Google Sheet for review.
How do I sync batch plant tickets into delivery records automatically?
WebRun keeps your delivery records in sync with the plant. Every ten minutes it reads new tickets in CommandBatch, matches each to its Dispatch360 order by job, truck, and time, and writes a delivery record with the mix, yardage, and batch time, logging any unmatched ticket to a sheet for dispatch to resolve.
- Delivery records stay current within minutes of each batch
- Unmatched tickets surface for review instead of going missing
- No ticket is counted twice against an order
Built for ready mix producers · concrete dispatchers · batch plant operators · aggregate suppliers
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.dispatch360.comin a real browser with your saved login - no setup, no API keys. -
1
CommandBatch - read new batch tickets
commandalkon.com
WebRun opens CommandBatch to read new batch tickets. - Open CommandBatch and list tickets batched since the last run
- Capture ticket number, mix design, yardage, plant, and batch time
- Skip tickets already synced this shift
Done when Every new batch ticket is read with its mix, yardage, and time.
-
2
Dispatch360 - match ticket to the order
dispatch360.com
WebRun opens Dispatch360 to match each ticket to its order. - Open Dispatch360 and find the order matching each ticket by job, truck, and time window
- Write a delivery record with the mix, yardage, and batch time attached
- Mark the order line as batched so it is not counted twice
Done when Each matched ticket has a delivery record on its Dispatch360 order.
-
3
Google Sheets - log any unmatched tickets
google.com
WebRun opens Google Sheets to log any unmatched tickets. - Log any ticket that had no clear order match to a review sheet
- Note the ticket number, plant, and the likely job so dispatch can resolve it
- Keep matched tickets out of the sheet to keep it short
Done when Unmatched tickets sit in the review sheet with enough detail to resolve.
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 my batch plant data?
No. WebRun only reads tickets from CommandBatch. It writes the matched delivery record into Dispatch360 and never edits the source ticket at the plant.
What happens to a ticket it cannot match?
It goes to a Google Sheet review list with the ticket number, plant, and likely job, so dispatch can assign it by hand instead of it being lost or double counted.
How does it avoid syncing the same ticket twice?
It marks each order line as batched in Dispatch360 and skips tickets already synced this shift, so a repeated run never creates a duplicate delivery record.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.