How to build a transportation management system: requirements, architecture and cost

transportation management system

A transportation management system (TMS) is software that helps businesses plan, execute, track, and financially manage the movement of freight from origin to destination. A transport management system can support carrier selection, load planning, shipment booking, tracking, exception management, proof of delivery, freight audit, and transportation reporting within one connected workflow.

A TMS normally works alongside ERP, warehouse management, carrier, accounting, and fleet systems rather than replacing all of them.

In practical terms, it helps answer four questions:

  • How should this freight move?

  • Which carrier or vehicle should handle it?

  • Where is the shipment now?

  • Did the final freight charge match what was planned?

This is why TMS software is used by shippers, manufacturers, distributors, third-party logistics providers, freight forwarders, and delivery businesses that need more control over transportation operations.

For a broader industry definition, IBM describes a transportation management system as a logistics tool used to manage inbound and outbound shipping and connect transportation activity with wider supply-chain systems: Transportation Management Systems.

How Does a Transportation Management System Work?

A transportation management system usually follows the shipment from the point transportation demand is created until delivery has been confirmed and the freight invoice has been checked.

A simplified workflow looks like this:

Order → Transportation Planning → Carrier Selection → Booking → Dispatch → Tracking → Delivery → Freight Audit → Reporting

Not every company follows exactly the same sequence.

A manufacturer moving full truckloads between factories has different requirements from an e-commerce company shipping thousands of parcels. A private fleet also operates differently from a shipper buying transportation from external carriers.

The TMS should reflect those differences.


Plan the Shipment and Compare Carriers

The process begins with transportation demand.

That demand may originate from:

  • a sales order;

  • a warehouse release;

  • a purchase order;

  • an e-commerce order;

  • a transfer between facilities;

  • a manually created shipment request.

The TMS gathers the information required to plan the movement.

That can include:

  • origin;

  • destination;

  • delivery date;

  • dimensions;

  • weight;

  • product type;

  • service level;

  • available carriers;

  • contracted freight rates.

The system may then perform transportation planning and load planning.

Suppose a business has four orders travelling from the same warehouse to customers in the same region.

Sending four separate vehicles may be unnecessary.

A TMS may identify that those orders can be combined into fewer planned loads while still meeting delivery commitments.

Carrier selection works in a similar way.

The cheapest rate is not always the correct choice.

Carrier A may charge less but take four days.

Carrier B may cost slightly more but meet a two-day customer commitment.

The TMS can help compare:

Cost + Transit Time + Service Level + Capacity + Carrier Rules

rather than relying on freight cost alone.

Book the Load and Send Dispatch Instructions

Once the transportation plan is accepted, the shipment needs to be executed.

For an external carrier, this may involve:

  • sending a booking or tender;

  • receiving carrier acceptance;

  • confirming pickup;

  • generating shipping documentation;

  • communicating load instructions.

For a private fleet, execution may instead involve:

  • assigning a vehicle;

  • assigning a driver;

  • sequencing stops;

  • sending dispatch instructions.

This is where the transportation plan becomes an operational movement.

A useful TMS should preserve the relationship between:

Order → Shipment → Load → Carrier/Vehicle

because these are not necessarily the same thing.

One customer order can create multiple shipments.

Several shipments can also be consolidated into one load.

Treating all three as interchangeable makes transportation reporting and exception handling unnecessarily difficult.

Track Delivery and Manage Exceptions

Once the load is moving, the focus shifts from planning to execution visibility.

Shipment tracking may receive information from:

  • carrier APIs;

  • EDI messages;

  • driver mobile applications;

  • GPS or telematics platforms;

  • manual updates;

  • warehouse systems.

A tracking screen is useful, but visibility alone is not enough.

The operational value comes from exception management.

Consider a shipment that was expected to reach a distribution centre at 14:00.

At 13:00, the latest tracking event indicates that delivery is unlikely before 17:00.

A useful TMS should help the operations team identify that risk before the customer has to ask where the shipment is.

Depending on the workflow, an exception may trigger:

  • an operations alert;

  • customer notification;

  • rescheduling;

  • carrier follow-up;

  • warehouse coordination.

