Skip to content

Talk to an integration expert today on 0191 820 1484

Shipping and Logistics

DPD Integration

Zynk's DPD integration turns the orders held in your accounting system, ERP or online store into DPD shipments, then exports the parcel labels ready to print. It works with DPD and DPD Local accounts, and suits UK businesses despatching from Sage 50, Sage 200, Business Central, NetSuite, Shopify or Magento who are tired of copying addresses into a courier website.

Available for

Capabilities may differ depending on the product.

Benefits

Why businesses connect DPD

Shipments created from orders

Delivery addresses, contacts, parcel counts, weights and references come straight from the order, so nobody retypes them into DPD. Each shipment is created against the DPD network code that your mapping selects for that delivery method.

Labels in the format your printer needs

Labels export as HTML or PDF, or in formats built for Citizen thermal printers and for Eltron printers or models with EPL emulation. They save to a folder that your despatch team prints from.

DPD and DPD Local accounts

The connection points at either the DPD or the DPD Local API, using your account number and login. Larger shippers typically hold DPD accounts and smaller businesses DPD Local, and the workflow is the same for both.

No duplicate consignments

With reprocessing prevention switched on, Zynk checks each order's external reference before creating a shipment. If a workflow runs twice, orders already sent to DPD are skipped instead of being booked again.

Labels ready before the packing starts

Workflows run on a schedule through the day, so shipments and labels are waiting when the packing bench needs them, rather than after someone has caught up on data entry.

Capabilities

What you can do with DPD

Every task the Zynk DPD connector can run, grouped by the direction data moves.

Import into DPD

Data Zynk writes into DPD

1 task

  • Shipments → into DPD

Export out of DPD

Data Zynk reads out of DPD

1 task

  • Labels → out of DPD

Need something that isn't listed?

Most DPD projects include at least one custom step. Our team builds it for you.

Talk to us

The problem

Why integrate DPD?

Courier booking is one of the most repetitive jobs in a despatch team. Each order means copying a name, address, phone number and parcel details into DPD, then printing a label and matching it to the right box. Typing mistakes send parcels astray, and the work grows in step with your order volume.

Without integration

  • Addresses copied by hand from the order screen into DPD
  • Mistyped postcodes and phone numbers on consignments
  • Labels printed one at a time from a browser
  • The same order booked twice after a busy afternoon
  • Service choices left to whoever happens to be packing

With Zynk

  • Shipments are created in DPD from the order data itself
  • Address and contact fields reach DPD exactly as they appear on the order
  • Labels for a batch of shipments export to a print folder in one run
  • Reprocessing checks skip orders that already have a shipment
  • Delivery methods map to DPD network codes, so each parcel goes on the right service

How it works

How the DPD integration works

  1. Step 1: Add your DPD account

    Choose the DPD or DPD Local endpoint and enter your account number, username and password. Zynk also connects to the order source, such as Sage 50, Shopify or Business Central.

  2. Step 2: Map services and parcels

    Each delivery method is matched to a DPD network code, and we agree how parcel count, weight, collection date and order references are filled for every consignment.

  3. Step 3: Create shipments and labels

    The workflow creates shipments in DPD, collects the shipment IDs and exports the matching labels to a folder in HTML, PDF or your thermal printer format.

  4. Step 4: Schedule around collections

    Runs are timed to suit your DPD collection, with failed orders written to a fail file so they can be put right before the van arrives.

DPD and Sage 50 UK

Sales orders waiting in Sage 50 are created as DPD shipments, with the customer's delivery address and contact taken from the order rather than retyped by the despatch team.

From Sage 50 UK to DPD:Shipments

View the Sage 50 UK integration →

DPD and Shopify

New Shopify orders become DPD shipments on a schedule you set, and their labels drop into a print folder so the packing bench never waits on a courier booking.

From Shopify to DPD:Shipments

View the Shopify integration →

DPD and Sage 200

Sage 200 sales orders or despatch notes can drive DPD shipment creation, so the warehouse books parcels from the same records that finance and customer service already rely on.

From Sage 200 to DPD:Shipments

View the Sage 200 integration →

DPD and Microsoft Dynamics 365 Business Central

Business Central sales shipments supply the delivery details for each DPD consignment, keeping courier bookings in line with what the ERP records as shipped.

From Microsoft Dynamics 365 Business Central to DPD:Shipments

View the Microsoft Dynamics 365 Business Central integration →

Find your integration →

DPD integration FAQs

Can I create DPD shipments from Sage 50 sales orders?
Yes. Zynk reads sales orders from Sage 50 UK and creates a DPD shipment for each one, using the delivery address and contact held on the order. Labels then export from DPD so your team can print them and pack.
Does Zynk support DPD Local?
Yes. When you set up the connection you choose either the DPD endpoint, typically used by larger businesses, or DPD Local, typically used by smaller ones. The rest of the workflow behaves in the same way for both.
Which label formats can Zynk export from DPD?
Labels can be exported as HTML or PDF, or in the Citizen and Eltron formats used by thermal label printers, including models that support EPL emulation. You choose the format and the folder the labels are saved to.
How do Shopify orders get booked with DPD?
Zynk exports new orders from Shopify, maps each shipping method to a DPD service and creates the shipments in your DPD account. Labels are then downloaded for printing, so packers never copy an address into the DPD website.
What do I need from DPD to set up the integration?
You need your DPD account number, which is normally six digits, plus the username and password for that account. Our team confirms the account type and the DPD services you use before the workflow is built.
Can Zynk stop the same order being sent to DPD twice?
Yes. The shipment import can check each order's external ID against records it has already processed and skip any it has seen before. That protects you from duplicate consignments if a workflow is rerun or an order is exported again.
Which other systems can send orders to DPD through Zynk?
Any system Zynk can export orders or sales documents from, including Sage 200, Business Central, NetSuite, Magento, WooCommerce and BigCommerce. Orders are converted into DPD's shipment format during the workflow, so the source system needs no DPD plugin of its own.
Can DPD shipments be created from NetSuite orders?
Yes. Zynk exports sales orders from NetSuite and creates a DPD or DPD Local shipment for each one, using the delivery address held on the order. Parcel labels then export from DPD as PDF, HTML or thermal printer formats, ready for your team to print and pack.

See what Zynk can automate for your DPD setup

Book a 20-minute call. We'll review your systems, flag the quick wins and outline a practical route to going live.

Book a callSee pricing