}

Warehouse automation for mid-sized logistics does not mean a new WMS. It means automating three handovers.

By
Bodo Buschick
14/9/26
•
4 min
Warehouse automation for mid-sized logistics does not mean a new WMS. It means automating three handovers.

Warehouse automation for a mid-sized logistics company does not mean a new WMS. That is the position of this piece. I have held it since the third quote for an SAP Extended Warehouse Management landed on the desk of a warehouse manager with a team of 30. Twelve to eighteen months, six-figure budget. Before that, a requirements analysis, and the analysis says the IT landscape needs rebuilding. The project gets postponed. The pick lists keep getting printed.

Why everyone thinks of the WMS

The picture of the warehouse is the picture of the system. If you have errors in the warehouse, you look for the cause in the WMS, and the vendors help you look. Add to that a consulting model that needs a large project to pay for itself.

Daily life looks different. Bitkom surveyed 1,103 companies with 20 or more employees in 2024. 38 percent handle about half of their office processes on paper. 30 percent still use fax regularly. In the warehouse, the paper collects at the handovers. The driver reports at the gate. The order arrives as a PDF. The pick list goes into the hall as a printout. No WMS change touches that, because the handover happens before or after the system.

The three handovers where the manual work sits

In recent months we automated three of these handovers at three companies without swapping a system. I call them handover 1 to 3, because they have the same names in almost every warehouse.

Handover 1: the arrival at the yard

A forwarder with its own transshipment yard. Between six and eight in the morning, 15 to 20 vehicles arrive almost at once. Every driver reported by phone. Dispatch could not keep up. Trucks stood at the dock whose arrival nobody had entered yet.

The service reads the telematics and draws a geofence of 500 meters around the yard. If a vehicle enters and stays longer than 90 seconds, it counts as arrived. (Without the 90 seconds, every truck driving past counts.) The service assigns the arrival to the tour. Then it notifies dispatch and dock.

The trap was the assignment. Telematics knows vehicles, not orders. A table vehicle to tour, maintained by the dispatcher in two minutes each morning, solved it. The second trap: the interface occasionally returned an empty answer instead of an error. The service read that as "no vehicle here". Since then an empty answer counts as a fault and raises an alarm. Build time: two weeks, no new license.

Handover 2: the order into the system

A wholesaler, 50 orders a day as PDF, eight formats, three and a half hours of retyping. Today a service reads the mailbox and recognizes the format by sender. It checks every line against the article master and creates the order in the warehouse system. Unclear cases go to a review list with PDF and proposal side by side. After three months: under an hour a day, error rate below one percent. The full story is in the order capture case study.

The lesson for the warehouse: the check against the master is the real value, not the text recognition. A wrong article number that was recognized cleanly is still a wrong article number.

Handover 3: the plan into the TMS

A forwarder kept its dispatch plan as an Excel file in SharePoint. The TMS needed the same data anyway, so it was retyped, with duplicate entries as a result. Today an import reads the file after every change, matches it against the orders in the TMS and books only what is new or changed. One source, two systems, zero duplicates.

Technically it is the most boring of the three services, and that is exactly why it ran after a week. Excel stays the dispatcher's tool. The TMS stays the system of record. The import is the bridge, and it writes a protocol of which line it booked when.

What the three have in common

  • No system was replaced. Telematics, warehouse system and TMS stayed as they were.
  • Each service has a threshold above which a human decides. Dwell time at the yard, review list for orders, change matching for the plan.
  • Each service writes a protocol per run, and the alarm hangs on the result, not on the run. A service that runs and books nothing is an outage.
  • Build time two to four weeks, no new licenses. The most expensive item was the time the customer needed to arrange access.

Where the WMS project is still right

There are cases. Several sites with chaotic storage, batch tracking and inventory rules: whoever runs that needs a system for it. An Excel import is no replacement for location management. Our three companies had 20 to 60 vehicles and one or two warehouses. Whether the rule holds above that, I cannot say from our own data.

The point stands: even with a new WMS, drivers arrive at the gate, orders arrive as PDF and plans come from Excel. The three handovers sit in front. Whoever automates them first has an easier WMS project later, because the data arrives clean.

Which of the three handovers costs your warehouse the most minutes a day? Name the one. I will show you, on our example, the protocol of the service that takes it over. Ask for a process check: 30 minutes, no sales pitch.