Automated Sawyer Robotics Kit Inventory Tracking
Every Monday, WebRun opens Sawyer, reads this week's robotics class rosters, checks each class's kit requirements against the stock counts logged in Google Sheets, and posts a Slack list of exactly which parts are running low before this week's classes.
How do I track robotics kit inventory before classes run short on parts?
WebRun checks your Sawyer class rosters every Monday, works out how many battery packs, sensor boards, and controller kits this week's robotics classes will use, and compares that against your Google Sheet stock counts. It then posts a Slack list of exactly which parts are running low, so your team can reorder before a class runs short.
- Low stock on a robotics part gets flagged before it stalls a class
- Kit counts stay accurate against live Sawyer enrollment every week
- No purchase happens without a person deciding to order it
Built for STEM class studio owners · robotics program directors · coding and robotics franchise operators · after school program coordinators
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.hisawyer.comin a real browser with your saved login - no setup, no API keys. -
1
Sawyer - read this week's class rosters
hisawyer.com
WebRun opens Sawyer to read this week's class rosters. - Open Sawyer and pull the enrolled headcount for every robotics class running this week
- Match each class to its kit recipe, the battery packs, sensor boards, motors, and controller kits it needs per student
- Total the parts required across every class for the week
Done when Every robotics class this week has its parts requirement totaled.
-
2
Google Sheets - check kit stock against demand
google.com
WebRun opens Google Sheets to check kit stock against demand. - Open the kit inventory sheet and read the current on-hand count for each part
- Subtract this week's total demand from on-hand stock
- Update the sheet with the projected count remaining after this week's classes
Done when The inventory sheet reflects projected stock after this week's classes for every part.
-
3
Slack - flag what's running low
slack.com
WebRun opens Slack to flag what's running low. - Post a list to the ops channel of any part projected to fall below its reorder threshold
- Sort the list by how many classes away the shortage is
- Leave ordering to your team. WebRun never places a purchase order
Done when Your team has this week's low-stock list in Slack before classes run short.
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 order replacement parts automatically?
No. WebRun only flags what's projected to run low and by when. Your team decides what to order, how much, and from where. Nothing is purchased automatically.
How does it know how many parts each class needs?
From the kit recipe you keep in the Google Sheet, the parts list per student for each robotics class. WebRun multiplies that by the enrolled headcount it reads from Sawyer.
What if we get a shipment mid week?
Update the on-hand count in the Google Sheet and the next Monday run picks up the new total automatically. Nothing needs to be reset or reconfigured.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.