Automated ShipHero Damaged Goods Reports
Every morning, WebRun opens ShipHero, pulls all items flagged as damaged in the prior day, totals them by SKU and damage type, posts a summary to the Slack ops channel, and appends the detail rows to a running Google Sheet log for finance and insurance tracking.
How do I automatically track and report warehouse damaged goods from ShipHero?
WebRun opens ShipHero each morning, pulls all items flagged as damaged in the prior day, posts a total-units-and-cost summary to Slack, and appends each damage event to a running Google Sheet. Supervisors see the daily impact instantly while finance builds a clean log for write-offs and carrier claims.
- Daily damage totals are visible in Slack before the morning ops review
- A running Google Sheet log is always ready for finance write-offs and carrier claims
- Damage spikes by SKU or location are easy to spot from the accumulated log
Built for warehouse supervisors · operations managers · finance teams · 3PL 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
app.shiphero.comin a real browser with your saved login - no setup, no API keys. -
1
ShipHero - pull prior day damaged goods records
shiphero.com
WebRun opens ShipHero to pull prior day damaged goods records. - Open ShipHero and filter inventory transactions to damaged status for the prior calendar day
- Capture SKU, quantity, damage type, location, and date for each damaged item
- Total the units and estimated cost by SKU
Done when All prior-day damaged goods records are captured with SKU, quantity, cost, and damage type.
-
2
Slack - post daily damage summary to ops channel
slack.com
WebRun opens Slack to post daily damage summary to ops channel. - Post a brief summary to the ops Slack channel: total units damaged, total estimated cost, and top SKUs by damage count
- If there are zero damage events, post a clear-all-clear note and stop
Done when The ops channel has today's damage summary before the morning shift review.
-
3
Google Sheets - append detail rows to running damage log
google.com
WebRun opens Google Sheets to append detail rows to running damage log. - Open the Damage Log Google Sheet
- Append each damaged item as a new row with date, SKU, qty, cost, damage type, and location
- This running log supports monthly finance write-offs and carrier claim documentation
Done when All prior-day damage events are appended to the Google Sheet running log.
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 file carrier damage claims automatically?
No. Carrier claims involve external communications and money, so WebRun logs the damage data and drafts a claim summary for human review. A manager submits the actual claim.
Can it distinguish between inbound receiving damage and warehouse handling damage?
Yes, as long as damage types are recorded in ShipHero. WebRun captures the damage type field from ShipHero and includes it in both the Slack summary and the Sheet log.
How is the Google Sheet log useful for finance?
The running Sheet accumulates daily damage rows that finance can use for monthly inventory write-offs, insurance reporting, and carrier claim evidence without any manual data entry.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.