The DACHSER integration links fulfillment in myFulfillment to the European Logistics network. The Boostmyshop module requests a quotation, creates the shipment, retrieves the label and SSCCs, and stores the tracking events in the shipment record. Your carrier account and transport contract remain with DACHSER.
Carrier label
DACHSERDACHSERDACHSER European Logistics is the group's road transport network for groupage, less-than-truckload, and full-truckload shipments across Europe. In myFulfillment, the Boostmyshop module steps in after the order and shipping unit have been checked. It sends DACHSER the information required for a quotation or transport order, then attaches the response to the prepared shipment record. The operator can review the returned amount, produce a PDF or ZPL label, and keep each SSCC without re-keying data in eLogistics. For tracking, DACHSER returns each event with its date, code, description, and location. The eLogistics portal remains available for account management and operations outside the connector's scope.
Your operations cover orders, barcode checks, and label creation.
Prepares shipment data and prints the DACHSER label at packing.
Shipment handed over to DACHSER.
An eligible order from a connected store or marketplace first enters myFulfillment. Once fulfillment is checked, the Boostmyshop module requests a quotation from DACHSER or creates the shipment, then stores the documents and tracking in the same record.
At the packing station, the Boostmyshop module sends DACHSER the division, service, weight, and addresses. The response returns a PDF or ZPL label and one SSCC for each shipping unit.
DACHSER label and SSCC returned after shipment creation
See the featureThe connector queries DACHSER with the tracking number, stores each event's date, code, description, and location, then maps the latest status for the logistics team.
DACHSER events imported when tracking is refreshed
See the featureFor each eligible road service, the Boostmyshop module requests a DACHSER quotation with the destination and pallet characteristics. The returned amount informs the operator's selection.
See the featureThe DACHSER shipment starts from an order already centralized in the myFulfillment OMS. The team checks the address, warehouse, and shipping method before requesting a quote or creating the shipment.
Order checked in the OMS before the DACHSER request
See the featureWhen a pallet received from a supplier matches a waiting order, myFulfillment identifies it by scanning its barcode and routes it to packing without put-away. The DACHSER shipment is created after that check.
See the feature| Data | When |
|---|---|
| Out | |
| Quotation request | for each eligible road service reviewed |
| Transport order | after shipment confirmation |
| CSV manifest | when the prepared batch is dispatched |
| In | |
| DACHSER amount | with the quotation response |
| Label and SSCC | with the creation response |
| Tracking events | on the configured refresh schedule |
DACHSER provides the road network and digital services. The integration fits warehouses that prepare pallet freight and need the quotation, documents, and tracking in one shipment record.
| Solution | Road freight quotation | Check before transport order | PDF or ZPL label | SSCC per shipping unit | Tracking events | Dispatch manifest |
|---|---|---|---|---|---|---|
DACHSER with the Boostmyshop moduleRecommended | Supportedin the shipment record | Supportedin the fulfillment workflow | Supportedattached to the shipment | Supportedkept with the shipment record | Supportedimported into myFulfillment | SupportedCSV uploaded by FTP or SFTP |
DACHSER eLogistics only | Supportedin the DACHSER portal | Partially supporteddata entered in the portal | Supportedproduced in eLogistics | Supportedvisible in the DACHSER tool | Supportedreviewed in eLogistics | Supportedbased on the account workflow |
Direct development with DACHSER APIs | Partially supportedbased on the implemented API | Partially supportedto be built in the calling system | Partially supportedwith the Label API | Partially supportedbased on the implementation | Partially supportedwith Shipmentstatus or Shipmenthistory | Partially supportedto be developed |
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 DACHSER integration fits into your operations
In the warehouse, the integration takes over when a checked order must enter the DACHSER road network. The operator prepares the pallet, reviews the quotation for an allowed service, and produces the documents without leaving the shipment record.
The destination, weight, dimensions, and loading meters are included in the request. The amount quoted by DACHSER is attached to the relevant service before the operator makes the final selection.
After creation, DACHSER returns the label and SSCCs. The Boostmyshop module attaches each tracking reference to the prepared shipment.
Ready shipments are grouped in a manifest file. The connector can upload it to the FTP or SFTP server configured for DACHSER.
The tracking refresh imports the DACHSER history and maps the latest event to an operational status for the logistics team.
Pallet data is re-keyed in a carrier portal, while the references remain separate from the prepared shipment record.
The DACHSER quotation, label, SSCC, and tracking are attached to the shipment checked in the warehouse.
Read the full storymyFulfillment sits in the middle, so DACHSER can create labels for orders received from your sales channels. A few live pairings below.
Your Shopify store orders are prepared in myFulfillment; the DACHSER label is printed during packing.
Guide
Amazon orders are centralized in myFulfillment; the DACHSER label is printed during packing.
Guide
Your BigCommerce store orders are prepared in myFulfillment; the DACHSER label is printed during packing.
Guide
Cdiscount orders are centralized in myFulfillment; the DACHSER label is printed during packing.
Guide
E.Leclerc orders are centralized in myFulfillment; the DACHSER label is printed during packing.
Guide
Fnac / Darty orders are centralized in myFulfillment; the DACHSER label is printed during packing.
Guide
Groupon orders are centralized in myFulfillment; the DACHSER label is printed during packing.
Guide
IBS.it orders are centralized in myFulfillment; the DACHSER label is printed during packing.
Guide
Leroy Merlin orders are centralized in myFulfillment; the DACHSER label is printed during packing.
Guide
Your Magento store orders are prepared in myFulfillment; the DACHSER label is printed during packing.
Guide
ManoMano orders are centralized in myFulfillment; the DACHSER label is printed during packing.
Guide
Mirakl orders are centralized in myFulfillment; the DACHSER label is printed during packing.
Guide
Your PrestaShop store orders are prepared in myFulfillment; the DACHSER label is printed during packing.
Guide
Temu orders are centralized in myFulfillment; the DACHSER label is printed during packing.
Guide
Veepee orders are centralized in myFulfillment; the DACHSER label is printed during packing.
Guide
Your WooCommerce store orders are prepared in myFulfillment; the DACHSER label is printed during packing.
GuideA DACHSER customer account, API token, and the European Logistics services covered by your contract are required. The Boostmyshop team configures the module, branch, shipping units, and label format during onboarding. The connector covers quotations, transport orders, PDF or ZPL labels, SSCCs, manifests, and tracking. Pickup points and return creation remain outside this exchange.
It covers three connector capabilities: road freight quotations, PDF or ZPL label creation with SSCCs, and tracking-event imports. The dispatch manifest completes the operating workflow.
The integration covers DACHSER European Logistics, DACHSER's road transport network in Europe: groupage, less-than-truckload, and full-truckload shipments.
You need a DACHSER account and API access. During onboarding, the Boostmyshop team adds the token, enters the branch and customer number, enables the contracted services, and validates a test shipment.
The service families offered include Targoflex, Targospeed, Targofix, Classicline, and Targo On-Site. The available choices depend on your contract, branch, and approved configuration.
The module sends the destination and shipping-unit characteristics to the DACHSER Quotation API. The amount returned for the eligible service appears in the shipment record before the operator decides.
Yes. The connector requests the label in the configured PDF or ZPL format. DACHSER also returns the SSCCs, which the module attaches to the prepared shipping units.
On the configured refresh schedule, the connector queries DACHSER with the tracking number. It stores each event's date, code, description, and location, then updates the operational status.
Yes. For ready shipments, it builds a CSV file with the required references, units, and shipment data, then uploads it to the configured FTP or SFTP server.
No. The DACHSER integration does not offer pickup-point delivery or return labels; returns follow the process agreed with DACHSER.
DACHSER covers shipping. Connect your sales channels and tools too.
DACHSER integration for pallets, rates, and tracking
See it in your own setup
