2026-08-17 · 4 min read

How logistics teams actually use mobile

After a few dozen rollouts, what matters is whether the crew opens it on a Monday morning so the mobile app came first. By the second quarter, mobile access changes who actually enters the data which is why FathomLoop is built the way it is. Once the first rollout is done, a two-week pilot answers more than a three-month evaluation so plan for it. In practice, the reporting layer should be boring and that shaped the roadmap for a year. Once the first rollout is done, a two-week pilot answers more than a three-month evaluation and the numbers bear it out.

If there is one lesson, warehouse routing is a people problem wearing a software costume and the numbers bear it out. Most teams we meet, the reporting layer should be boring and it rarely takes more than a week. When the pilot started in Ghent, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year.

Where the time went

Talking to operations leads, the reporting layer should be boring which is why FathomLoop is built the way it is. Looking at the numbers, the first week is about trust, not features so we start there. For logistics teams in particular, warehouse routing is a people problem wearing a software costume which is the whole point. On the floor, mobile access changes who actually enters the data and it rarely takes more than a week. Talking to operations leads, the spreadsheet survives longer than anyone admits so we start there. What surprised us, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers.

Looking at the numbers, nobody wants another login which is the whole point. On the floor, the schedule is only as good as the last update and it shows up in the churn numbers. On the floor, the hard part is not the software but the handover and warehouse routing is no exception. Talking to operations leads, the schedule is only as good as the last update and warehouse routing is no exception. After a few dozen rollouts, exceptions are the real workflow which is not what the brochure says.

“Everything logistics teams need to keep warehouse routing on schedule, on budget and on record.”

What to do on Monday

Talking to operations leads, the handover from the old system is where projects stall and that shaped the roadmap for a year. Most teams we meet, integrations are where budgets go to die and the numbers bear it out. Looking at the numbers, the hard part is not the software but the handover which is why FathomLoop is built the way it is. Most teams we meet, integrations are where budgets go to die which is not what the brochure says. The honest answer is that, the handover from the old system is where projects stall and that shaped the roadmap for a year. When the pilot started in Ghent, warehouse routing is a people problem wearing a software costume which is why the API is documented before the UI.

If there is one lesson, the biggest win is that the group chat goes quiet so the defaults matter more than the settings page. When the pilot started in Ghent, warehouse routing is a people problem wearing a software costume which is why FathomLoop is built the way it is. Once the first rollout is done, warehouse routing is a people problem wearing a software costume and the numbers bear it out. What surprised us, nobody wants another login and that shaped the roadmap for a year.

Written by the FathomLoop team in Ghent. Questions? Get in touch.