This moves the TMS from passive tracking toward active transportation management.

Confirm Delivery and Reconcile the Freight Invoice

Transportation does not necessarily end when the vehicle reaches its destination.

The system may still need to capture:

  • delivery status;

  • delivery timestamp;

  • recipient;

  • signature;

  • photograph;

  • damaged or missing goods;

  • delivery notes.

This information forms the electronic proof of delivery.

The proof of delivery can support:

  • customer service;

  • dispute resolution;

  • billing;

  • freight reconciliation.

The finance workflow can then compare:

Booked Rate → Actual Shipment → Carrier Invoice

Suppose the TMS recorded an agreed freight cost of ₹24,000.

The carrier later invoices ₹28,500.

Instead of approving the invoice automatically, the system can identify the difference and help determine whether the additional charge is valid.

This is the basis of freight audit and settlement.


Which Features Belong in a TMS?

There is no universal TMS feature list.

The right functionality depends on whether the business uses external carriers, private vehicles, parcel services, multimodal freight, last-mile delivery, or a combination.

However, most transportation management software can be grouped around three areas:

Plan → Execute → Financially Control

Load Planning, Carrier Selection and Rate Comparison

Transportation planning features may include:

  • order-to-shipment planning;

  • load consolidation;

  • routing;

  • capacity planning;

  • carrier assignment;

  • rate management;

  • service-level comparison;

  • tendering.

These capabilities help operations teams decide how freight should move before money is committed.

For example, a planner may need to compare:

CarrierFreight RateTransit TimeService
Carrier A₹21,0004 daysStandard
Carrier B₹24,0002 daysExpress
Carrier C₹23,0003 daysStandard

The lowest number does not automatically produce the best transportation decision.

The planner has to consider the customer’s delivery requirement.


Shipment Tracking, Alerts and Electronic Proof of Delivery

Execution functionality may include:

  • pickup confirmation;

  • real-time or milestone tracking;

  • ETA updates;

  • exception alerts;

  • driver communication;

  • delivery confirmation;

  • electronic proof of delivery.

A strong tracking workflow should make it easier to answer:

  • Which shipments are late?

  • Which loads have stopped progressing?

  • Which customers need to be informed?

  • Which deliveries are complete?

  • Which records are missing proof of delivery?

This is more useful than showing hundreds of shipment pins on a map without prioritizing operational action.


Freight Audit, Settlement and Reporting

The financial side of freight management can include:

  • planned freight cost;

  • carrier invoice;

  • accessorial charges;

  • invoice matching;

  • dispute handling;

  • approval;

  • payment status;

  • transportation reporting.

Reporting can then measure areas such as:

  • freight spend;

  • cost per shipment;

  • cost by lane;

  • cost by carrier;

  • on-time pickup;

  • on-time delivery;

  • carrier performance;

  • exception frequency.

A TMS becomes more valuable when operational events and financial outcomes can be analysed together.


Who Uses Transportation Management Software?

Transportation management software is useful wherever moving goods creates enough operational complexity to require structured planning, execution, visibility, or freight-cost control.

Shippers and Manufacturers

Manufacturers and shippers may use TMS software to manage:

  • inbound materials;

  • transfers between plants;

  • outbound customer shipments;

  • carrier procurement;

  • routing;

  • freight costs.

For example, a manufacturer may have finished goods ready in three factories and customer orders across several regions.

The TMS helps determine:

  • what needs to ship;

  • when;

  • from where;

  • through which carrier;

  • at what expected cost.


Third-Party Logistics Providers and Freight Forwarders

A 3PL or freight forwarder manages transportation on behalf of customers.

Its TMS may need additional capabilities such as:

  • multiple customer accounts;

  • carrier rate management;

  • customer quoting;

  • shipment booking;

  • documentation;

  • billing;

  • customer tracking portals.

Because a 3PL may coordinate many carriers and customer workflows, integrations and account-level visibility become particularly important.


Private Fleets and Last-Mile Delivery Teams

Companies operating their own vehicles may use transportation software for:

  • dispatch;

  • route planning;

  • driver assignment;

  • vehicle allocation;

  • delivery sequencing;

  • mobile tracking;

  • proof of delivery.

