TMS Modernization
How a 20‑Year‑Old TMS Unified Fuel Management and Dispatch in One Modern Platform
TMSCloud users managed dispatch and fuel in two separate systems, with two logins and fuel costs typed in by hand, on a codebase still running PHP 5.6. We moved the platform to Laravel 10, merged fuel management into the TMS, and connected ELD data so fuel, dispatch, and invoicing finally share one record.
- Faster fuel and invoice management
- 30%
- Customer satisfaction score
- 7.2 → 9.1
- Return on investment
- 6 Months
Client Overview
Client Story
TMSCloud is a California-based transportation management platform with 20 years in trucking software. Carriers, owner-operators, brokers, and dispatching services across the US use it for load dispatch, accounting and invoicing, driver settlements, and fleet management. CTO Daryn Duff leads the product.
Fuel was the part that did not fit. Fuel management ran as a separate system on a different URL, so dispatchers logged in twice and moved between screens to match a load to its fuel cost. Fuel expenses were typed in by hand, which made budgets inaccurate and reports late. Underneath both sat a legacy codebase on PHP 5.6, hard to secure and harder to extend. Prospects wanted one platform for dispatch and fuel, and when TMSCloud could not offer it, some chose a competitor instead.
Background
Project Background
Daryn wanted TMSCloud to offer what its prospects were asking for: one platform for dispatch and fuel, on a codebase that could keep growing. The brief:
- One Platform for Fuel and TMS
- Merge fuel management into the TMS with a single login.
- A Modern, Secure Codebase
- Move from PHP 5.6 to a current Laravel framework.
- Fuel Costs Without Manual Entry
- Track fuel expenses and invoicing as they happen.
- A Modern Interface
- Responsive screens for dispatchers and admins.
We struggled to manage fuel and dispatch separately: logging in twice, reconciling numbers manually, and losing hours weekly. We needed a single system that could do it all.
Discovery
Research & Ideation
Adding fuel features to a PHP 5.6 codebase would have stacked new work on an unsafe base. The order mattered: modernize first, then merge.
Modernize the Foundation First
Move the platform to Laravel 10 so every new feature is built on a secure, maintainable base.
One Login, One Record
Fuel and dispatch data should live in the same platform, so nobody reconciles two systems by hand.
Let the Trucks Supply the Data
ELD integrations can provide driver logs, routes, and fuel use directly, replacing manual fuel entry.
Design
Designing a Unified Fuel and Dispatch Flow
Fuel data now enters once and travels with the load, from the truck to the invoice.
- ELD ProvidersDriver logs, routes, fuel use
- Automated Fuel EntriesNo manual expense typing
- TMS DispatchFuel linked to loads and drivers
- InvoicingFuel costs included automatically
- Dashboards and ReportsFuel and operations in one view
Every step runs inside one Laravel 10 platform with one login, instead of two systems on two URLs.
Challenges
Project Challenges
Two Platforms, Two Logins
Fuel management and the TMS ran on different URLs, slowing users down and inviting errors.
Manual Fuel Expense Entry
Fuel costs were typed in by hand, causing inaccurate budgets and late reports.
A Legacy PHP 5.6 Codebase
The old stack was hard to secure and maintain, and lacked modern authentication and API handling.
Lost Deals to Unified Competitors
Prospects who wanted dispatch and fuel in one platform went elsewhere.
Approach
Our Solutions
We analyzed both systems and rebuilt them as one Laravel platform, solving the technical and the operational problems together.
Fuel Expense Tracking and Invoicing
Fuel entries and expense reports are automated and tied into TMS workflows, so fuel costs follow each load.
Migration to Laravel 10
The PHP 5.6 codebase moved to Laravel 10, with role-based access control, stronger API security, and detailed logging.
Modern, Responsive Interface
Dashboards and route views were redesigned on the Metronic admin theme and work on desktop, tablet, and mobile.
ELD Provider Integrations
Third-party ELD APIs sync driver logs, routes, and fuel consumption into the platform.
Custom Features
Custom Functionalities
The engineering decisions that turned two aging systems into one platform TMSCloud can keep building on.
Single Login, Shared Data
Fuel and dispatch modules share one account system and one database, ending duplicate logins and duplicate records.
Role-Based Access Control
Dispatchers, accountants, and admins see and change only what their role allows.
Hardened API Security and Logging
API access is secured and activity is logged, closing gaps the PHP 5.6 system left open.
ELD Data Sync
Driver logs, routes, and fuel use arrive from ELD providers without anyone retyping them.
Automated Fuel Expense Reports
Fuel costs roll up into reports on their own, so budgets reflect current numbers.
Responsive Route Views
Route and dashboard views adapt to tablets and phones for dispatchers away from a desk.
Support
On Going Support
After the 6-month build, testing, and deployment, iCommuneTech continues to maintain TMSCloud and ship new features.
Ongoing Maintenance
A dedicated team keeps the platform updated and secure on its modern stack.
New Features, Not Workarounds
On Laravel 10, new modules are added directly instead of patched around legacy code.
Trusted With Two Products
Daryn Duff also chose iCommuneTech to build CDLApps, his driver recruiting platform. See that case study.
The new unified TMS + Fuel Management platform completely changed the way we operate. We now track everything in real-time, invoice faster, and provide better service to our clients.
Impact
Project Outcome
- Faster fuel and invoice management
- 30%
- Customer satisfaction score, out of 10
- 7.2 → 9.1
- Lower monthly operating costs
- $500/mo
- To return on investment
- 6 Months
Results reported by TMSCloud.
Before: two separate systems
- Fuel and TMS on different URLs with separate logins
- Fuel expenses typed in by hand
- Legacy PHP 5.6 codebase
- Prospects lost to unified competitors
After: one modern platform
- Fuel and dispatch in one platform with one login
- Fuel data synced from ELD providers
- Laravel 10 with role-based access and API security
- A unified product TMSCloud can sell
TMSCloud now runs dispatch and fuel management in one platform with one login. Fuel and invoice work is 30% faster, and fuel data arrives from ELD providers instead of being typed in.
Customer satisfaction rose from 7.2 to 9.1 out of 10, operating costs fell by $500 a month, and the project returned its investment within 6 months. Most important for growth, TMSCloud can now offer the unified product its prospects were asking for.
How iCommuneTech Works
Understand first. Build exactly what’s needed. Stay for the long run.
We deliver the exact solution to a business problem with the least investment and time, then stay to keep it working.
We understand before we quote
We start by understanding how the work actually gets done, before we propose anything.
The exact solution, not the biggest one
We recommend the smallest solution that fully solves the problem, and use what already works.
A team that stays
Every launch includes a 90-day warranty, then an optional long-term delivery plan with the same team.
Problem Slowing Business Growth? Let’s Find the Exact Fix.
Tell us how the work gets done today. We’ll map it before we propose anything.
Connect on WhatsApp+91 97256 00878
Share your requirementsenquiry@icommunetech.com