CRM for customs brokers and freight forwarders
A forwarder's customer relationship is not a deal, it is a lane: the same importer shipping the same goods month after month, judged on the last shipment that went wrong. A sales CRM can log that an importer was won; it cannot see that their last three shipments cleared late, that a quote for a new lane has been sitting unanswered for a week, or that the account's volume has been sliding for a quarter. The operational systems know the shipments; nothing watches the relationship.
Where the generic CRM breaks:
Won once, invisible forever. An importer is won once and then ships for years. The CRM closes the deal and stops looking, so an account quietly shifting volume to a competitor shows nothing until the monthly totals do — months too late to have the conversation.
Quotes are not deals. A forwarding desk issues dozens of quotes a week per account, most against a rate that expires. Modelling each as a pipeline deal buries the desk in stages; not modelling them means nobody knows the win rate per lane or which quotes died on price versus on silence.
The CRM cannot see shipments. The account's health is written in its shipments — volumes, exceptions, holds, late clearances — and all of that lives in the TMS or filing system. A CRM with no shipment feed reduces account management to remembering to call.
Compliance documents on file, nowhere. Powers of attorney, bond details and credit terms have effective dates and expiries, and an expired one stops shipments. Filed as attachments on a contact, nothing warns the desk before the importer finds out at the border.
The data model that actually fits:
Account with shipment feed. The importer as an entity fed by shipment counts and exception rates from the operational system, so a declining or exception-heavy account surfaces on a list instead of in a year-end review.
Quote with expiry. Each quote tracked per lane with its rate validity and outcome, so follow-up happens before expiry and the desk learns which lanes and which accounts it actually wins.
Lane. Origin, destination and mode as a first-class thing the account ships, because forwarding relationships grow lane by lane and nobody can sell the next lane without seeing the current ones.
Compliance document with expiry. Powers of attorney, bonds and credit agreements dated and expiry-tracked per account, flagged well before they stop a shipment.
Issue record. Holds, damage, billing disputes and service failures logged against the account, so the person making the next renewal call knows exactly what the importer remembers.
Our verdict: Keep the TMS and the filing software; entry filing is regulated and those systems are entrenched for good reason. The genuine gap is the commercial layer that reads from them — account health from shipment data, quote tracking with expiries, compliance documents that warn before they lapse. A generic CRM configured hard gets you the quote log; it will never see your shipments. That connection is the build, and it is a modest one.
Why not use the CRM module our TMS vendor sells?
Look at it honestly first — if it tracks quotes against expiry and shows account trends, use it. Most are a contact list bolted to the shipment screen. The test is whether it can produce a list of accounts whose volume fell this quarter and whose last quote went unanswered. If it can, you are done; usually it cannot.
What is the highest-value list this system produces?
Accounts trending down. Volume falling, exceptions rising, or a quote unanswered past its validity — each is a conversation that saves an account if it happens early. No operational system produces that list, because no operational system is watching the relationship.
How should quotes be tracked without drowning in pipeline stages?
As quotes, not deals: issued, followed up, won, lost or expired, attached to a lane and an account. Two dates and an outcome per quote is enough to know win rates and to chase before expiry. The pipeline metaphor is the thing to drop, not the tracking.
Does this overlap with an importer status portal?
No — they face opposite directions. A status portal tells the importer where their shipment is; this tells your desk how the account is doing. They share the shipment data underneath, which is a reason to build them on the same foundation, not to confuse them.
Last reviewed 27 August 2026