FLOW LGX · PART 12 · SEPTEMBER 2026
By September 2026 every major feature existed. This month was about trust: telling users the moment something changes, recording who changed it, and proving — role by role — that the whole platform works together.
Month by month, how a logistics platform for a Toronto client went from a simple brief to a live, multi-company SaaS product.
Users get live notifications, important actions land in a read-only audit log, and we tested the whole platform by following real work through every role.
Operations people should not refresh a page to learn that a quote arrived or an exception was raised. Flow LGX keeps a live Socket.io connection for each signed-in user. When a notification arrives, the notifications list and the unread count in the top bar update on their own. Users choose which notifications they want in their settings.
In a multi-company platform, “who changed this?” is a question asked weekly. The audit log records actions with their type, the user, the time and the IP address, and can be filtered by action type. Dispatchers and the super admin team can use it to answer questions with facts instead of memory.
Once a job is locked for dispatch, nobody quietly edits its fields any more. Reroutes and other changes to work already in progress are recorded as override or exception events with an admin note, and the audit log page itself is read-only. Logs can be exported to CSV for an auditor or a dispute, and a separate seat log tracks when users are added or removed.
Direct customers can raise support tickets from their own area, with a subject, category, priority and message, so requests reach the right support agent with context instead of arriving as a vague email.
Testing page by page misses the problems that happen between people. We tested by following real work through the platform as each role: a customer posts a request, a carrier quotes, a distributor accepts, staff scan the freight in, a dispatcher handles an exception, and billing closes the job. Every forbidden address was tried as every role, and every main screen was checked at phone, tablet and desktop widths.
Test the journey, not the page. Most bugs in multi-role software live in the hand-off between two people.