Flag shrinkage and trim loss before it adds up
Every night, WebRun opens Markt POS, compares received weight against sold weight and logged waste for each cut, values the difference using cost per pound data from QuickBooks, and posts a Telegram alert for any cut running above its normal shrink rate.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I catch shrinkage and trim loss before it adds up?
WebRun flags shrinkage and trim loss the same night it happens. It compares Markt POS received weight against weight sold and waste logged at the block, values the gap using QuickBooks cost per pound data, and posts a Telegram alert for any cut running above its normal shrink rate, so trim loss gets caught before it becomes a monthly surprise.
- Shrink over the normal rate gets flagged the same night, not at month end
- Trim loss is valued in real dollars using actual cost data
- Every case or block's shrink percentage is tracked run over run
Built for butcher shops · meat markets · meat processors · meat department managers
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
marktpos.comin a real browser with your saved login - no setup, no API keys. -
1
Markt POS - compare received and sold weight
WebRun opens Markt POS to compare received and sold weight. - Open Markt POS and pull received weight by cut for the day
- Compare it against weight sold and any waste logged at the block
- Calculate the shrink percentage for each cut
Done when Every cut handled today has a calculated shrink percentage.
-
2
QuickBooks - value the trim loss by cost
- Pull the current cost per pound for each cut from QuickBooks
- Multiply the shrink weight by cost to get a dollar value
- Total the day's shrink value across all cuts
Done when Every cut's shrink weight has a dollar value and the day has a total.
-
3
Telegram - flag cuts over normal shrink
WebRun opens Telegram to flag cuts over normal shrink. - Post any cut running above its normal shrink percentage to the channel
- Include the dollar value and which block or case it came from
- Leave the cause for staff to investigate
Done when Any cut over its normal shrink rate is flagged in Telegram with a dollar value.
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 identify who caused the trim loss?
No. It flags which cut and block ran over its normal shrink rate and its dollar value. Staff investigate the cause from there.
What counts as a normal shrink rate?
It uses the shrink percentage you've set per cut. Give WebRun your own targets and it flags anything above them.
Does this affect inventory counts in Markt POS?
No. It only reads received, sold, and waste weight to calculate shrink. It never edits a count or a record in Markt POS.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.