Automated Vendor Manifest Tracking
Every morning, WebRun opens METRC, pulls all incoming transfer manifests scheduled or in transit for the current day, logs each one to Google Sheets with vendor, expected quantities, and ETAs, and posts a receiving task list to Slack so your team is fully prepared before delivery vehicles arrive.
How do I track incoming METRC transfer manifests for my dispensary?
WebRun opens METRC each morning and pulls all incoming transfer manifests scheduled for the day, logging vendor details, expected quantities, and ETAs to Google Sheets. It then posts a clear receiving task list to Slack so your staff knows exactly what to prepare for before the first delivery arrives.
- Receiving team is prepared before the first delivery arrives each morning
- All incoming manifest details are logged automatically in Google Sheets
- Compliance staff are reminded to accept each transfer in METRC
Built for dispensary receiving staff · inventory managers · compliance officers · cannabis retail operators
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
ca.metrc.comin a real browser with your saved login - no setup, no API keys. -
1
METRC - pull incoming manifests
WebRun opens METRC to pull incoming manifests. - Open METRC and navigate to the Incoming Transfers section
- Filter for transfers with an estimated delivery date of today or marked as in transit
- Capture the transfer ID, vendor name, licence number, expected package count, product categories, and estimated arrival window for each manifest
Done when All incoming manifests scheduled for today are captured with vendor and quantity details.
-
2
Google Sheets - log manifest details
WebRun opens Google Sheets to log manifest details. - Open the manifest tracking sheet in Google Sheets
- Append each incoming manifest as a new row with date, transfer ID, vendor, expected quantities, and ETA
- Mark each row as pending until the receiving team confirms acceptance in METRC
Done when All today's incoming manifests are logged in the sheet with pending status.
-
3
Slack - post receiving task list
WebRun opens Slack to post receiving task list. - Post a receiving task list to the operations Slack channel listing each expected delivery with vendor, product categories, and ETA
- Flag any manifest with a large expected quantity or a first-time vendor for extra attention
- Remind the receiving team to verify and accept each transfer in METRC upon arrival
Done when Today's receiving task list is posted to Slack before the first expected delivery window.
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 accept or confirm transfers in METRC automatically?
No. WebRun only reads and surfaces incoming manifest data for your team's preparation. Accepting a transfer in METRC is a regulated action that must be completed manually by a licensed employee after physically verifying the delivery.
What if a delivery time changes after the morning run?
WebRun pulls a fresh METRC snapshot each morning. If a delivery is rescheduled mid-day, the next morning's run will reflect the updated ETA. For urgent changes, your vendor or driver should contact the store directly.
Can it track outgoing transfers too?
The default workflow focuses on incoming deliveries to support receiving staff. Outgoing transfer tracking can be added as a separate workflow using the same METRC connection and Google Sheet structure.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.