Connect BigCommerce with Schenker (DB Schenker, now part of DSV) to automate shipping labels, live tracking, shipment status updates, returns flows, and B2B/B2C delivery rules.
• Order, customer, and address data is read from BigCommerce and mapped to DB Schenker shipment entities, including service level, package details, and reference fields.
• Shipment creation requests are sent to Schenker via API, and carrier responses are stored against the BigCommerce order as shipment records and fulfillment metadata.
• Shipping labels are generated by Schenker and returned as printable documents (for example, PDF/ZPL), with label identifiers linked to the corresponding BigCommerce shipment.
• Tracking numbers are written back to BigCommerce, and tracking URLs are resolved using Schenker tracking endpoints where available.
• Shipment status events are polled or consumed via webhook-style callbacks when supported, then normalized into BigCommerce-friendly status updates and order notes.
• Return labels and RMA-linked shipments are created using return-specific endpoints and mapped to BigCommerce return workflows when present.
• B2B vs. B2C delivery rules are handled through mapped service codes, Incoterms-related fields when required, and validation of address, phone, and pickup/drop-off constraints.
• Sync jobs log payloads, responses, and retry states, with idempotency keys used to prevent duplicate shipments on reprocessing.
.png)
It pushes BigCommerce order data to Schenker/DB Schenker to create shipments and labels, then writes tracking numbers and shipment status events back to BigCommerce.
Yes, we can map shipping methods, service levels, cutoff times, and address requirements by customer type, destination, or warehouse logic.
Typically this includes shipment created, in transit, out for delivery, delivered, exception, and failed delivery, depending on the Schenker event feed available in your region.
Yes, it can generate return shipments, store return label links, and sync return tracking and status to keep support and customers aligned.
We integrate against the active Schenker/DB Schenker APIs and align naming, credentials, and endpoints to your carrier setup, while keeping the build flexible if DSV-led changes affect services.