However, a TMS and a fleet management system are not identical.

The TMS primarily manages the movement of freight.

Fleet software primarily manages the vehicles performing that work.

A business running its own fleet may use both.


What Are the Benefits of a Transportation Management System?

The useful benefits of a TMS are operational and measurable.

The objective is not simply to “digitize logistics.”

It is to improve decisions made during transportation.


Compare the Planned Freight Cost With the Invoiced Cost

Without a structured system, the commercial lifecycle of a shipment may be fragmented across:

  • carrier emails;

  • spreadsheets;

  • accounting software;

  • transport documents.

A TMS can connect the original freight decision with the final invoice.

For example:

Booked: ₹32,000
Invoiced: ₹35,500
Difference: ₹3,500

The operations or finance team can investigate the difference instead of approving the charge without context.

The result is better freight-cost visibility rather than simply cheaper transportation.


Identify Late Shipments Before Customers Have to Ask

Transportation problems become more expensive when the customer discovers them first.

A TMS can help monitor shipment milestones and identify:

  • missed pickup;

  • delayed departure;

  • late arrival;

  • route deviation;

  • missing delivery confirmation.

Operations teams can then intervene or communicate proactively.

The goal is not to eliminate every delay.

Transportation involves weather, congestion, capacity constraints, mechanical problems, and other factors outside the software’s control.

The goal is to identify exceptions early enough to respond.


Measure Carrier Performance and On-Time Delivery

Carrier selection improves when decisions are based on actual performance.

A TMS can help compare carriers using measures such as:

  • acceptance rate;

  • on-time pickup;

  • on-time delivery;

  • average transit time;

  • damage or claim frequency;

  • freight cost;

  • exception frequency.

Suppose Carrier A is 5% cheaper but consistently misses the required delivery window.

Without performance data, the business may continue choosing A because the quoted rate looks attractive.

Transportation reporting makes the trade-off visible.


What Is the Difference Between a TMS, WMS, ERP and Fleet Management System?

These systems often exchange information, which is why their responsibilities can be confused.

The simplest distinction is to ask what operational question each system is designed to answer.

SystemQuestion it answersExample in the same shipment
ERPWhat did the customer order, and what must the business fulfil or invoice?Records the sales order and receives the approved freight cost.
WMSWhat is ready to leave the warehouse?Confirms that the cartons have been picked, packed and staged.
TMSHow will the freight move, and was the carrier’s charge correct?Compares rates, books the shipment, tracks delivery and checks the freight invoice.
Fleet management systemWhat is happening with the vehicles used for delivery?Tracks vehicle location, availability and maintenance.


The four systems can participate in the same transaction.

For example:

ERP: customer orders 100 units.

WMS: warehouse picks and stages 100 units.

TMS: books a carrier and manages transportation.

Fleet system: tracks the vehicle if the company uses its own fleet.

After delivery:

TMS: validates transportation cost.

ERP: records the approved financial transaction.

This is why TMS vs WMS is usually the wrong framing.

In a mature logistics environment, the systems should complement one another.


How Does a Cloud TMS Connect to Existing Logistics Software?

A cloud TMS hosts transportation-management functionality in a cloud environment rather than requiring the customer to operate the entire application on local infrastructure.

Cloud deployment does not remove the need for integrations.

The TMS still needs operational information from other systems.


ERP and Warehouse Management Systems

An ERP may send:

  • customer orders;

  • purchase orders;

  • supplier information;

  • billing data.

A WMS may send:

  • inventory availability;

  • pick completion;

  • package information;

  • shipment readiness.

The TMS can return information such as:

  • carrier;

  • shipment number;

  • freight cost;

  • tracking status;

  • delivery confirmation.

A typical workflow might look like:

ERP → WMS → TMS → Carrier

and later:

Carrier → TMS → ERP / WMS / Customer

An important architecture decision is deciding which system owns each record.

For example:

ERP owns the sales order.

WMS owns warehouse execution.

TMS owns the transportation plan.

Clear ownership reduces synchronization conflicts.


Carrier APIs, EDI and Tracking Updates

Carrier connectivity can be implemented in several ways.

