Automated ShipHero Inbound Receiving Digest
Every morning, WebRun opens ShipHero, collects all purchase order receipts logged the prior day, totals units received by SKU and supplier, flags any receipts with quantity discrepancies vs. the PO, and sends a concise digest to the operations Telegram group.
How do I automatically get a daily inbound receiving summary from ShipHero?
WebRun opens ShipHero each morning, pulls all purchase order receipts from the prior day, totals units by SKU and supplier, flags any lines where quantity received differs from the PO, and sends a concise digest to the operations Telegram group. Teams know what arrived and what needs follow-up before the floor opens.
- The ops team knows what arrived the prior day before the floor opens
- PO quantity discrepancies are flagged before inventory is released to pick locations
- Receiving activity is summarized without any manual ShipHero report running
Built for warehouse receiving teams · operations managers · purchasing teams · ShipHero users
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
app.shiphero.comin a real browser with your saved login - no setup, no API keys. -
1
ShipHero - collect prior day PO receipts and discrepancies
shiphero.com
WebRun opens ShipHero to collect prior day PO receipts and discrepancies. - Open ShipHero and navigate to the Receiving report
- Filter to all purchase orders received in the prior calendar day
- Capture PO number, supplier, SKU, quantity ordered, and quantity received for each line
- Flag any line where quantity received differs from quantity ordered by more than your tolerance
Done when All prior-day receipts are listed with total units by SKU, supplier, and any discrepancy flags.
-
2
Telegram - send inbound receiving digest to ops group
telegram.org
WebRun opens Telegram to send inbound receiving digest to ops group. - Format the digest with total POs received, total units, and a line per supplier with their SKU count
- Call out any discrepant receipts with PO number and variance
- Send the digest to the operations Telegram group
Done when The ops Telegram group has the prior day's receiving summary with discrepancies called out.
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
Does it contact the supplier if a receipt is short?
No. Supplier contact for short receipts is drafted and queued for a buyer to review and send. WebRun only posts the internal receiving summary to the ops Telegram group.
What counts as a discrepancy?
A discrepancy is any line where the quantity received in ShipHero differs from the PO quantity by more than a tolerance you set during setup, typically 1 unit or a small percentage.
What happens on days when no inventory is received?
WebRun sends a brief Telegram note confirming no receipts were logged in ShipHero the prior day, so the ops team knows the run completed and no inbound activity was missed.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.