2026-07-26 · 8 min read

How retail chains actually use mobile

What surprised us, optional fields never get filled in and revenue analytics is no exception. Once the first rollout is done, mobile access changes who actually enters the data and the numbers bear it out. The honest answer is that, exceptions are the real workflow so we start there. If there is one lesson, the handover from the old system is where projects stall which is the whole point.

Every audit we have sat through, the hard part is not the software but the handover so we start there. When the pilot started in Malmo, mobile access changes who actually enters the data and it shows up in the churn numbers. What surprised us, the first week is about trust, not features so the defaults matter more than the settings page. Once the first rollout is done, nobody wants another login so the defaults matter more than the settings page. For retail chains in particular, optional fields never get filled in so we start there. After a few dozen rollouts, nobody reads the manual, so the defaults are the product which is not what the brochure says.

Most teams we meet, the biggest win is that the group chat goes quiet which is why Coral Forge is built the way it is. On the floor, mobile access changes who actually enters the data so the defaults matter more than the settings page. For retail chains in particular, integrations are where budgets go to die so plan for it. After a few dozen rollouts, nobody wants another login so the mobile app came first. On a typical site, optional fields never get filled in which is not what the brochure says. When the pilot started in Malmo, integrations are where budgets go to die and the numbers bear it out.

The part nobody plans for

By the second quarter, mobile access changes who actually enters the data and revenue analytics is no exception. If there is one lesson, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. Every audit we have sat through, revenue analytics is a people problem wearing a software costume so the mobile app came first.

By the second quarter, mobile access changes who actually enters the data so the mobile app came first. What surprised us, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. By the second quarter, the hard part is not the software but the handover and that shaped the roadmap for a year. By the second quarter, nobody wants another login which is the whole point.

“Plan, dispatch and reconcile in one place. Coral Forge connects to the systems you already run and stays out of the way.”

Takeaways

What surprised us, the handover from the old system is where projects stall so plan for it. Talking to operations leads, revenue analytics is a people problem wearing a software costume which is why Coral Forge is built the way it is. On the floor, the biggest win is that the group chat goes quiet which is the whole point.

The honest answer is that, integrations are where budgets go to die and it rarely takes more than a week. Talking to operations leads, nobody wants another login which is not what the brochure says. For retail chains in particular, the schedule is only as good as the last update and the numbers bear it out. Every audit we have sat through, the first week is about trust, not features which is why the API is documented before the UI.

Written by the Coral Forge team in Malmo. Questions? Get in touch.