Carrier APIs can support:

  • rate requests;

  • booking;

  • labels;

  • shipment creation;

  • tracking.

EDI may be used for structured business documents and transportation messages between organizations.

Other integrations may rely on:

  • webhooks;

  • file exchange;

  • telematics feeds;

  • driver apps.

The integration must also account for failure.

What happens if:

  • the carrier API times out?

  • the booking succeeds but the TMS does not receive the response?

  • the same tracking event arrives twice?

  • shipment status stops updating?

Reliable transportation integration requires:

  • retries;

  • duplicate protection;

  • logging;

  • reconciliation;

  • manual exception handling.

That engineering detail becomes especially important when transportation software is connected to many carriers.


What Do Shipping and Last-Mile Systems Look Like in Practice?

A TMS does not have to look identical across every business.

Two Pavans Group logistics projects show how different transportation problems lead to different software workflows.


Evership: Connecting Shipping and Carrier Workflows

Evership is a shipping and fulfilment automation platform designed for e-commerce businesses.

The platform connects online orders with shipping operations and supports functions such as:

  • order synchronization;

  • comparison of courier rates;

  • shipping labels;

  • delivery management;

  • tracking;

  • fulfilment workflows.

This illustrates the shipping side of transportation software.

The user may not be managing a traditional enterprise TMS, but the workflow still needs to connect orders, carriers, shipping rates, tracking, and fulfilment.

The important lesson is that transportation software should match the operating model.

For an e-commerce shipper, carrier comparison and fulfilment automation may matter more than complex private-fleet functionality.


Molo: Supporting Last-Mile Delivery Operations

Molo addresses a different transportation problem: last-mile parcel delivery.

Its platform includes a mobile application for delivery agents and a web portal for management.

The documented workflow includes:

  • parcel tracking;

  • offline support;

  • route optimization;

  • delivery management;

  • payments;

  • operational reporting.

Offline support is particularly important.

Delivery operations do not stop because a driver moves into an area with poor network coverage.

The mobile application therefore has to continue supporting the workflow and synchronize appropriately when connectivity returns.

For two different parts of this workflow, see Evership’s shipping and fulfilment platform and Molo’s last-mile delivery platform.

These projects should not be treated as identical TMS implementations. They demonstrate different transportation-software patterns: multi-carrier shipping automation and last-mile delivery operations.


How Do You Choose a Transportation Management System?

Start with your freight workflow, not a software feature checklist.

A system with 300 features is not necessarily a better fit than one that handles your 30 important workflows correctly.


Match the Software to Your Freight, Carriers and Delivery Requirements

Document how transportation works today.

Start with:

What is being moved?

Then define:

  • shipment types;

  • transportation modes;

  • origins;

  • destinations;

  • carriers;

  • private fleet involvement;

  • freight volume;

  • delivery commitments;

  • existing systems.

Next identify where the current process breaks.

For example:

  • planners compare rates manually;

  • carrier booking happens through email;

  • customers repeatedly call for shipment status;

  • delivery records arrive late;

  • freight invoices cannot easily be checked against agreed rates.

Those problems should shape the TMS requirements.

If your operation is primarily parcel shipping, you may prioritize:

  • carrier APIs;

  • rate comparison;

  • shipping labels;

  • tracking.

If you operate a private fleet, you may prioritize:

  • dispatch;

  • routes;

  • drivers;

  • delivery sequencing;

  • proof of delivery.

If you manage large freight networks, you may need deeper:

  • load optimization;

  • tendering;

  • freight settlement;

  • carrier performance reporting.


Test One Shipment From Order Intake to Invoice Approval

Product demonstrations often show individual screens.

That is not enough.

Ask the vendor to demonstrate one complete shipment.

For example:

1. Receive an order

2. Build the shipment

3. Compare available carriers

4. Select a carrier

5. Book the load

6. Receive tracking events

7. Handle a delayed shipment

8. Capture proof of delivery

9. Receive the freight invoice

10. Compare the invoice with the planned freight cost

This exposes gaps that feature lists can hide.

A system may have:

  • carrier management;

  • shipment tracking;

  • invoicing;

but still require manual work between those modules.

