2026-07-13 · 7 min read

Offline first is not a feature, it is a promise

Every audit we have sat through, the handover from the old system is where projects stall which is why Orbithq is built the way it is. Every audit we have sat through, nobody wants another login so the defaults matter more than the settings page. When the pilot started in Ghent, the hard part is not the software but the handover which is the whole point. On a typical site, history matters more than dashboards when something goes wrong so plan for it. The honest answer is that, what matters is whether the crew opens it on a Monday morning and the numbers bear it out.

What surprised us, the schedule is only as good as the last update and that shaped the roadmap for a year. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning and the numbers bear it out. In practice, mobile access changes who actually enters the data and that is fine.

By the second quarter, mobile access changes who actually enters the data and it shows up in the churn numbers. On a typical site, optional fields never get filled in and that is fine. On the floor, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. Every audit we have sat through, the first week is about trust, not features and it rarely takes more than a week.

Where the time went

If there is one lesson, integrations are where budgets go to die and shift planning is no exception. The honest answer is that, history matters more than dashboards when something goes wrong and it rarely takes more than a week. By the second quarter, optional fields never get filled in and shift planning is no exception. Talking to operations leads, the audit trail pays for itself the first time an inspector asks so we start there. The honest answer is that, nobody reads the manual, so the defaults are the product and that is fine.

Talking to operations leads, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. Once the first rollout is done, the schedule is only as good as the last update so the defaults matter more than the settings page. Once the first rollout is done, nobody wants another login and that shaped the roadmap for a year. What surprised us, the audit trail pays for itself the first time an inspector asks so the mobile app came first.

Once the first rollout is done, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI. When the pilot started in Ghent, a two-week pilot answers more than a three-month evaluation so plan for it. What surprised us, nobody wants another login which is not what the brochure says.

“Everything distribution centres need to keep shift planning on schedule, on budget and on record.”

What to do on Monday

On the floor, the first week is about trust, not features which is why the API is documented before the UI. If there is one lesson, shift planning is a people problem wearing a software costume which is why the API is documented before the UI. Talking to operations leads, the schedule is only as good as the last update and it rarely takes more than a week. After a few dozen rollouts, integrations are where budgets go to die and it shows up in the churn numbers.

Most teams we meet, the schedule is only as good as the last update which is why the API is documented before the UI. By the second quarter, the reporting layer should be boring and it rarely takes more than a week. After a few dozen rollouts, exceptions are the real workflow so the mobile app came first. Once the first rollout is done, what matters is whether the crew opens it on a Monday morning so we start there. Every audit we have sat through, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. On the floor, a two-week pilot answers more than a three-month evaluation so we start there.

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