Automated Katana BOM Cost Change Alerts
Every night, WebRun opens Katana, reviews product recipes and the average cost of their materials, spots components whose cost has moved since yesterday, recalculates the affected product build costs, logs the changes to a Google Sheet, and alerts your team on Slack to the biggest swings.
How do I get alerted when a product's build cost changes in Katana?
Every night, WebRun opens Katana and reviews product recipes and the average cost of their materials, spotting components whose cost moved since the last run. It recalculates the affected build costs, logs the changes to a Google Sheet, and alerts your team on Slack to the biggest swings, so a rising component price never quietly eats your margin.
- Rising component costs surface the same night
- Build cost is recalculated per affected product
- Margin erosion is caught before the next quote
Built for cost accountants · production managers · small manufacturers · operations leads
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
factory.katanamrp.comin a real browser with your saved login - no setup, no API keys. -
1
Katana - check recipe component costs
WebRun reviews Katana product recipes for moved component costs. - Open Katana and go to Items, then review each product's recipe and its materials
- Capture the current average cost of each component and the product's total build cost
- Compare against yesterday's costs and flag components that moved beyond your threshold
Done when Every product recipe has been checked and moved component costs are flagged.
-
2
Google Sheets - log cost changes
WebRun logs component cost moves and recalculated build costs. - Open the BOM cost tracking sheet
- Log each component whose cost moved with the old cost, new cost, and percent change
- Recalculate and record the new total build cost for every affected product
Done when Cost changes and recalculated build costs are recorded in the sheet.
-
3
Slack - alert on the biggest swings
WebRun alerts your team to the biggest build-cost swings. - Post an alert to your team channel naming the products whose build cost moved most
- Show the component behind each swing and the percent change
- Leave any price update to your team. Never change a cost or a sell price in Katana on its own
Done when Your team has tonight's build-cost change alert 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 my costs or sell prices?
No. WebRun only reads component costs and recalculates build costs to alert you. Updating a material cost, a recipe, or a product sell price stays with your team inside Katana.
How does it detect a cost change?
It reads the current average cost of each material in your Katana recipes and compares it against the prior run, flagging any component that moved beyond the percent threshold you set.
Which products does it recalculate?
Only the products whose recipe contains a moved component. WebRun rebuilds the total build cost for each affected product so you see the margin impact, not just the raw material change.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.