The standard case is the easy part
Every demo shows the normal case. The work sits in the exception — and in logistics the exception is everyday business.
RPA has been overtaken
And that is good news. What used to need its own template per sender is now read by a model without one — the boundary moves from “structured” to “readable”.
RPA was the answer to a missing interface. Starting with it today means building maintenance burden for a solved problem.
The real jump: every sender format used to need its own template. Today an order email is read without anyone knowing its format. That moves the boundary from “structured” to “readable”.
What RPA was
A script operating screens, click by click. For years the only route into systems without an interface.
Why it tips
It breaks at the next field change, silently. And it can only do what someone specified step by step.
Still holds
Legacy system, no interface, replacement in sight, process unchanged. A bridge does not have to be beautiful.
No longer holds
Anything requiring understanding. That was never RPA’s strength.
Never was right
Operating the screen although an interface exists.
A customer sends an order by email — sometimes a table, sometimes three lines of prose.
Worked example: the order email with no fixed structure
Sometimes a table, sometimes running text, sometimes “same as last week”. The case shows why “eighty per cent recognised” and “eighty per cent done” are two different statements.
Three outputs
Confident → automatic. Uncertain → draft, a human confirms. Unclear → exception queue with the original text.
Where the benefit sits
Not in the saved minute. An order in the system at 10:01 p.m. can be dispatched next morning — the gain is in the night.
“80 per cent automated” is not a success report until it says who handles the other 20.
A customer credit note arrives. The AI reads it and matches the line items.
And why projects still fail
Almost never on the idea, almost never on the technology. The most expensive mistake is rarely the wrong tool but the wrong moment — and that is decided before anything is bought.
Whoever does not decide the order gets it handed to them by whoever asks loudest.
Master data: outdated contacts and companies under three spellings make any automation useless. What works is not the one-off clean-up but the check inside the process.
The sequence
The most expensive mistake is rarely the wrong tool but the wrong moment: a dispatch system before the data clean-up, a portal before the process behind it.
The undescribed process
What is one process in the demo is three variants in operations, handled three ways. The machine implements one of them.
A dispatch system is introduced. The selection was careful.
Where the best solution sits today
What is named is the pattern, not the vendor — a product name ages, an idea does not.
The exception as its own product
Its own queue, its own metric, a name beside it. Only then is it visible whether automation works or merely moves the pile.
Interface before rebuild
Before anything operates a screen: is there an interface, and why are we not using it? The question predates AI and is not answered by it.
Straight-through rate as the measure
Not the number of automated steps but the share that passes without human touch. Everything else can be talked up.