CRM for logistics: how to manage customers, requests, shipments, and communications

A CRM for logistics helps connect customers, their requests, agreements, and follow-up activities in one unified workflow. Let’s explore how to organize this process and what kind of operational model you can build in Uspacy.

Lost business often starts long before a shipment falls through. All it takes is leaving a request without an assigned owner or failing to inform a colleague about a change in the loading date.

A sales manager receives an inquiry by phone, promises to calculate the shipping cost, and then gets distracted by an urgent issue. The request remains in their memory, and the customer turns to a competitor. In another scenario, the rate is revised in a conversation, but the previous amount remains in the shared spreadsheet.

For a carrier operating its own fleet, this creates a risk of agreeing to terms without confirming vehicle availability. For a freight forwarder, it may mean passing incomplete cargo requirements or inaccurate timelines to a partner. The consequences are similar: repeated clarification requests, conflicting commitments, and lost orders.

Review the progress of several recent inquiries. Where is each request recorded? Who is responsible for calculating the cost? How are agreed terms communicated to the team? These are exactly the points where shared record-keeping procedures are needed—especially when employees have to search through private messages to find the information they need.

CRM and TMS systems help manage different aspects of a logistics business. A CRM organizes customer relationships and business agreements, while a TMS focuses on transportation planning and execution.

In a CRM system, managers work with customers: they receive inquiries, prepare quotes, record agreed rates, and schedule follow-up communications. A complete interaction history makes it easier to review negotiation details, hand over an account to a colleague, or offer the customer another shipment.

A TMS helps organize deliveries: it supports route planning, order allocation across vehicles, carrier selection, and shipment execution tracking. The available features depend on the product: some solutions focus on last-mile delivery, while others cover complex transportation operations.

The right TMS depends on the types of transportation and the complexity of your operations. For example, SAP Transportation Management and Oracle Transportation Management help companies plan shipments, select carriers, monitor execution, and calculate transportation costs. Evaluate these solutions based on your specific use cases, such as coordinating deliveries between warehouses, managing multiple carriers, or overseeing international shipments.

CRM and TMS capabilities may overlap, and whether you need to integrate the two systems depends on your company's workflows. If customer inquiries and agreements are getting lost, start by improving customer management with a CRM. If route planning and vehicle capacity management are the main challenges, consider the relevant TMS capabilities. If you need both systems, define which data and statuses should be shared between them to ensure your team works with consistent, up-to-date information.

Each request should have its own record, an assigned owner, and a clearly defined next action. This allows the team to see which inquiries are still being processed and which have already become orders. Establish a clear workflow: new request → requirement clarification → cost calculation → terms approval → order confirmation. Define criteria for each stage transition. For example, cost calculation begins once all the necessary cargo details have been received, and an order is considered confirmed once all key terms have been agreed upon.

If information is missing, the manager should schedule a follow-up with a specific deadline. The request remains active, with a clearly defined next step.

For recurring customers, create separate records for each new shipment and link them to the same company profile. This preserves the relationship history without mixing up routes, rates, and agreements from different orders.

Once an order is confirmed, it moves into the execution stage along with all agreed terms. The logistics coordinator or dispatcher must have enough information to arrange the shipment without having to ask the customer for the same details again.

Define clear areas of responsibility. The sales manager agrees on commercial terms, the logistics coordinator selects a carrier or arranges company-owned transportation, and the accounting team verifies documents and payments. Also, establish who is responsible for notifying the customer about any changes.

If the customer reschedules loading, record the new date, who approved the change, and how it affects the cost. Create a task to notify the carrier and obtain confirmation. Store approved requests, contracts, invoices, and transportation documents linked to the relevant order.

Track customer payments and payments to carriers separately, as amounts, deadlines, and statuses may differ. A delivered shipment does not necessarily mean the financial process is complete. Include document and payment verification in your workflow, even after transportation has been completed.

In Uspacy, you can build a workflow around customers, commercial requests, and order execution. Start with the essential relationships and add more detail as your team's needs evolve.

Use Contacts and Companies to manage customers, contact persons, and partners. Add an attribute that helps distinguish between customers and carriers. Use Deals to process requests, clarify requirements, calculate costs, and agree on terms.

If shipment execution requires a separate workflow, create a Smart Object called “Shipment.” Add fields for routes, dates, and carriers, and establish relationships with the customer and the corresponding deal. Set up activities and tasks for everyone involved, and define access permissions. Track shipment stages and financial statuses separately so that delivery does not automatically mean all payments and settlements are complete.

If your company already uses a TMS, you can connect it to Uspacy through the open API. For example, you can configure the transfer of approved orders from the CRM to the transportation system and send shipment status updates back to Uspacy. This allows managers to monitor execution and keep customers informed without having to enter the same data twice. Specific integration scenarios depend on the API capabilities of both systems and require integration setup.

Launch the selected workflow for one transportation route. Agree on the required fields, responsible team members, and information update rules, then test the setup using real requests. If you are integrating with a TMS, also verify that data and status updates are transferred correctly. Track response times, the number of requests without a defined next action, conversion rates from inquiries to orders, and repeat inquiries.