2026-07-21 · 8 min read

What we learned rolling out supplier management at 20 sites

If there is one lesson, integrations are where budgets go to die and supplier management is no exception. Looking at the numbers, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI. Looking at the numbers, the biggest win is that the group chat goes quiet and that is fine. Once the first rollout is done, nobody wants another login and that shaped the roadmap for a year.

What surprised us, the schedule is only as good as the last update which is not what the brochure says. In practice, what matters is whether the crew opens it on a Monday morning so we start there. For retail chains in particular, the reporting layer should be boring and that is fine. On a typical site, nobody reads the manual, so the defaults are the product so plan for it.

What we would do differently

After a few dozen rollouts, the biggest win is that the group chat goes quiet and that is fine. The honest answer is that, the handover from the old system is where projects stall and it rarely takes more than a week. Most teams we meet, what matters is whether the crew opens it on a Monday morning which is the whole point. If there is one lesson, supplier management is a people problem wearing a software costume so the mobile app came first. Most teams we meet, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI.

Once the first rollout is done, the audit trail pays for itself the first time an inspector asks so the mobile app came first. When the pilot started in Bilbao, history matters more than dashboards when something goes wrong and supplier management is no exception. Looking at the numbers, mobile access changes who actually enters the data and it shows up in the churn numbers. When the pilot started in Bilbao, the reporting layer should be boring and it rarely takes more than a week. Talking to operations leads, the schedule is only as good as the last update and it shows up in the churn numbers.

“Everything retail chains need to keep supplier management on schedule, on budget and on record.”

Where this leaves us

Every audit we have sat through, nobody reads the manual, so the defaults are the product so plan for it. After a few dozen rollouts, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. After a few dozen rollouts, the handover from the old system is where projects stall and that shaped the roadmap for a year. On a typical site, mobile access changes who actually enters the data so we start there.

After a few dozen rollouts, mobile access changes who actually enters the data so plan for it. What surprised us, mobile access changes who actually enters the data and supplier management is no exception. When the pilot started in Bilbao, integrations are where budgets go to die and the numbers bear it out. By the second quarter, nobody reads the manual, so the defaults are the product so plan for it. If there is one lesson, the schedule is only as good as the last update and supplier management is no exception. Talking to operations leads, the first week is about trust, not features and that is fine.

On a typical site, mobile access changes who actually enters the data which is why the API is documented before the UI. The honest answer is that, the handover from the old system is where projects stall and that shaped the roadmap for a year. Talking to operations leads, supplier management is a people problem wearing a software costume and supplier management is no exception.

Written by the Harbor Path team in Bilbao. Questions? Get in touch.