Custom DPD integration
Appfront connects DPD Netherlands (and the European DPD organisations) to your webshop, ERP or warehouse system. Labels from DPD Webservices, pickups requested on time, track & trace that flows through to the customer and returns that come back automatically - no more manual labels in the DPD portal.
What is DPD?
DPD - Dynamic Parcel Distribution - is one of Europe's largest parcel carriers, operating in the Netherlands as DPD Nederland. For e-commerce shipments up to 31.5 kilos, DPD typically delivers the next working day to business and consumer addresses.
Compared with PostNL, DPD is stronger in B2B shipments and in cross-border delivery within Europe - an important argument for webshops that want to deliver directly to Belgium, Germany or France without handing over to a second carrier. DPD's sorting network uses the same scan steps across Europe, so the track & trace feed stays the same across borders.
DPD Webservices
DPD's API suite for creating shipments, generating labels, requesting pickups and retrieving track & trace. Available as REST/JSON or (older) SOAP. Requires a delISID and credentials per shipping location.
Pickup & depot integration
Cut-off times per depot determine whether a pickup is still collected the same day. A good integration knows which pickup time your orders need to make and schedules shipment deadlines around the right cut-off.
Track & trace events
Status updates from DPD via webhooks or polling: created, picked up, in transit, delivered, returned, not delivered. Passed on to customers by email or SMS, internally to your service desk, and into your dashboard.
How we build your DPD integration
A carrier integration is judged above all on how smoothly it runs in day-to-day operations. Our approach has four phases, focused on working labels and correct cut-off times.
DPD account & API access
We help you request API access from DPD Netherlands: a delISID per shipping location and credentials for the Webservices. Sandbox first, production only after functional acceptance. Including signing the API contract.
Products & shipping rules
Which DPD product do you use per shipment: Classic, Predict, front-door delivery, parcel shop, international? Which rules (weight bands, dimensions, cash on delivery, age verification) do we send along? We settle this before writing any code.
Label flow & printer integration
We retrieve labels from the Webservices as PDF (universal) or ZPL (for Zebra printers in the warehouse). The flow is hooked straight into your WMS, ERP or webshop backend, so warehouse staff get the label alongside the packing slip.
Track & trace, returns, monitoring
Track events are sent to customers and dashboards. Return labels are generated where relevant. Monitoring of API errors and missed cut-offs gives you a warning before shipments are left sitting. Maintenance contract for ongoing support.
Which DPD integrations do we build?
Most DPD integrations revolve around the same four processes, but the details vary widely by setup and industry.
Webshop → DPD label
An order in your webshop automatically becomes a DPD shipment with a label, the selected DPD product and the correct pickup location. For Shopify, WooCommerce, Magento, Lightspeed or custom webshops.
WMS integration
Print labels at the pick location straight from your WMS (Magento Order Management, Brink, Onbel, in-house WMS). ZPL output for Zebra printers and address validation before the label is generated.
ERP integration
ERP integration
Customer communication
Pass the track link with the DPD status on to the customer by email, SMS or WhatsApp. With a landing page on your own domain, so the tracking reflects your brand rather than the DPD portal.
Returns via DPD
Generate return labels via the Webservices, with automatic processing on receipt and integration with your stock and refund flow. Including a portal where customers can register a return themselves.
Multi-carrier strategy
DPD alongside PostNL, DHL or UPS. Carrier selection per shipment based on destination, weight, speed or contract rates. A solid fallback flow for when a carrier's API is down.
Which companies do we work with on DPD?
DPD is a strong fit for webshops with cross-border shipments, B2B deliveries and organisations that want to take their customer experience around parcel shipments more seriously.
Cross-border webshops
Webshops that deliver from the Netherlands to Belgium, Germany and France without a second carrier or customs hand-offs. DPD's European sorting network enables consistent tracking across borders.
B2B wholesalers
Wholesalers and distributors with daily shipments to business customers. DPD's business delivery preferences and Predict time slots suit fixed delivery addresses with opening hours.
Scalable D2C brands
Webshops that have outgrown their shipping tool and want a direct carrier integration for control over costs, product choice and branding of the tracking page.
Logistics service providers
Fulfilment providers and 3PL companies shipping from a central warehouse for multiple clients. Multi-account DPD setup with label output across different delISIDs.
Our technical approach
A DPD integration that works reliably in production requires attention to cut-off times, label formats, error handling and monitoring.
Cut-off times are crucial: a shipment that misses the pickup request after the cut-off is collected a day later. We monitor the cut-off in a schedule per depot and show a warning in the operational tooling before time runs out. We retrieve labels as PDF or ZPL, depending on the printer stack in the warehouse. Address validation runs up front, so an incorrect address doesn't only surface from the DPD API at the label call.
For production stability, we use idempotency keys on every shipment create to prevent duplicate shipments on retries. We process webhooks asynchronously via a queue, so a slow downstream flow doesn't cause a DPD callback to time out. We monitor the shipment-create error rate, label-print latency and webhook-receive lag, with alerts to your service team before a day's work goes wrong.
Tech stack
Why Appfront for your DPD project?
DPD integrations look simple: generate a label and pass on a tracking event. Until you hit production, where cut-offs, retries, multiple accounts and tracking formats all come together.
- Works alongside your existing webshop, ERP or WMS
- Cut-off monitoring with advance warnings
- Labels in PDF or ZPL for warehouse printers
- Returns flow with customer portal
- Multi-carrier ready: DPD alongside PostNL, DHL and UPS
- Monitoring with alerts on error rates and missed cut-offs
- Maintenance contracts for ongoing support
DPD versus PostNL, DHL and UPS
In the Netherlands, we often see a mix of carriers. DPD has strengths in specific areas, other carriers in others. A good strategy chooses per shipment.
DPD performs well on cross-border deliveries within Europe and on B2B delivery. PostNL is more dominant in pure consumer delivery in the Netherlands and has more pick-up points. DHL is stronger for heavy and non-European shipments. UPS has the tooling and service level for enterprise volumes but is more expensive for SMEs.
We build multi-carrier integrations in which the right carrier is chosen per shipment based on destination, weight, speed and contract rate. DPD for cross-border BE/DE/FR, PostNL for parcel-shop deliveries in the Netherlands, DHL for heavier shipments or destinations outside Europe. With a fallback if a carrier API has temporary problems.
- Rule-based carrier choice per shipment
- Multi-carrier label generation
- Fallback strategy for API outages
- Rate comparison per shipment
- Central track & trace across all carriers
- Reporting on shipping costs and service levels
Frequently asked questions about DPD integrations
European parcel carrier, in the Netherlands DPD Nederland. Strong in B2B shipments and cross-border within Europe, with its own sorting network and uniform track & trace events across borders.
DPD Webservices in REST/JSON for modern implementations; the older SOAP services for legacy integrations or if your system still requires them.
You need a DPD account, a delISID per shipping location and a signed API contract. We guide you through the application and start development in the sandbox.
PDF for general printers, ZPL for Zebra label printers in the warehouse. We determine which format best suits your hardware stack.
We schedule cut-offs per depot and raise warnings in the operational tooling before the deadline passes. This stops shipments from sitting for a day after the cut-off.
Yes - DPD alongside PostNL, DHL or UPS, with carrier selection per shipment based on destination, weight and rate. With central track & trace across all carriers.
Return labels via Webservices, a customer portal for self-registration, and automatic processing in your stock and refund flow as soon as the shipment is back.
A simple label flow from a webshop: three to five weeks. A multi-carrier setup with WMS integration and a returns portal: eight to twelve weeks, delivered in iterations.
Ready to integrate DPD with your systems?
Book a no-obligation advisory call. We'll map your shipping flow, choose the right DPD products and, within a week, give you a concrete approach and indicative price for your integration.