Routes instead of manual assembly
Requests become trips with time windows and capacity in mind. When a stop is added, the visit order recalculates — dispatchers do not draw routes in Excel.
TMS Development — Transport Management Systems
Dispatchers see requests, the trip on a map, and arrival forecasts in one screen. The TMS recalculates routes when stops change, prices trips by tariff rules, and keeps trip documents — without driver calls or spreadsheet reconciliations.
What changes in the dispatch desk after a TMS goes live
Trip status and ETA on the map
The vehicle on the map, events like loading and en route, arrival forecast. Plan deviations show up before the client call.
Trip cost by rules
Tariff, zone, and actual mileage produce a sum with a breakdown. In SWAPPZ the price updated when the route changed — disputes closed with numbers in the system.
One panel instead of chats
Request, vehicle, driver, and trip files share one ID. Managers do not hunt waybills in email by order number.
TMS modules for freight trips
Screens and integrations are chosen for the trip type: city distribution, long-haul, or mixed. Below are the blocks that most often cover dispatch and freight accounting.
Planning and routing
The system proposes stop order; the dispatcher approves a version. Time windows and payload limits are checked before departure.
Request queue and assignment
Inbound requests are ranked by SLA and priority. Vehicle and driver are assigned by rules, not by messenger agreements.
Tracking and trip events
GPS and telematics write coordinates and statuses into the trip card. Events are not duplicated when a webhook is delivered twice.
Rate and surcharge calculation
Mileage, idle time, returns, and surcharges roll into a total. Accounting sees the formula, not a handshake total.
Trip documents
Waybills, acts, and attachments live on the trip. The documents ready status moves with the freight stage.
Trip and cost reports
Mileage, delays, plan deviations, and fuel — sliced by period. Leadership sees which route or client eats margin.
Cases: routes, trips, and freight cost
WAPP projects where the core contour is dispatch and freight movement — not warehouse or passenger transport.
DevelopmentDesign
Optimised bike, scooter and bicycle rentals in the UAE and reduced theft
SWAPPZ case: Fleet Management System for UAE rental operations with end-to-end fleet visibility.
Want to see more?
View all projectsConnecting TMS to ERP, telematics, and maps
A trip in TMS lives on events from accounting and from the vehicle. WAPP defines exchange contracts before screen design — so status and amount stay aligned across systems.
Telematics
Coordinates, speed, and sensors land in the trip card. Dispatchers see real movement, not the last driver call.
Maps and geodata
Geocoding, distance matrices, and route building via API. ETA recalculates when stop order changes.
ERP and accounting
Orders and counterparties come from your accounting system; shipment facts and invoices go back over API. Fields are agreed once to avoid double entry.
Shipper portals
Statuses and documents are shared with partners via API or EDI. Clients see the trip stage without calling the desk.
Custom TMS development
Start with the trip map: which statuses, tariffs, and roles dispatchers, logistics, and accounting need. Then — prototypes of key screens and a pilot on one corridor.
Trip and tariff map
Lock transport types, statuses, zones, and pricing rules. Note where a mobile driver contour is required.
Dispatcher screens
Assemble request → trip → map → documents. Logistics walks the scenarios before server logic is built.
Integrations on a test set
Connect ERP, telematics, and maps on a limited vehicle group. Reconcile events and amounts per trip.
Phased launch
Roll out roles in sequence and tune reports. Tariffs and rules improve without stopping live trips.
TMS and rollout questions
Price depends on depth: dispatch desk and map only, tariff calculation, driver mobile app, ERP exchange. On a call WAPP maps trips and integrations and quotes by stage.
In SWAPPZ the routing and pricing MVP shipped in three months from discovery to release — long-haul contours are estimated after the external systems list.
WMS runs the warehouse: bins, picking, shipping from the shelf. TMS runs the trip after shipment: route, vehicle, ETA, freight documents.
The link is the order and the shipped event. If order IDs differ across systems, dispatchers reconcile tables again.
Yes. Accounting sends orders; telematics sends coordinates and events. WAPP designs APIs and webhooks with idempotency so a duplicate event does not create a second trip.
Maps are connected for routing and ETA — the set is locked in the specification before UI.
A pilot on one branch or corridor is usually shorter than a full mobile + reporting contour. Timelines follow the process map.
Design accounts for request peaks: event queues and degradation so a surge does not stop the dispatch desk.
Yes, if the model has long-haul legs, loading and unloading points, and per-kilometre or per-segment tariffs. Trip and tariff models follow your transport type — city, long-haul, or mixed.
SWAPPZ covers short trips and last mile: map, statuses, and real-time pricing.
Common start: requests, map, statuses. Then tariffs, documents, ERP exchange. WAPP locks shared order IDs and events so a new module does not break live trips.
Related contours are on the WAPP logistics hub (warehouse layer, fleet).
Contact
A call to map trips and integrations helps size the TMS and a launch plan without extra screens.