All templates

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.

Runs on WebRun · Strict Lockdown policy
Every few hours during production shifts WebRunorchestrates each step
1 Mar-Kov check formulations for changes
2 Google Sheets log the change details
3 Slack summarize changes for QA
In short

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

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens mar-kov.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Mar-Kov - check formulations for changes
    mar-kov.com
    WebRun in 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.

  3. 2
    Google Sheets - log the change details
    google.com
    WebRun in 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.

  4. 3
    Slack - summarize changes for QA
    slack.com
    WebRun in 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.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
mar-kov.com
ScheduleRuns automatically on this cadence
Every few hours during production shifts
DeliveryHow each run's result reaches you
Change log · Slack
OutputWhat each run produces - A logged row for every formulation field that changed, plus a Slack summary QA can scan in seconds.
Spreadsheet + alert
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

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.