CRM vs TMS for Freight Forwarders: What Belongs Where

A TMS runs the shipment. A CRM runs the sale. Almost every forwarder owns a competent TMS and improvises the second half in an inbox, which is why the same firm can tell you exactly what it shipped last month and not what it quoted.

The test that settles any argument

For any piece of information, ask: does this exist before there is a shipment, or only after? Everything that exists before the booking belongs on the commercial side. Everything that only exists once cargo is moving belongs in operations.

An enquiry exists before. A house bill does not. A customer's decision timeline exists before. A container number does not.

The split, record by record

Commercial side

• Enquiries and quote requests, whatever channel they arrived on
• Quotes sent, their validity date and their current status
• Follow-up history and who owns it
• Customer and prospect relationships, including the people who never became customers
• Agent and partner relationships, agreements and reciprocity
• Marketing, campaigns and everything that generates an enquiry in the first place

Operations side

• Bookings and confirmed shipments
• Rate contracts and carrier tariffs
• Documents, customs filings, compliance records
• Milestones, tracking and exceptions
• Shipment costing and customer invoicing

The two records that cause every dispute

The rate. A rate lives in the TMS. What you quoted lives on the commercial side. These look like the same thing and are not: the rate is a cost structure, the quote is a commercial position with an expiry date and a customer attached. Duplicating rate tables into a CRM is how integration projects die.

The customer. Both systems need one. The honest answer is that operations owns the billing entity and the commercial side owns the relationship, and the two should be linked by a shared reference rather than kept identical by hand.

What happens when the split is wrong

Push sales into the TMS and you get a contact list attached to shipments. It will show you every customer who has already bought and nothing about the ones who asked and left.

Push operations into a CRM and you get an eighteen month configuration project, a half built TMS and a team that goes back to the old system within a quarter. The category question itself is covered in what a freight forwarding CRM is and is not.

How they should connect

Thinly. A quote that is won creates a booking reference. A booking that completes updates the commercial record so the next conversation starts from what actually happened. That is enough. Every additional field you synchronise is a field that will disagree with itself eventually.

For how this looks in practice, see the features page, and for the operations side of the same question, RYNR vs Magaya.

Frequently asked questions

Does my TMS already include a CRM?

Many do include a module with that name. In most cases it is a contact directory linked to shipment history rather than a system for managing open quotes and follow-up. Check whether it can tell you what you quoted and never heard back on.

Can one system do both?

In theory. In practice the platforms that try tend to be strong at one half and thin at the other, and you discover which half after you have migrated.

Where should agent relationships live?

On the commercial side. An agent relationship exists long before and long after any individual shipment.

How much integration do I actually need?

Less than most projects assume. A shared reference on won business covers the majority of the value.

To see the split applied to your own setup, book a demo.