Testing the complete workflow shows whether the application behaves like one transportation system or several disconnected features.


Decide Whether to Buy, Extend or Build

There are three reasonable approaches.

Buy

Use an existing commercial TMS when your transportation workflows are well supported by available software.

This can reduce:

  • development time;

  • technical ownership;

  • maintenance responsibility.

Extend

An existing platform may solve most requirements but still need:

  • integrations;

  • reporting;

  • workflow extensions;

  • customer portals;

  • mobile applications.

Extending an existing product can be more practical than replacing it.

Build

Custom TMS development becomes more appropriate when transportation processes are sufficiently specialized that packaged software creates significant workarounds.

Examples might include:

  • unusual planning rules;

  • proprietary carrier workflows;

  • complex legacy integrations;

  • differentiated logistics products;

  • specialized mobile workflows.

Custom development creates greater control, but it also creates responsibility for:

  • product ownership;

  • security;

  • maintenance;

  • infrastructure;

  • ongoing enhancement.

If packaged software covers your freight workflow but cannot connect to a critical carrier or warehouse system, identify that gap before committing to a replacement. If the workflow itself requires custom development, use our guide to building a transportation management system to define requirements, integrations and cost drivers.


Frequently Asked Questions

Is a Transport Management System the Same as a Transportation Management System?

Yes. Transport management system and transportation management system are commonly used for the same type of logistics software. TMS is the usual abbreviation. Terminology can vary by country and software provider, but both generally refer to software used to plan, execute, monitor, and optimize freight transportation.

Can a TMS Work With an Existing ERP or WMS?

Yes. TMS software commonly works alongside ERP and warehouse systems rather than replacing them. The ERP may provide order and financial information, the WMS manages warehouse execution, and the TMS manages transportation planning, booking, tracking, delivery, and freight-cost workflows.

Integration may use APIs, EDI, webhooks, files, or other system-specific methods.

What Is the Difference Between Freight Management and Fleet Management?

Freight management focuses on moving goods from origin to destination. It includes planning shipments, selecting carriers, tracking freight, managing delivery, and controlling transportation costs.

Fleet management focuses on vehicles and related assets. It may include vehicle location, maintenance, driver information, utilization, fuel, and availability.

A company using external carriers may need freight-management functionality without operating its own fleet.

A private fleet operator may need both.

What Affects the Cost of Transportation Management Software?

TMS cost depends on the implementation approach and operational complexity.

Important factors include:

  • number of users;

  • shipment volume;

  • transportation modes;

  • carriers;

  • private-fleet requirements;

  • integrations;

  • mobile applications;

  • tracking;

  • route optimization;

  • reporting;

  • security;

  • support.

Commercial TMS products may use subscription or transaction-based pricing.

A custom TMS requires software-design, development, testing, integration, deployment, and ongoing maintenance investment.

The best comparison is therefore not simply:

License price vs development price

but:

Total cost of ownership for the required workflow.


Conclusion: Start With One Complete Freight Workflow

A transportation management system helps businesses plan how freight should move, execute the shipment, monitor delivery, manage exceptions, confirm completion, and control transportation costs.

Its core value is not the number of features it contains.

It is the ability to connect transportation decisions across one complete operational workflow.

A useful starting point is:

Order → Plan → Carrier/Vehicle → Book → Track → Deliver → Audit → Report

Map that workflow first.

Then identify:

  • where manual work occurs;

  • where data is duplicated;

  • where transportation visibility is lost;

  • where freight cost becomes difficult to reconcile.

That gives you a practical basis for deciding whether an existing TMS software product fits, whether your current system should be extended, or whether custom development is justified.

Planning a logistics software project? Share one shipment workflow, the systems involved and the step that causes the most manual work. Discuss your logistics software requirements with Pavans Group.


About the Author

Naresh Chauhan – CEO, Pavans Group

Naresh Chauhan is CEO of Pavans Group, a software and digital product development company based in Vadodara, India. He works with teams building custom software, logistics platforms, web and mobile applications, SaaS products, AI-enabled systems, integrations, and other digital solutions for businesses across different industries.

Get in touch

Talk to our experts and get the right solution for your business.