Automated Outbound Feed Load Tracking
Every evening, WebRun opens Ceres, reads the day's outbound feed and grain shipments, applies each load to its sale contract or feed order, logs tons, destination, and carrier into a Google Sheets shipping register, and sends a Telegram recap of what shipped and which sale contracts are now closer to filled.
How do I track outbound feed loads against their sale contracts?
Every evening, WebRun opens Ceres and reads the day's outbound feed and grain shipments, applying each load to its sale contract or feed order. It logs tons, destination, and carrier into a Google Sheets shipping register, then sends a Telegram recap of what shipped and which sale contracts moved closer to filled.
- Every outbound load is applied to its contract the day it ships
- Tons, destination, and carrier are logged in one shipping register
- Sale contracts falling behind schedule are called out for you to chase
Built for grain elevators · feed mills · grain operations teams · country elevators
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.verticalsoftware.netin a real browser with your saved login - no setup, no API keys. -
1
Vertical Software Ceres - read outbound shipments
verticalsoftware.net
WebRun opens Ceres to read and apply the day's outbound loads. - Open Ceres and list the day's outbound feed and grain shipments
- Apply each load to its sale contract or feed order and update the balance
- Capture net tons, grain or ration, destination, and carrier for each load
Done when Every outbound load is applied to its contract and captured.
-
2
Google Sheets - log the shipping register
google.com
WebRun logs each outbound load into the Google Sheets shipping register. - Open the shipping register and add a dated row per outbound load
- Record tons, grain or ration, destination, carrier, and the contract applied
- Keep a running filled-versus-remaining figure for each sale contract
Done when Every outbound load is logged in the shipping register.
-
3
Telegram - recap what shipped
telegram.org
WebRun sends the day's outbound shipping recap to Telegram. - Send a recap of tons shipped today by grain and destination
- Show which sale contracts moved closer to filled and which are behind
- Keep the recap internal to the operations team, no customer contact
Done when The team has today's outbound shipping recap in Telegram.
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
Is it safe to run unattended?
Yes. This tracker only reads outbound loads in Ceres, writes an internal Google Sheets register, and sends a Telegram recap. It contacts no customer and issues no shipping document on its own, so it is safe to run every night.
How does it match a load to a sale contract?
It reads the destination, grain, and order reference on each outbound ticket in Ceres and applies the load to the matching sale contract or feed order, updating the filled and remaining tons.
Can it tell me which sale contracts are behind?
Yes. The register keeps a filled-versus-remaining figure per contract, and the Telegram recap calls out any sale contract falling behind its shipping schedule so you can chase transport.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.