Book DPD parcels the moment an order is packed

On most trade accounts, the DPD part of the day looks the same. The warehouse finishes packing, a weight gets passed to the office, and someone types the consignment into DPD’s web portal before copying the tracking number back into the ERP. It takes a few minutes per order, and it lands at the worst possible time, in the hour before the driver arrives.

Zestcode Automation builds bespoke order platforms that book DPD parcels automatically from approved orders: the warehouse marks an order packed, and the platform prices it, books it with DPD, prints the 4x6 label and saves the tracking number to the order in your ERP. It is built around your process, and your company owns it once it goes live.

Following one order through to the DPD van

To see where the minutes go, take a single hypothetical order. A trade customer emails a PDF purchase order for six cartons of fixings and asks for next-day delivery.

1. Approved in the office. A member of the team checks the order in the review queue and approves it. The delivery method, DPD Next Day, comes from the PO or the customer’s account default.
2. Created in the ERP. The sales order is created with the customer’s PO number as its reference, just as it would be keyed by hand.
3. Picked on a handheld. The order appears on a rugged Android device in the warehouse, lines sorted by product group.
4. Packed and weighed. The packer adds two parcels with their weights and dimensions and photographs the packed order.
5. Priced. The platform prices the consignment with DPD, or against your rate card, and updates the delivery charge on the order.
6. Booked and printed. The booking goes through DPD’s API. The label prints at the packing bench and the ship note on the A4 printer.
7. Completed. Tracking number, parcel count and total weight are saved to the ERP order, which is completed so invoicing runs as normal.

Between packing and completion, the only physical job left is sticking the labels on.

What does DPD need to enable on our account?

Bookings run on your existing DPD account at your contracted rates. DPD makes API access available to account customers, but it normally has to be switched on for your account, so early in the specification we ask your DPD account manager to enable it and issue test credentials. The services the platform can book, such as next day, before 12 or Saturday, depend on your contract, and only those are offered on the order.

DPD uses the recipient’s email address and mobile number for its delivery notifications. Where the PO or the customer’s account has them, they are passed through on the booking. Where they are missing, the reviewer sees that before approving the order, while it is still easy to ask the customer.

Catching delivery charges that don’t match the PO

A distributor charging a flat delivery fee on trade orders will now and then send a consignment that costs more than the customer was charged, usually an oversized or unusually heavy one. When the live DPD price differs from the delivery charge on the customer’s PO, the order is held on a list for the office. Someone compares the two figures, decides whether to absorb the difference or amend the order, and only then is it completed and invoiced.

When DPD won’t accept a consignment

Bookings occasionally fail, typically on a postcode DPD doesn’t recognise or an address line over the allowed length. The shipment is marked failed with DPD’s reason in plain English, the office corrects the address and the booking is retried from the same screen. Addresses are checked at review, so most of these are caught before the warehouse ever sees the order.

Each step lands in the audit log. When a customer rings about a parcel, you can see who packed it, when it was booked and its tracking number, without opening the DPD portal.

Cost, timescale and who owns the result

DPD booking is part of the dispatch phase, built alongside the warehouse devices (see how shipping works). A full order to dispatch platform, covering capture, review, ERP sync, warehouse and shipping, is typically £20k–£30k ex VAT across two phases and around 14 weeks. That becomes a fixed price once the written specification is agreed, and the pricing page has the breakdown.

Day-to-day costs are small: hosting at about $25 a month, PrintNode at $9 a month for automatic printing, and a few pence per order for the AI that reads incoming POs. Everything runs in hosting accounts in your company’s name, with no per-user licence, and a maintenance plan is your choice rather than a condition.

To talk it through with your own DPD account and volumes in mind, book a free discovery call.