PDI Technologies Automated Weekly Shrink Anomaly Detection
Every Monday, WebRun opens PDI Technologies, pulls the prior week's inventory variance report by product category for each location, compares shrink percentages against your baseline thresholds, flags any category or site where shrink is above normal, logs the detail to a Google Sheet, and posts a prioritized shrink anomaly report to your loss-prevention Slack channel so the team can investigate the highest-risk locations first.
How do I automatically detect shrink anomalies across my convenience store network?
WebRun opens PDI Technologies every Monday, pulls the prior week's inventory variance by product category for every location, and compares shrink percentages against your baselines. Above-threshold combinations are logged to a Google Sheet with color-coded severity, and a prioritized shrink anomaly report listing the top five risk sites is posted to your loss-prevention Slack channel.
- Above-baseline shrink is surfaced every Monday before it compounds another week
- Top five highest-risk sites are named and prioritized in the Slack report
- Persistent above-baseline patterns are tracked week-over-week in the same sheet
Built for c-store loss prevention teams · convenience store district managers · fuel retail operations directors
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
pditechnologies.com/increase-productivity/erp-back-officein a real browser with your saved login - no setup, no API keys. -
1
PDI Technologies - pull inventory variance report by category and location
pditechnologies.com
WebRun opens PDI Technologies to pull inventory variance report by category and location. - Open PDI Technologies and navigate to the Inventory Variance or Shrink report
- Pull the prior week's book inventory versus physical or system-on-hand count by product category at each location
- Calculate shrink percentage as the variance divided by expected inventory for each category-location combination
- Compare each percentage against your configured baseline shrink threshold per category
Done when Shrink percentage is calculated for every category at every active location, with above-baseline combinations identified.
-
2
Google Sheets - log shrink percentages and flag anomalies
google.com
WebRun opens Google Sheets to log shrink percentages and flag anomalies. - Open the shrink tracking sheet and add a new weekly tab named for the week ending date
- Write one row per category-location combination with columns for category, site, expected, actual, shrink units, and shrink percentage
- Highlight rows in red where shrink exceeds the category baseline and yellow where it is within 25% of the threshold
- Add a summary row for each location with its total shrink percentage across all categories
Done when The weekly shrink sheet is populated with all category-location rows, color-coded by severity.
-
3
Slack - post prioritized shrink anomaly report to loss-prevention channel
slack.com
WebRun opens Slack to post prioritized shrink anomaly report to loss-prevention channel. - Format a Slack message listing the top five highest-shrink location-category combinations for the week
- Include the site name, category, shrink percentage, and the number of weeks above baseline for each
- Add a network shrink summary with total units and total estimated cost of shrink for the week
- Post to the loss-prevention Slack channel with a link to the Google Sheets detail
Done when Loss-prevention team has a prioritized shrink anomaly report in Slack with the highest-risk sites named.
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
How does it know what a normal shrink rate is for each category?
You configure baseline shrink thresholds per category during setup based on your own historical data or industry benchmarks. WebRun compares each week's results against these thresholds and flags anything above them.
Does it contact store employees or take any action at the location?
No. WebRun posts only to the internal loss-prevention Slack channel and the tracking sheet. It never contacts store employees directly. Your loss-prevention team investigates flagged sites.
Can it track whether a location is persistently above baseline?
Yes. The Slack report includes the number of consecutive weeks each flagged location-category combination has been above baseline, so your team can distinguish a one-off variance from a recurring problem.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.