Shipper accounts and the commercial relationship
A shipper may have many locations, shipping profiles, and contacts across logistics, procurement, and customer service. Model the account to capture lanes, volumes, modes, and service requirements, and track the contract terms that govern them. Knowing which lanes a shipper uses with you and which it gives to competitors reveals growth opportunities, so record share of wallet where it can be estimated.
- Lane and mode information stored with the account.
- Contract terms, service levels, and renewal dates.
- Contacts across logistics, procurement, and finance.
Rate requests and quoting speed
Shippers expect fast answers to rate requests, and the first credible quote often wins. Capture requests with origin, destination, equipment, weight, and timing, and route them to pricing staff with the right information. Track quote outcomes and reasons so you learn where you are competitive. Where rates come from a pricing tool or a carrier-cost system, integrate it so representatives are not rebuilding quotes by hand.
Quoting and revenue solutions →Connecting the transportation management system
Operational detail such as loads, status, and delivery events lives in the TMS. Present summaries in Salesforce so account managers can see shipment performance without logging into another system. Decide which events matter, such as late deliveries or damage claims, and create cases or tasks automatically when thresholds are crossed. Keep the TMS as the system of record for operations, and avoid copying every data point.
Integration planning →Service recovery and exception management
When a shipment is late or damaged, the shipper wants an answer quickly. Use cases to track exceptions with owners, deadlines, and escalation paths, and give customer service the shipment context they need. Analyze causes by lane, carrier, and facility to find systemic problems. Proactive notices about known delays preserve trust better than waiting for the shipper to call.
Carrier and partner relationships
Brokers and forwarders depend on carriers and agents. Record carrier capabilities, safety and insurance documents, lanes served, and performance. Track onboarding and compliance status so only qualified carriers receive loads. A portal can let carriers update documents and view payments, reducing administrative follow-up. Verify with your compliance advisors what documentation must be maintained.
Experience Cloud portals →Pipeline, forecasting and capacity planning
Sales forecasts in logistics need to connect to capacity. A large new contract may require equipment, drivers, or warehouse space before revenue arrives. Share pipeline visibility with operations so they can plan, and tag opportunities by lane and mode to anticipate demand. Win-rate analysis by lane shows where pricing and service are strongest.
Reporting leaders actually use
Executives in logistics want a short list of measures: win rate by lane, revenue and margin by shipper, on-time performance, claims ratio, and quote response time. Build these from the connected data and review them in a regular meeting where commercial and operations leaders sit together. When sales sees service performance and operations sees the pipeline, trade-offs such as accepting a difficult lane for a strategic shipper are made deliberately instead of by surprise. Keep definitions written down so the numbers mean the same thing to everyone, and retire reports nobody opens.
Account reviews with large shippers benefit from the same data. Presenting on-time performance, exceptions resolved, and savings delivered turns a contract renewal from a price negotiation into a conversation about value.
Decisions to settle before configuration starts
- Lane data model. Decide how lanes, modes, and volumes are stored against accounts.
- Quote workflow. Define who prices what and how requests are routed.
- TMS boundary. List which operational events appear in Salesforce.
- Exception rules. Specify which events create cases and who owns them.
A realistic first 90 days
- Days 1 to 30. Map the commercial and service processes, and clean shipper and contact data.
- Days 31 to 60. Configure accounts, rate requests, and the first TMS integration, and pilot with one team.
- Days 61 to 90. Add exception cases and carrier records, train teams, and publish the first win-rate and service reports.
Pitfalls in logistics projects
- Mirroring the TMS. Copying all operational data creates cost and conflicts. Summarize.
- Slow rate requests. A clumsy process loses bids. Optimize speed first.
- No exception ownership. Cases without owners linger. Assign and escalate.
- Forecasts without capacity. Selling what you cannot move damages reputation.
