The DB Schenker connector links the Boostmyshop module's fulfillment workflow to road freight: selecting from preconfigured services, booking transport, storing the freight document, and retaining a tracking reference. It is designed around pallets, cartons, and consolidated freight shipments; DB Schenker's former public portals now lead to DSV.
Carrier label
DB SchenkerDB SchenkerDB Schenker is a freight forwarder whose operations joined DSV in 2025. The existing connector retains the DB Schenker name. For sellers, this is road freight: pallets, cartons, consolidated (groupage) freight, and scheduled departures across a European network, not a small-parcel drop-off flow. The Boostmyshop module handles order orchestration, warehouse checks, and booking; DSV carries the freight.
Your operations cover orders, stock updates, barcode checks, and label creation.
Prepares shipment data and prints the DB Schenker label at packing.
Shipment handed over to DB Schenker.
DB Schenker does not import sales orders. A Shopify, WooCommerce, or PrestaShop store, or a marketplace, feeds the Boostmyshop module first; the freight booking is then created during fulfillment, regardless of the originating channel.
During fulfillment, myFulfillment creates the DB Schenker booking with the service, recipient, package type, Incoterm, and pickup window, then stores the returned barcode document for PDF or ZPL printing.
See the featureThe connector presents the allowed DB Schenker services, including FR PALETTE and SYSTEM options, with the price set in your matrix. It does not request a live carrier quote.
See the featureThe booking ID returned by DB Schenker is stored as the shipment reference and used to build the public tracking link. The connector pulls back neither transport events nor statuses.
Booking ID received when the booking is created · no transport status pulled back
See the featureAn order from a connected sales channel reaches the Boostmyshop module's OMS before it is assigned to DB Schenker. The forwarder is not the order source; it enters the workflow during fulfillment.
Inbound: validated, paid orders from connected channels, about every 5 minutes.
See the featureWhen the DB Schenker shipment is confirmed, the Boostmyshop module deducts the shipped items and sends available stock to connected channels. No inventory or selling price is sent to the forwarder.
Outbound: available stock to sales channels after shipment confirmation.
See the featureIn cross-docking, a supplier pallet can be scanned at receiving, matched to an existing customer order, and routed to packing. The DB Schenker booking is created only after that operator check.
See the feature| Data | When |
|---|---|
| In | |
| Validated and paid order | about every 5 minutes from the connected channel |
| Barcode document and booking ID | in the booking response |
| Out | |
| Weight, volume, package type, Incoterm, and instructions | when the DB Schenker booking is created |
| Available stock | to sales channels after shipment confirmation |
Our operator's view: DB Schenker supplies the road network; the Boostmyshop module keeps a pallet or consolidated freight shipment from becoming an isolated parcel record in a separate portal.
| Solution | Carton or pallet booking | Road services and configured prices | Live carrier quote | Barcode document at the station | Orders from multiple channels | Warehouse checks and cross-docking | Synchronized delivery events | Available stock returned to channels |
|---|---|---|---|---|---|---|---|---|
DB Schenker via the Boostmyshop moduleRecommended | Supportedduring fulfillment | Supportedinternal matrix | No | SupportedPDF or ZPL | Supportedconnected channels | Supportedbefore booking | No, reference only | Supportedafter shipment confirmation |
DSV / Schenker portal | Supportedby portal entry | Partially supportedDepends on the account | Depends on the DSV service | Supportedto download | Not supported | Not supported | Portal lookup | Partially supportedOutside the carrier portal |
Custom road API integration | Supportedto build | Partially supportedTo build | To build | Partially supportedTo build | Partially supportedTo build | Partially supportedSeparate WMS | To build | Partially supportedDepends on WMS depth |
Comparison based on the official documentation and myFulfillment docs. The limit is stated under the "Partial" badge; no rating, no sponsored placement.
See how the DB Schenker integration fits into your operations
Teams connecting DB Schenker to the Boostmyshop module prepare a road-freight shipment for an order that is already centralized. They choose a configured service, check the package type and dimensions, enter pickup instructions, and create the booking without re-keying the address in a separate carrier portal.
For a palletized load, the rule can propose FR PALETTE; the operator confirms weight, volume, and package type before sending the DB Schenker booking.
An order for a business customer is assigned to a configured SYSTEM or export service. The displayed price comes from the internal matrix, so it is never presented as a live DSV quote.
In cross-docking, the received pallet is checked and matched to the customer order. The goods move to packing, then the DB Schenker booking is created for the outbound leg.
Address, goods description, Incoterm, handling instructions, optional insurance, and pickup window feed the booking. The barcode document and booking ID are returned through the same workflow.
A pallet received from a supplier for an existing customer order is waiting to be matched to that order, checked, and handed over to the road-freight network.
The Boostmyshop module routes the item through verification, then prepares the DB Schenker booking without forcing it into a parcel workflow.
Read the full storymyFulfillment sits in the middle, so DB Schenker can create labels for orders received from your sales channels. A few live pairings below.
Your Shopify store orders are prepared in myFulfillment; the DB Schenker label is printed during packing.
Guide
Amazon orders are centralized in myFulfillment; the DB Schenker label is printed during packing.
Guide
Your BigCommerce store orders are prepared in myFulfillment; the DB Schenker label is printed during packing.
Guide
Cdiscount orders are centralized in myFulfillment; the DB Schenker label is printed during packing.
Guide
Fnac / Darty orders are centralized in myFulfillment; the DB Schenker label is printed during packing.
Guide
Groupon orders are centralized in myFulfillment; the DB Schenker label is printed during packing.
Guide
Leroy Merlin orders are centralized in myFulfillment; the DB Schenker label is printed during packing.
Guide
Your Magento store orders are prepared in myFulfillment; the DB Schenker label is printed during packing.
Guide
ManoMano orders are centralized in myFulfillment; the DB Schenker label is printed during packing.
Guide
Mirakl orders are centralized in myFulfillment; the DB Schenker label is printed during packing.
Guide
Your PrestaShop store orders are prepared in myFulfillment; the DB Schenker label is printed during packing.
Guide
Temu orders are centralized in myFulfillment; the DB Schenker label is printed during packing.
Guide
Veepee orders are centralized in myFulfillment; the DB Schenker label is printed during packing.
Guide
Your WooCommerce store orders are prepared in myFulfillment; the DB Schenker label is printed during packing.
GuideA DB Schenker / DSV business account with API access is required. The connector covers a configured selection of domestic and export road services, with cartons or pallets, booking, and a barcode document. Because former Schenker portals have moved to DSV, credentials must be validated during rollout. The tracking reference is stored, but delivery events are not synchronized.
Yes. DSV completed its acquisition of Schenker in April 2025 and later moved dbschenker.com under dsv.com. The connector retains the DB Schenker name because that is the historic account and flow name; customer access, support, and current road documentation now sit with DSV.
Yes, within a configured road-freight scope. The connector includes FR PALETTE, FR SYSTEM, and several export SYSTEM services. Package type can be set to carton, Euro pallet, or one-way pallet, with weight and dimensions. The exact service depends on what your account allows.
No. The connector loops through the allowed services and displays the price defined in the account matrix inside the Boostmyshop module. It does not request a live quote from the carrier. Displayed dates are local estimates too; they are not a DSV delivery commitment.
The response contains a barcode document and booking ID. The document is stored with the shipment and can be printed as PDF A4, PDF A6, or ZPL, depending on the station setting. This document accompanies a freight shipment, not a standard parcel label.
No. The booking ID is stored as the tracking reference and used to build the shipment's public tracking link. The connector does not retrieve delivery scans, milestones, or statuses. Use DSV or Schenker tracking services to check the shipment status.
You need an access key, a group ID, and a test or production environment. Your DB Schenker / DSV contact provides the API access tied to your account. Since online services have moved to DSV, validate those credentials during implementation.
Yes, when the sales channel is connected to the Boostmyshop module. The order reaches the OMS first; the operator prepares it, selects the road service, and creates the DB Schenker booking. This is not a separate DB Schenker module installed in every storefront.
Cross-docking is handled by the Boostmyshop module: the pallet received from the supplier is matched to an existing customer order, then routed to packing. Once the check is complete, the connector creates the DB Schenker booking for the outbound transport.
DB Schenker covers shipping. Connect your sales channels and tools too.
DB Schenker integration for pallet and consolidated freight
See it in your own setup
