# DPD dispatch integration

> Connect DPD dispatch to your warehouse. Consignment, collection and tracking follow packed status, not a browser tab. Built for UK wholesale and ecommerce ops.

When an order is packed, DPD should already be in the loop. Dispatch is part of the warehouse system, not a browser tab on the side.

**Problem:** Packed orders wait while someone creates a DPD consignment by hand, copies a tracking number, emails a driver, and tells the customer. The warehouse knew it was ready an hour ago.

**System:** Warehouse release triggers the courier path: consignment, collection window, driver notification, customer update. Status belongs on the order, not in a copied email.

**Outcome:** Collections happen against warehouse truth. Tracking is a system fact. People stop being the API between packing bench and courier.

DPD is a common UK collection and delivery partner for wholesale and ecommerce operations. The failure mode is always the same: the warehouse and the courier portal disagree because a person is in between.

OnDraft treats dispatch as an operational event. Packed and ready is a warehouse state. Arranging DPD pickup and notifying the customer follow from that state, and Bud can start that work too when the system is connected.

We scope services, accounts and label rules against your DPD setup. We do not claim an official DPD marketplace badge.


## FAQs

### Do you have a DPD app for my ERP?

No. We do not claim an official DPD marketplace listing or a ready-made app for each ERP. We scope label rules and accounts against your DPD setup, connect from warehouse state, and send tracking back to your ERP or shop.

### Do you only work with DPD?

DPD is a frequent requirement. The same design applies to other couriers: warehouse state in, consignment out, status back.

### Can Bud arrange a pickup?

Yes, when dispatch is connected. Arranging a pickup and notifying the driver or customer is the kind of action Bud is for, not just answering “is it packed?”