What Is a TMS and Why Carriers and Freight Forwarders Need One
A TMS is a working system in which a carrier or freight forwarder manages a shipment from the request and calculation through delivery, documents, and settlement. It connects the route, rates, currencies, costs, assigned parties, and statuses in one shipment record. A TMS becomes useful when transport data is split across spreadsheets, messages, and accounting, making it hard to see the current stage, margin, or amount payable.
What a TMS does in plain language
Every shipment starts with a request record: the ordering party, cargo, loading and unloading points and time windows, terms, responsible forwarder, carrier, and vehicle. Instead of maintaining separate spreadsheet rows, the team works from one record that shows the current state and the person responsible for the next action.
A shipment calculation example
Suppose the customer rate is agreed in euros while the carrier is paid in another currency. An agency fee or an agreed extra service is recorded as a separate line. The system uses the contractually defined exchange rate for the loading, delivery, invoice, or payment date and stores both the rate and its date. Dispatch and finance can then see how margin was calculated, even if an exchange rate or expense changed after the first approval.
Typical shipment stages
- The request is accepted and the route and terms are recorded.
- Rates are approved and the carrier and vehicle are assigned.
- The vehicle arrives for loading and the cargo is collected.
- The shipment is in transit, with delays or exceptions assigned for action.
- Delivery is confirmed and original documents are pending or received.
- Invoices and payments are reconciled and the shipment is closed.
Documents attached to the shipment
A shipment record may hold the transport order or contract, CMR or domestic consignment note, service acceptance certificate, invoice, and proof of delivery. Each document should have a visible state such as expected, copy received, original received, checked, or returned for correction. A missing acceptance certificate then remains an actionable item instead of disappearing among files, and finance can see whether invoicing or payment may proceed.
Who benefits from a TMS
A TMS is relevant when one shipment contains several currencies, costs, and responsible people, while a route change has to be corrected separately in a spreadsheet, messages, an invoice, and accounting. Another sign is that only one dispatcher knows the actual status, while the financial result requires a manual document reconciliation.
Questions the system should answer in seconds
- What is the margin on a particular shipment, and which income and cost lines produced it?
- Which delivered shipments are still missing the documents required to close them?
- How much is payable to carriers on a selected date, and against which invoices?
- Which vehicles have not arrived for loading, and who is handling the exception?
- Which shipments had a rate, route, or exchange-rate change after approval?
Custom development is worth considering when the standard workflow cannot represent tariff rules, approvals, roles, documents, or exchange with the accounting system. Review several ordinary and problematic shipments first. This shows whether dedicated logic is needed or whether the existing process only needs clearer rules.
How TMS differs from CRM and ERP
CRM systems manage contacts, enquiries, proposals, and the history of commercial agreements. A TMS takes over the operational detail once there is a specific shipment: route, vehicle, stages, costs, documents, and margin.
An ERP system holds financial and management accounting, purchasing, and other resources. The TMS can send approved invoices, service acceptance records, and amounts to it, while receiving reference data, counterparties, or payment states. Before development, decide where each record is created, who may edit it, and which system wins when values conflict.
Typical TMS modules
The core includes a request register, shipment record, income and cost calculation, execution stages, documents, settlements, and shipment reports. Dispatch needs routes, vehicles, contacts, deadlines, and exceptions. Finance needs invoices, currencies, exchange rates, certificates, and payment states. Management needs margin, unclosed shipments, overdue actions, and a change log.
Separate modules and integrations
GPS, a driver account, routing, telematics, and electronic consignment notes are added for specific workflows. A driver account can receive assignments and proof photos, coordinates can confirm arrival, and electronic document exchange can place a signed document in the shipment record. The presence of an integration alone does not make the process useful.
Every exchange needs a trigger event, field list, direction, and response to failure. If the accounting system is temporarily unavailable, for example, an invoice can remain in a visible queue and an authorised person can retry it. This prevents a shipment from appearing closed when its financial data never reached accounting.
How custom TMS development proceeds
Development begins with real shipments, not a list of screens. The team follows a request from receipt to closure and records formulas, approval points, documents, roles, and exceptions. The first stage is limited to a complete workflow, such as creating a request, confirming delivery, and sending an invoice to accounting.
- Review an ordinary shipment, a route change, and a case with missing documents.
- Agree record fields, formulas, currencies, exchange-rate date, stages, and role permissions.
- Design the accounting exchange and retry rules for failed transfers.
- Walk dispatch, forwarding, finance, and management through the prototype using their tasks.
- Build the first workflow and test it on copies of real shipments without unnecessary personal data.
What the commissioning company needs to provide
The development team needs access to a test environment for the existing accounting system and its API documentation, examples of real shipments, document templates, and working reference directories. These directories may include counterparties, vehicles, drivers, cargo types, currencies, cost categories, and statuses. People from dispatch and finance must also be available to explain exceptions and check the result.
Ask a prospective contractor how rate and exchange-rate changes are logged, what happens after an exchange failure, how financial data is restricted by role, and which conditions close a shipment. Specific answers make proposals comparable by operating logic rather than by the number of modules listed.