Two systems that never agreed, agreeing every night.

Orders from the shop into the warehouse, deliveries back into the shop, the invoice out when the goods leave, and the automations somebody built in Make or n8n three years ago, watched and taken over one at a time. It moves data between systems. It never ships a thing without a plan you approved.

SCYTIAN · OPERATIONS · A NORMAL WEDNESDAY{{ clock }}

Scytian · Operations09:50

Order 51 882 wants 40 pcs of item K-220. The warehouse shows 12. Ship 12 now and the rest next week, or hold the whole order?

Split itHold

TODAY, FOR YOU

1question · one tap

0differences between systems

38 orders through · 3.9 h of a dispatcher’s day

every step writes what it did · nothing ships outside the plan{{ foot }}

WHAT IT TAKES OVER

Five hand-offs between systems that used to be a person.

What each one takes a person today, and what is left of it afterwards. The last one is not a job you do; it is the one you inherited.

THE JOBTODAY, BY HANDWITH OPERATIONS

each is a process of its own, with a plan your operations lead approvesnot on the list? if it repeats and has a digital shape, it fits

WHAT REACHES YOU

Two things a week. Both about an order that would have gone wrong.

203 orders went shop → warehouse → invoice last week without anyone copying a number. You heard about one that asked for more than was in stock, and about a Make scenario that quietly stopped on Saturday night and would have been noticed on Tuesday. The second one is why this desk exists.

A question waits. Splitting a delivery, or holding it, is the dispatcher’s call, not the agent’s.

A report does not. The systems already agree, the scenario was already restarted.

17:00

Friday

Operations{{ m.day }}

Split itHold

WHAT IT NEVER DOES

Moves data. Never moves goods on its own.

It never ships outside the plan

An order in stock, paid, to a known address goes through. Anything else, such as short stock, a new address or a first-time customer over a limit, stops and asks. The limits are yours and written down.

It never overwrites a stock count

When the shop and the warehouse disagree, it does not pick a winner. It shows both numbers, when each was last touched, and waits for a person to say which is true.

It never touches an old automation undocumented

A Make or n8n flow is first watched and documented as it really runs. Only then is it taken over, one at a time, with the old one kept until the new one has run clean for a month.

WHAT IT COST, WHAT IT SAVED

One desk. One month. To the cent.

Every run is written down with its cost and the time a dispatcher would have needed, plus the Make credits you no longer buy. Including the one job on this desk that is not worth it yet, and what would fix it.

These are our own books first. That is where the numbers come from.

SCYTIAN · OPERATIONS · JANUARYdispatcher’s rate · 20 €/h

SAVED131 h= 2 620 € + 340 € Make

COST94.10 €2 306 runs · 22 chats

NET2 866 €+9 % on December

Supplier order confirmations by e-mail cost more than they save. Every supplier writes them differently, so the agent reads each one at 0.42 € a minute. Two suppliers sending a CSV would flip the sign. Either way, you saw it here first.

Name the two systems that never agree.

Your Operations agent arrives set up for it, by the next working day, including the automations nobody remembers building.

Get your agent