Automatic Vendor Price Increase Tracking
Every morning, WebRun scans Gmail for manufacturer price increase notices, looks up each affected item's current cost and sell price in Epicor Eclipse, and posts purchasing and the affected sales reps a Slack digest grouped by vendor and effective date.
How do I track manufacturer price increases before they hit my margins?
WebRun scans Gmail every morning for manufacturer price increase notices, looks up each affected item's current cost and sell price in Epicor Eclipse, and posts purchasing and the affected sales reps a Slack digest grouped by vendor and effective date. It only flags items for review, it never changes pricing on its own, so margin protection stays a human decision.
- Price increases get caught the morning they land instead of after a margin-losing sale
- Purchasing sees every affected SKU and open quote in one digest instead of hunting through email
- No price change is ever applied without a buyer reviewing it first
Built for electrical distributors · purchasing and buying teams · branch pricing managers · outside sales reps
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
mail.google.comin a real browser with your saved login - no setup, no API keys. -
1
Gmail - scan for vendor price increase notices
gmail.com
WebRun opens Gmail to scan for vendor price increase notices. - Scan the inbox and vendor folders for price increase letters and attachments from manufacturers
- Extract the vendor, effective date, and affected product lines or SKUs from each
- Skip newsletters and anything that isn't an actual pricing notice
Done when Every price increase notice received is logged with its vendor and effective date.
-
2
Epicor Eclipse - flag the affected items and cost
epicor.com
WebRun opens Epicor Eclipse to flag the affected items and cost. - Look up each affected SKU's current cost and sell price in Eclipse
- Note which open quotes and contract-priced customers reference those items
- Flag the items for your buyer to update. WebRun does not change pricing on its own
Done when Every affected SKU is flagged with its current cost, sell price, and any open quotes touching it.
-
3
Slack - digest the increases to the team
slack.com
WebRun opens Slack to digest the increases to the team. - Post a digest to the purchasing and pricing channel, grouped by vendor and effective date
- Tag the reps whose open quotes are affected
- Put increases taking effect soonest at the top
Done when Purchasing and the affected reps have today's price increase digest in Slack.
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 change prices in Eclipse automatically?
No. WebRun only flags the affected items with their current cost and sell price for your buyer to update. It never changes pricing on its own.
How does it find price increase notices in a busy inbox?
It reads the subject line, sender, and attachments of incoming mail each morning for manufacturer pricing letters, and skips general newsletters and unrelated vendor mail.
What about quotes that already went out at the old price?
It flags any open quote referencing an affected item, so your rep knows to reprice or honor it before the increase takes effect.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.