All templates

Automated LithosPOS Stall Transfer Alerts

Every hour during business hours, WebRun opens LithosPOS, compares stock on hand for each species across your locations, flags when one stall is running low while another has spare, logs the suggested transfer to Google Sheets, and posts a Slack alert for a manager to create and approve in LithosPOS.

Runs on WebRun · Strict Lockdown policy
Every hour during business hours WebRunorchestrates each step
1 LithosPOS compare stock across locations
2 Google Sheets log the suggested transfer
3 Slack alert a manager to approve it
In short

How do I know when to transfer seafood stock between stalls?

WebRun compares LithosPOS stock on hand across your locations every hour during business hours, and flags when one stall is running low while another has spare of the same species. It logs the suggested transfer in Google Sheets and posts a Slack alert tagging the manager, so stock moves between stalls before a customer hears no at the counter.

  • Low stock at one stall gets matched to spare at another before a customer is turned away
  • Transfer suggestions use live stock levels checked hourly, not a weekly guess
  • Managers get an actionable Slack alert instead of manually comparing locations

Built for seafood markets · fishmongers · multi location fish stalls · fish market operations managers

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 lithospos.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    LithosPOS - compare stock across locations
    lithospos.com
    WebRun in LithosPOS: compare stock across locations
    WebRun opens LithosPOS to compare stock across locations.
    • Open LithosPOS and pull stock on hand per species at every location
    • Compare each location to its par level
    • Match a location running low to another with spare of the same species

    Done when Every species is checked across all your locations.

  3. 2
    Google Sheets - log the suggested transfer
    google.com
    WebRun in Google Sheets: log the suggested transfer
    WebRun opens Google Sheets to log the suggested transfer.
    • Log the suggested transfer with species, quantity, from location, and to location
    • Keep a running history of suggested and completed transfers
    • Drop any suggestion once the transfer is created in LithosPOS

    Done when Today's suggested transfers are saved in the log.

  4. 3
    Slack - alert a manager to approve it
    slack.com
    WebRun in Slack: alert a manager to approve it
    WebRun opens Slack to alert a manager to approve it.
    • Post the suggested transfer with quantity and both locations
    • Tag the manager responsible for that stall
    • Leave creating and approving the transfer in LithosPOS to a person

    Done when A manager has an actionable transfer suggestion in Slack.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
lithospos.com
ScheduleRuns automatically on this cadence
Every hour during business hours
DeliveryHow each run's result reaches you
Transfer suggestion · Slack
OutputWhat each run produces - A suggested stock transfer between locations, with species, quantity, and both stalls named.
Text
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 create the transfer in LithosPOS automatically?

No. It only suggests a transfer and alerts a manager. Creating and approving the actual transfer in LithosPOS is always a person's call.

How does it decide which stall sends stock?

By comparing live LithosPOS stock on hand to par level at every location, so it only suggests moving stock from a stall with genuine spare.

What if two stalls both need the same species?

It only suggests a transfer when one location has spare above its own par level, so it won't recommend leaving a stall short to fill another.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.