BLOG
Month by month, how a logistics platform for a Toronto client went from a simple brief to a live, multi-company SaaS product.
November 2026 on Flow LGX: the first weeks with real users, the kinds of fixes that only appear in production, and what comes next for the platform.
October 2026 on Flow LGX: production builds, caching rules for fast repeat visits, the public website and mobile app page, final fixes, and handing a live logistics platform to the client.
How Flow LGX gives the platform owner a plain-language health page — performance score, API errors, average and P95 response times, scan problems — plus security alerts on the dashboard.
September 2026 on Flow LGX: real-time notifications over Socket.io, notification settings, an audit log of who did what, a support desk for direct customers, and how we tested nine roles end to end.
How Flow LGX keeps real-time notifications reliable on unstable connections: authenticated Socket.io, automatic reconnection with back-off, and refreshing cached data instead of trusting every message.
August 2026 on Flow LGX: subscription plans with included admin and driver seats, per-seat pricing, job billing invoices with payment timelines and refunds, and card payments through Stripe.
How Flow LGX splits a freight payment into a deposit at booking and a balance charged later — with a payment timeline, clear statuses and a one-click “capture balance” for staff.
July 2026 on Flow LGX: requests for quotes with full freight details, carriers responding with price and timing, quotes that expire on a countdown, and a vendor marketplace with ratings and compliance status.
June 2026 on Flow LGX: a public “Become a carrier” flow, invite links for vendors, compliance documents with expiry, review by the super admin team, and versioned terms for each user type.
May 2026 on Flow LGX: growing from a few roles to nine, giving distributors their own workspace as sub-admins, limited super-admin staff roles, and admin and driver seats.
Six months into Flow LGX the client changed direction to SaaS. How we extended the platform instead of starting again — what we kept, what we wrapped, and the order we changed things in.
April 2026 on Flow LGX: six months in, the client asked to turn a single-company logistics platform into a SaaS product where each company manages itself. What changed, and what we kept.
March 2026 on Flow LGX: the first complete operational loop — jobs, warehouses, inbound and outbound work, barcode scanning, inventory, and an exceptions workflow for damaged or missing freight.
How Flow LGX lets warehouse staff receive freight by scanning a barcode, QR code, SKU or reference — and what happens when the scan matches nothing, or matches the wrong item.
February 2026 on Flow LGX: the full sign-in journey with email codes, how each role’s API module is organised, and the caching rules that keep a busy dashboard fast without stale data.
How Flow LGX keeps the access token in memory instead of localStorage, refreshes it through a secure cookie, and queues requests during a refresh so users are never logged out mid-task.
January 2026 on Flow LGX: organising a React and TypeScript codebase by role and feature, one protected layout for every signed-in user, and role-based routes that keep each user in their own area.
How Flow LGX serves nine different user roles from one React layout and router while making sure nobody can open a page that is not meant for them — including limited super-admin staff.
December 2025 on Flow LGX: a shared component library, data tables, forms with validation, status badges and skeleton loading — and why every page reuses the same twelve pieces.
November 2025 on Flow LGX: receiving the Figma design, listing every screen and state, and turning colours, type and spacing into reusable building blocks before writing pages.
How the Flow LGX project started in October 2025: a simple brief from a Toronto logistics client, the questions we asked, and the job lifecycle we agreed before any screen was drawn.