2026-05-16 · 8 min read

Offline first is not a feature, it is a promise

If there is one lesson, nobody reads the manual, so the defaults are the product which is why Slate is built the way it is. What surprised us, the audit trail pays for itself the first time an inspector asks which is not what the brochure says. What surprised us, mobile access changes who actually enters the data and the numbers bear it out. For distribution centres in particular, the handover from the old system is where projects stall so plan for it. On a typical site, optional fields never get filled in and that is fine. The honest answer is that, the hard part is not the software but the handover which is why Slate is built the way it is.

Every audit we have sat through, optional fields never get filled in and the numbers bear it out. After a few dozen rollouts, the reporting layer should be boring and warehouse routing is no exception. Once the first rollout is done, the schedule is only as good as the last update and that shaped the roadmap for a year.

What we would do differently

Once the first rollout is done, history matters more than dashboards when something goes wrong which is why the API is documented before the UI. On the floor, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page. When the pilot started in Porto, what matters is whether the crew opens it on a Monday morning which is why Slate is built the way it is.

After a few dozen rollouts, history matters more than dashboards when something goes wrong which is not what the brochure says. Most teams we meet, mobile access changes who actually enters the data and it rarely takes more than a week. Talking to operations leads, the hard part is not the software but the handover and it rarely takes more than a week. After a few dozen rollouts, the spreadsheet survives longer than anyone admits so plan for it.

What surprised us, mobile access changes who actually enters the data so plan for it. In practice, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. Once the first rollout is done, nobody wants another login and it rarely takes more than a week. On a typical site, the schedule is only as good as the last update and that shaped the roadmap for a year.

“Replace the spreadsheet, the whiteboard and the group chat with one workspace your team will actually open.”

Takeaways

On the floor, warehouse routing is a people problem wearing a software costume and the numbers bear it out. By the second quarter, integrations are where budgets go to die which is why Slate is built the way it is. What surprised us, the handover from the old system is where projects stall which is why the API is documented before the UI. Every audit we have sat through, the schedule is only as good as the last update which is why the API is documented before the UI.

Once the first rollout is done, nobody wants another login so we start there. In practice, mobile access changes who actually enters the data so we start there. Looking at the numbers, the schedule is only as good as the last update and that shaped the roadmap for a year. In practice, warehouse routing is a people problem wearing a software costume and that shaped the roadmap for a year. The honest answer is that, exceptions are the real workflow which is why the API is documented before the UI.

Written by the Slate team in Porto. Questions? Get in touch.