Salesforce for Logistics and Supply Chain

In logistics, the customer experience is mostly the operation itself. A shipment that arrives late with no warning does more damage than any campaign can repair. Yet the operational truth sits in transport and warehouse systems, while account managers, customer service and marketing work in Salesforce with a partial, often delayed view.

Common challenges in logistics

• Operational data is high volume and fast moving. Shipment events, scans and status changes arrive constantly. Copying all of them into CRM is rarely sensible, but sales and service still need the right subset.
• Customers are businesses with many contacts. A shipper may have a procurement lead, several operations contacts and finance users, each needing different information.
• Quotes are complex. Lanes, modes, weights, surcharges and contract rates make quoting slow and error-prone when it lives in spreadsheets.
• Service teams answer the same question all day: where is my shipment? Without proactive updates, every delay turns into a phone call.
• Recipients are often not your customer. In parcel and last-mile work you message consignees on behalf of a shipper, which raises questions about consent, branding and data ownership.

Integration landscape

A logistics provider's Salesforce org is usually surrounded by a transport management system, a warehouse management system, an ERP or billing system, carrier and telematics feeds, and sometimes customer EDI connections. Some patterns that work well:

• Events for change, lookups for detail. Publish meaningful changes (shipment delayed, delivered, exception raised) as platform events or through middleware, and let agents look up full tracking history from the source system when they need it.
• One owner per data item. Decide which system owns customer master data, rates, shipments and invoices, and write it down. Many integration problems trace back to two systems both believing they own the same field.
• Plan for retries and duplicates. Operational feeds will resend, arrive out of order or fail. Integrations should be idempotent, use external IDs and log failures somewhere a person will see them.
• Check platform limits for your volumes. API, event and storage allowances vary by edition and contract. Check current limits for your org in Salesforce Help before deciding how much data to replicate.

Data, consent and compliance

Most logistics data is about businesses, but consignee names, addresses and phone numbers are personal data. GDPR, India's DPDP Act and local rules on commercial messaging may apply depending on where recipients are. Keep service notifications clearly separate from marketing, agree with shippers who is responsible for recipient data, and retain delivery contact data only as long as you need it.