How to integrate PostNL, DHL and DPD in one workflow
Dutch sellers often need PostNL for domestic parcels, DHL for cross-border lanes and DPD for specific B2B or pickup flows. ChannelDock’s Integrations page is the natural starting point for connecting carriers, marketplaces and webshops into one shipping operation.
each carrier account
orders by lane
labels from one queue
A multi-carrier setup matters because the best carrier changes by destination, parcel size, delivery promise, pickup cutoff and marketplace requirement.
Before you start: what you need
A PostNL, DHL and DPD workflow only becomes reliable when carrier access, order data and marketplace settings are ready before the first label is printed.
Collect account numbers, API credentials, label formats, pickup agreements and the services each warehouse may use.
Make sure order weight, dimensions, destination country, delivery promise and phone or email fields are available before carrier selection.
Give operations managers access to carrier settings, while packers follow the approved workflow in the order queue.
Step-by-step: integrate PostNL, DHL and DPD
Use this workflow to move from separate carrier portals to one controlled shipping process.
Map your carrier use cases first
List which orders should use PostNL, which should use DHL and which should use DPD. Include domestic parcels, EU cross-border shipments, pickup points, B2B deliveries, bulky products and return labels.
Collect the required carrier credentials
Request API access, contract references and label permissions from each carrier. Store them securely and check whether the account can create production labels, not only test labels.
Connect the carriers in ChannelDock
Open ChannelDock Integrations and connect the carrier accounts you use in daily operations. Keep the naming clear, especially if you ship from more than one warehouse or legal entity.
Connect marketplaces and webshops to the same order queue
Bring bol.com, Amazon, Shopify, WooCommerce and other channels into the same workflow so labels and tracking updates start from one source of truth.
Define carrier selection rules
Use Shipping Rules to choose carrier services by destination, weight, parcel size, marketplace, pickup cutoff and delivery promise.
Print test labels before going live
Run a small batch of real order scenarios: a Dutch parcel, a Belgian or German shipment, a DPD pickup-point order and a marketplace order that needs tracking uploaded quickly.
Train the packing bench on exceptions
Show packers where to see the chosen carrier, how to print or reprint a label, and when to hold an order instead of manually switching carriers.
Monitor failed labels and tracking uploads
Review failed label requests, missing address fields, carrier service errors and marketplace tracking delays during the first two weeks. Fix the source data or rule instead of patching each order manually.
The multi-carrier flow at a glance
Carrier integration should feel like one shipping workflow, not three disconnected portals.
The goal is not to make every carrier available to every order. The goal is to make the right carrier available at the right moment.
Common multi-carrier integration pitfalls
- Connecting a carrier account before confirming which services are active on the contract.
- Using different address formats in each marketplace, causing label errors after the order reaches the packing bench.
- Letting PostNL, DHL and DPD rules overlap so two services could match the same order.
- Forgetting to test tracking upload back to bol.com, Amazon or the webshop after label creation.
- Leaving old carrier portal workflows active, which creates duplicate labels and split tracking history.
Separate carrier portals vs. ChannelDock Integrations
Separate portals can work for a few parcels. They break when order volume, marketplaces and carrier exceptions grow.
Without ChannelDock
- Operators copy order data into PostNL, DHL and DPD portals manually.
- Labels, tracking numbers and shipment statuses live in separate systems.
- Carrier choice depends on the person packing the order that day.
With ChannelDock
- Carrier connections sit next to marketplace, webshop and order workflows.
- Shipping rules, Bulk Processing and label printing use the same order data.
- Tracking can flow back to the sales channel without retyping numbers.
PostNL, DHL and DPD integration FAQ
Related workflows to improve next
Once carriers are connected, strengthen the workflows around labels, rules and order volume.
Print shipping labels
Turn carrier connections into reliable label and tracking flows.
Read the how-toConnect PostNL, DHL and DPD without three separate workflows
Use ChannelDock Integrations to connect carriers, marketplaces and webshops so labels and tracking stay in one operational flow.