Fretum Freight TMS
A Transportation Management System for Fretum Freight — dispatch routing, load tracking, driver management, and automated logistics, consolidated onto a centralized cloud architecture.
The Problem
Fretum Freight ran their logistics on fragmented, manual workflows — dispatch, load tracking, and driver coordination scattered across disconnected tools and inboxes. Loads were hard to follow end-to-end, driver status lived in someone's head, and nothing scaled when shipment volume grew.
They needed a single, centralized system that handled the full lifecycle of a freight operation in one place.
Architecture
A centralized TMS on GCP. A Next.js + TypeScript frontend talks to a Node.js backend; dispatch routing, load tracking, and driver management all share one data model so every role sees the same source of truth.
Approach
- Built a comprehensive TMS covering the freight lifecycle end-to-end — dispatch routing, load tracking, driver management, and automated logistics operations in a single application.
- Transitioned operations off fragmented tools onto a centralized cloud architecture, so dispatchers, drivers, and operators all work from one shared source of truth.
- Implemented the platform with Next.js and TypeScript on the frontend, a Node.js backend, and Tailwind CSS for the UI — deployed on GCP for a managed, scalable hosting surface.
- Automated logistics operations that were previously manual, reducing hand-offs and the errors that come with them.
Outcomes
Fretum Freight moved from scattered, manual workflows to a single production TMS running on GCP. Dispatch routing, load tracking, and driver management now live in one place, with automated operations handling the repetitive work — a centralized cloud architecture that scales with shipment volume instead of breaking under it.