Haulpath, freight dispatch and delivery management
An operations system for a freight company: quotes, approvals, a dispatch board with drag-and-drop and a route map, inventory, proof of delivery and a full audit trail.
Overview
Haulpath runs the daily work of a freight and delivery operation. Customers' loads are quoted and, above a set value, approved by someone other than the requester. Approved loads go to a dispatch board where a dispatcher drags a load onto a vehicle, picks a driver and sends it out. A delivery is only closed with proof of delivery.
Around that sit inventory with stock movements, a fleet list, incident reports, notifications, reports with CSV and PDF export, and an audit trail of who did what.
The problem
Dispatch is often run from spreadsheets and chat threads. Loads go out on vehicles that are too small or on stock that is not there, nobody can see what is on the road, and approvals leave no record.
The solution
One system where the rules are enforced on the server: vehicle capacity, stock at the origin warehouse, driver and vehicle state, approval thresholds and segregation of duties. The dispatch board shows waiting loads, vehicles with capacity bars, and a network map with a preview of the route before anything is sent.
Key functionality
Dispatch board: drag a load onto a vehicle, see capacity fill before you drop, confirm driver and route
Network map of southern Ghana with a route preview and estimated vehicle positions (no GPS feed)
Command palette (Ctrl or Cmd + K), keyboard shortcuts and a light and dark theme
Server-side quotes and an approval workflow above a configurable threshold, with segregation of duties
Capacity and stock checks at dispatch; proof of delivery required to close a shipment
Inventory with stock movements, fleet management, incidents and notifications
Live updates through PostgreSQL LISTEN/NOTIFY streamed as server-sent events
Audit trail, CSV export, PDF delivery notes and summaries, file uploads checked for type and size
Five roles (admin, dispatcher, warehouse, approver, driver) enforced on the server
Architecture
A FastAPI service with SQLAlchemy 2 and Alembic migrations on PostgreSQL. Business rules live in a service layer so the interface cannot bypass them. Authentication uses Argon2 password hashes, a short-lived JWT and a rotating HttpOnly refresh cookie, with login rate limiting.
The front end is Vue 3 with Pinia and Vite, with Apache ECharts for the dashboards. The map is drawn in SVG from approximate city coordinates and a small road graph. Vehicle positions are estimated from dispatch time and route length.
Contribution
Designed and built end to end by Burgess Awalayah Glay at BURGTECH Solutions: interface, API, database schema, workflow rules and tests.
