Logistics companies use Salesforce for the commercial and customer side of the business, while the transportation or warehouse management system keeps running the freight. For 3PLs and freight brokers that usually means shipper accounts and contacts, lane-level quoting and RFP pipelines, carrier relationships where they matter commercially, service cases for exceptions and claims, and account reviews built on shipment data pulled from the TMS. The hard part is integration: bringing the shipment data people need into Salesforce without copying every tracking event.
Where does Salesforce sit next to the TMS and WMS?
| Data | System of record | What Salesforce needs |
|---|---|---|
| Shipments, loads and tracking events | TMS | Summary volumes by account and lane, plus exceptions that need a person |
| Inventory, orders and warehouse activity | WMS | Order status and service issues for customer-facing teams |
| Rates and tenders | TMS or rating engine | Quoted lanes, rate history and win or loss by bid |
| Shipper accounts, contacts and contracts | Salesforce | The full commercial relationship |
| Claims and service cases | Salesforce, often | Case history linked to shipment references |
How should lane quoting and RFPs work?
Shippers buy by lane, so the opportunity model should too. Many logistics teams track an RFP as one opportunity with lane-level line items: origin, destination, mode, equipment and expected volume. Pricing usually comes from the TMS or a rating tool, and Salesforce records what was quoted and awarded. That makes win rates by lane, mode or region reportable, and it gives account managers a clear view of where they carry freight and where they lost the bid.
- Model RFPs as opportunities with lane line items rather than one lump sum.
- Record awarded lanes and volumes, then compare actual shipments from the TMS against awards.
- Keep spot quotes lightweight; many teams log them in the TMS and summarize in Salesforce.
- Use Revenue Cloud only when quote complexity truly requires it; standard quotes with lane line items are often enough for brokers.
What about carriers?
Carrier onboarding, compliance and load tendering usually stay in the TMS or a dedicated carrier platform. Salesforce helps where carrier relationships are commercial: capacity partnerships, dedicated fleet agreements or partner programs. Keep carriers as separate account types with their own page layouts and sharing, so shipper teams are not cluttered with carrier data.
How does Service Cloud handle exceptions and claims?
- Create cases automatically from TMS exceptions such as missed pickups or delays, linked to the shipper account and shipment reference.
- Route by customer tier and lane so key accounts reach their dedicated team.
- Track claims with documents, amounts and status, and report claim rates by lane and carrier.
- Give shippers an Experience Cloud portal for shipment status, documents and case updates to cut status calls.
Where does AI help first?
- Summarizing a shipper's recent exceptions, volumes and open cases before a quarterly business review.
- Drafting customer updates on delayed shipments for a person to approve.
- Answering routine where-is-my-shipment questions in a portal, using TMS data the agent is allowed to read.
- Highlighting accounts whose volume is falling compared with awarded lanes.
What should a logistics company build first?
- Clean shipper accounts and contacts, with parent and child relationships for large shippers.
- RFP and lane-quote opportunities with consistent stages.
- A TMS integration that brings in volumes by account and lane, plus exceptions.
- Service cases for exceptions and claims.
- Account review dashboards comparing awarded and actual volume.
