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.
INT · DPDonDraft
Integration
DPD ↔ Dispatch
one process, two systems.
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.
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 are consequences of that state — work Bud can also initiate when the system is connected.
We scope services, accounts, and label rules against your DPD setup. This page is the SEO and commercial home for that conversation, not a claim of an official DPD marketplace badge.
Questions about this system
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?
When dispatch is connected, arranging pickup and notifying the driver or customer is exactly the kind of action Bud is for — not just answering “is it packed?”
We build systems that power growth.
AI agents, integrations and operational software—built around your business.