Automated Mar-Kov Batch Formulation Change Logs
Every few hours, WebRun opens Mar-Kov, compares each batch formulation against its last known version, logs any ingredient, quantity, or process change to a Google Sheet with who made it and when, and posts a short change summary to Slack so QA never misses an update.
How do I keep an audit trail of batch formulation changes in Mar-Kov?
WebRun checks Mar-Kov every few hours for changes to any batch formulation, comparing ingredients, quantities, and process steps against the last known version. It logs each change to a Google Sheet with the old value, new value, editor, and timestamp, then posts a Slack summary so QA has a complete, searchable audit trail without checking Mar-Kov by hand.
- Every formulation edit is logged within hours instead of discovered at audit time
- QA gets a Slack summary instead of manually diffing recipes in Mar-Kov
- Allergen-related changes are flagged separately so they get reviewed first
Built for ice cream manufacturers · frozen dessert QA teams · production managers · co-packers
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
mar-kov.comin a real browser with your saved login - no setup, no API keys. -
1
Mar-Kov - check formulations for changes
WebRun opens Mar-Kov to check formulations for changes. - Open Mar-Kov and pull the current version of every active formulation
- Compare each one against the version captured on the last run
- Note the ingredient, quantity, or process step that changed, and who saved the edit
- Flag changes to allergen-related ingredients as high priority
Done when Every formulation has been checked and any changed fields are captured with who made them.
-
2
Google Sheets - log the change details
WebRun opens Google Sheets to log the change details. - Open the Formulation Change Log sheet
- Append one row per changed field with the old value, new value, editor, and timestamp
- Keep high-priority allergen changes at the top of the sheet
Done when The change log sheet has a row for every formulation edit found this run.
-
3
Slack - summarize changes for QA
WebRun opens Slack to summarize changes for QA. - Post a short summary to the QA channel listing how many formulations changed and by whom
- Call out any allergen-related changes separately
- Link to the full Google Sheet log
Done when QA has a Slack summary of today's formulation changes with a link to the full 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 change or approve formulations itself?
No. WebRun only reads formulations in Mar-Kov and records what changed. It never edits a recipe or approves a change. Every update still happens in Mar-Kov by your own team.
How does it handle allergen-related changes?
It flags any change touching an allergen ingredient as high priority in both the sheet and the Slack summary, so QA reviews those first instead of scrolling through routine tweaks.
What if the same formulation changes twice in one day?
Each change gets its own row with its own timestamp, so the log shows the full sequence of edits rather than overwriting the previous entry.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.