FREIGHT COUNTRY

Deorwine built the complete Freight Country platform: a two-sided freight marketplace and full transportation management system covering the entire load lifecycle from creation through carrier assignment, dispatch, real-time tracking, delivery, and financial settlement. The scope included UX/UI product design, a Next.js web frontend, a FastAPI Python backend spanning 115+ API modules and 100+ data entities, a Flutter driver mobile app for iOS and Android, real-time infrastructure, and integrations across payments, mapping, compliance, accounting, and messaging.

A transportation management system is software that plans, executes, and tracks the movement of freight. It typically manages load creation, carrier assignment, dispatch, shipment tracking, documentation, and invoicing. Freight Country goes further than a standard TMS by operating simultaneously as a marketplace where shippers and vetted carriers transact directly, with offer and counter-offer negotiation, embedded payments, and native FMCSA compliance built into the same system.

Freight Country was delivered in structured phases over approximately 14 months: 4 weeks of discovery and architecture, 4 weeks of UX/UI design, 8 months of core platform development, 3 months of mobile app development, and 2 months of integrations and testing. Deorwine continues as an ongoing development partner post-launch. Timelines vary with role complexity, integration count, and whether real-time tracking and embedded payments are in scope.

Freight Country was built by a cross-functional team of eight: one product manager (12 yrs), two frontend engineers on Next.js (4-5 yrs), two backend engineers on FastAPI/Python (4-5 yrs), one Flutter developer (3.5 yrs), one QA engineer (2 yrs), and one DevOps engineer (6 yrs). Every specialist worked under a single product manager accountable to the client, ensuring tight communication and sprint-based delivery.

Freight Country runs on a Next.js and React frontend, a FastAPI Python backend with a layered Router → Service → Repository → ORM structure, PostgreSQL for data, and Flutter for the driver mobile app. Real-time features use Socket.IO and WebSockets. Integrations include Stripe, BondQuest and Cardknox for payments, Google Maps for tracking, FMCSA/USDOT SAFER for compliance, QuickBooks for accounting, Twilio and Brevo for messaging, Firebase for notifications, AWS S3 for storage, and Docker for containerization.

Off-the-shelf TMS tools manage shipments but rarely support carrier marketplace workflows, offer negotiation, real-time public tracking links for end customers, six-role permission models, embedded payments with freight factoring, or native FMCSA compliance. Freight Country evaluated existing platforms and found none could accommodate those requirements together, which is why a custom build made sense for their business model.

Compliance is built into the workflow rather than managed manually. Integrated USDOT/MC lookup and FMCSA SAFER verification confirm carrier legitimacy at the point of onboarding, and Certificate of Insurance tracking ensures cover is current before a carrier can accept loads. Ratings and reviews for both shippers and carriers add a trust layer that improves match quality over time.

Yes. The Freight Country driver app is built in Flutter, giving a single shared codebase across iOS and Android with offline resilience for routes with poor connectivity. Drivers can accept loads, update statuses, capture signatures, upload documents, navigate via integrated maps, and chat with dispatch, with everything syncing back to the web platform once connectivity is restored.