Connect Salesforce with Schenker (DB Schenker, now part of DSV) to automate label creation, shipment tracking, status updates, returns, and B2B/B2C delivery rules.
• Orders, ship-to addresses, package details, and selected service levels are mapped from Salesforce objects to DB Schenker shipment request payloads, with B2B/B2C delivery rules applied via fields such as Incoterms, time windows, and carrier product codes.
• Shipment creation calls return carrier shipment identifiers plus label documents, which are stored against the Salesforce order/shipment records and linked for printing and audit.
• Tracking numbers are written back to Salesforce and associated to the correct shipment and package lines to support split shipments and partial fulfillments.
• Shipment status events are synchronized into Salesforce via scheduled polling or webhook-style callbacks (when available), with state mapping to in-transit, delivered, exception, and returned flows.
• Return shipments reuse original order references and RMA data where present, generating return labels and updating return status back into Salesforce.
• Sync runs handle delta updates, retries, and idempotency keys so repeated calls do not duplicate shipments, while failures are logged with correlation IDs for traceability.
.png)
We map Salesforce order, address, and service-level data to DB Schenker shipment creation, then write label links, tracking numbers, and carrier events back to the Salesforce order record.
Typically shipped, in transit, out for delivery, delivered, exception, and failed delivery, plus timestamps and tracking URLs, depending on the Schenker event feed you use.
Yes – we implement rule logic for service level, incoterms, cutoff times, and split shipments, so B2B and B2C flows follow the right carrier product and labeling rules.
It can generate return labels, store them on the case or order, and sync return tracking events back to Salesforce to reduce “did you receive it?” support tickets.
Yes – we’ve delivered 2,100+ eCommerce projects since 2003, and we design integrations with rate limits, retries, and audit logs to keep shipment updates reliable at volume.





