← All cases 01

Freight Control System

Driver tracking rebuild, waybills in reporting, MTS Coordinator API integration, automated dispatch and route planning.

MTS API AUTOMATION YII
ruskkom.com/ →
Client
Logistics company (freight)
Period
2023–2024
Role
Development, integrations, automation

Driver and shipment tracking lived in scattered spreadsheets, phone calls, and a legacy module. Tracker coordinates and waybill data never formed a single operational picture — dispatchers manually reconciled statuses, duplicated routes, and delivered reports late to management.

At peak load, one broken spreadsheet blocked planning for hours. The client needed an operations system, not another macro-driven file.

We rebuilt the backend on Yii2: a unified shipment model, trip statuses, driver and waybill links. We integrated the MTS Coordinator API for live coordinates, configured scheduled reports, and rule-based trip assignment.

Critical flows were covered with service-level tests. Rollout was phased — integration and reporting first, then assignment automation — so daily operations never stopped.

What changed

−40%
time on manual reporting
1 system
instead of spreadsheets and calls
MTS API
in real time

Phases

  1. Legacy audit and entity map (shipment, trip, waybill, driver).
  2. MTS API integration with exchange logging.
  3. Dispatcher and management reporting.
  4. Auto-assignment rules and client team training.

Stack rationale

Yii2 and MySQL matched the client's existing skills and need for fast iterations. A REST layer remains ready for future mobile scenarios.

Post-launch support is a separate workstream; the system is now the core of daily logistics, not a side report.

Similar challenge?

Tell us about your project — we will propose architecture and timeline.

Discuss project