Automated Mar-Kov Private Label Order Routing
As each new private label order lands in Mar-Kov, WebRun reads its flavor, packaging, and volume specs, matches it to the correct production line or co-packer capable of running it, drafts an order acknowledgment for the customer's contact, and posts the routing decision to Microsoft Teams so ops can schedule it.
How do I route new private label orders to the right production line automatically?
As each new private label order appears in Mar-Kov, WebRun reads its flavor, packaging, and volume specs and matches it to a production line or co-packer set up to run it. It drafts a customer order acknowledgment in Gmail for your team to send, and posts the routing decision to Microsoft Teams so ops can schedule the run without digging through specs by hand.
- Orders get routed to a matching line within hours instead of sitting in an inbox
- Ops sees every routing decision in Teams instead of checking Mar-Kov order by order
- Unmatched orders are flagged for a human instead of silently misrouted
Built for private label ice cream manufacturers · frozen dessert co-packers · production planners · customer service and ops teams
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 - read the order specs
WebRun opens Mar-Kov to read the order specs. - Open Mar-Kov and find any new private label order not yet routed
- Read its flavor, packaging format, volume, and any customer-specific spec
- Match it against which production lines or co-packers are set up to run that spec
- Assign the order to the best-matched line or co-packer
Done when Every new private label order has a matched production line or co-packer assigned.
-
2
Gmail - draft the order acknowledgment
WebRun opens Gmail to draft the order acknowledgment. - Draft an order acknowledgment to the customer's contact confirming the order was received and its expected production window
- Reference the order number and quantity confirmed in Mar-Kov
- Save it as a draft in Gmail. Never send it automatically
Done when A draft acknowledgment exists in Gmail for every newly routed order.
-
3
Microsoft Teams - notify ops of the routing
WebRun opens Microsoft Teams to notify ops of the routing. - Post the routing decision to the ops Teams channel with the order number, customer, and assigned line or co-packer
- Flag any order that couldn't be matched to a line so a planner can route it by hand
- Tag the scheduler responsible for that line
Done when Ops has the routing decision in Teams for every order, with unmatched ones flagged for manual routing.
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 the customer get the acknowledgment without anyone checking it?
No. WebRun only drafts the acknowledgment and saves it in Gmail. Someone on your team reviews the order details and sends it, so nothing reaches the customer unchecked.
What happens if no line or co-packer matches the order's specs?
It leaves the order unrouted and flags it in Microsoft Teams for a planner to assign by hand, rather than guessing at a line that can't actually run the spec.
Does it reserve production capacity on the line itself?
No. It assigns the order to the best-matched line or co-packer in Mar-Kov and alerts your scheduler. Blocking out the actual production slot is still confirmed by your planning team.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.