2026-07-02 · 6 min read

What we learned rolling out warehouse routing at 39 sites

For food producers in particular, mobile access changes who actually enters the data and that shaped the roadmap for a year. Once the first rollout is done, the first week is about trust, not features which is not what the brochure says. Once the first rollout is done, warehouse routing is a people problem wearing a software costume so the defaults matter more than the settings page. The honest answer is that, the audit trail pays for itself the first time an inspector asks which is why KestrelNode is built the way it is. Looking at the numbers, exceptions are the real workflow so plan for it. Looking at the numbers, the audit trail pays for itself the first time an inspector asks which is why KestrelNode is built the way it is.

On a typical site, history matters more than dashboards when something goes wrong and warehouse routing is no exception. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. Most teams we meet, the handover from the old system is where projects stall so plan for it. On the floor, optional fields never get filled in which is the whole point. After a few dozen rollouts, the handover from the old system is where projects stall and that is fine. Most teams we meet, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year.

Every audit we have sat through, nobody wants another login and it shows up in the churn numbers. On a typical site, the first week is about trust, not features and it rarely takes more than a week. In practice, the first week is about trust, not features which is why the API is documented before the UI.

Where the time went

After a few dozen rollouts, the spreadsheet survives longer than anyone admits which is why KestrelNode is built the way it is. By the second quarter, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. The honest answer is that, mobile access changes who actually enters the data and that shaped the roadmap for a year. For food producers in particular, the schedule is only as good as the last update and warehouse routing is no exception.

If there is one lesson, the first week is about trust, not features so plan for it. What surprised us, nobody wants another login so the mobile app came first. Once the first rollout is done, the first week is about trust, not features which is the whole point. If there is one lesson, the spreadsheet survives longer than anyone admits so plan for it.

“Everything food producers need to keep warehouse routing on schedule, on budget and on record.”

What to do on Monday

Looking at the numbers, history matters more than dashboards when something goes wrong which is why KestrelNode is built the way it is. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks so plan for it. For food producers in particular, what matters is whether the crew opens it on a Monday morning and that is fine. After a few dozen rollouts, the reporting layer should be boring so plan for it.

On the floor, the biggest win is that the group chat goes quiet and the numbers bear it out. The honest answer is that, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers. After a few dozen rollouts, exceptions are the real workflow and that shaped the roadmap for a year. If there is one lesson, the reporting layer should be boring which is why KestrelNode is built the way it is.

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