FLOW LGX · PART 6 · MARCH 2026
By March 2026 the original single-company platform worked end to end. A job could be created, received into a warehouse, tracked, sent out and closed, with problems recorded along the way. Six months after the brief, the client could use it with real freight.
Month by month, how a logistics platform for a Toronto client went from a simple brief to a live, multi-company SaaS product.
Six months in, the original platform worked end to end: jobs, warehouse receiving and dispatch, stock by shelf, and a clear process for damaged or missing goods.
Warehouse staff got two focused areas: inbound (what is arriving and needs receiving) and outbound (what must leave and when). Both are built around scanning, because typing reference numbers on a warehouse floor is slow and error-prone. Receiving records the quantity and a bin location, so every item can be found on a shelf later.
Inventory views show stock by warehouse and bin, and warehouse pages give admins a list of sites with their details.
In logistics, things go wrong every day: a carton arrives crushed, a pallet is short, a delivery is refused. Before Flow LGX these lived in emails and photos. We made them first-class records with four types — damaged, missing, partial and refused — and three states: open, in review, and resolved.
Exceptions can be raised by warehouse staff on the floor and handled by dispatchers or admins. Because each one is linked to the job, anyone opening the job sees the problem and what was done about it.
Each role’s home page became a real dashboard rather than a welcome message: counts of open jobs, inbound and outbound work for today, open exceptions, and charts built with Recharts. Reports pages give admins and staff the numbers they used to assemble by hand.
At the end of March the single-company platform did what the original brief asked. Watching it work, the client began to see something bigger: other logistics companies had the same problems. That idea became the turning point of the project in April.
Model problems as records with states, not as comments. A problem with a status gets resolved; a problem in an email gets forgotten.