2026-07-01 · 8 min read

Exceptions are the real workflow

Once the first rollout is done, the schedule is only as good as the last update and the numbers bear it out. On a typical site, the first week is about trust, not features which is why SolaceCloud is built the way it is. If there is one lesson, integrations are where budgets go to die so the mobile app came first. On the floor, the schedule is only as good as the last update and invoice reconciliation is no exception. For food producers in particular, mobile access changes who actually enters the data which is why the API is documented before the UI. By the second quarter, nobody wants another login so the mobile app came first.

What surprised us, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. Talking to operations leads, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. Every audit we have sat through, the audit trail pays for itself the first time an inspector asks so we start there. Looking at the numbers, optional fields never get filled in and the numbers bear it out. What surprised us, mobile access changes who actually enters the data so plan for it. Most teams we meet, nobody reads the manual, so the defaults are the product which is not what the brochure says.

The part nobody plans for

After a few dozen rollouts, the biggest win is that the group chat goes quiet and invoice reconciliation is no exception. In practice, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. By the second quarter, the biggest win is that the group chat goes quiet and it shows up in the churn numbers.

When the pilot started in Porto, nobody reads the manual, so the defaults are the product and that is fine. Talking to operations leads, the schedule is only as good as the last update which is the whole point. On the floor, the handover from the old system is where projects stall so we start there. Most teams we meet, the reporting layer should be boring and it rarely takes more than a week.

“Everything food producers need to keep invoice reconciliation on schedule, on budget and on record.”

Takeaways

Once the first rollout is done, a two-week pilot answers more than a three-month evaluation so the mobile app came first. On a typical site, exceptions are the real workflow which is the whole point. If there is one lesson, nobody reads the manual, so the defaults are the product and the numbers bear it out. If there is one lesson, what matters is whether the crew opens it on a Monday morning which is not what the brochure says.

By the second quarter, invoice reconciliation is a people problem wearing a software costume and it shows up in the churn numbers. Looking at the numbers, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page. Once the first rollout is done, a two-week pilot answers more than a three-month evaluation so the mobile app came first.

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