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 integration for warehouse 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 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.
DPD and your ERP or shop
Whatever runs your orders, the pattern is the same. The warehouse owns packed status. DPD gets the consignment from that event. Your ERP or shop gets the tracking number back.
Shopify and other ecommerce shops. The order comes in from the shop and the warehouse picks and packs it. The DPD consignment is created when the parcel is packed, and tracking goes back to the shop order so the customer email is right.
Sage. Sales orders often start in Sage. The warehouse decides when the order is packed, the DPD consignment follows, and the tracking number goes back against the Sage order.
Microsoft Dynamics. Same approach. Dynamics keeps the sales order, the warehouse owns pick and pack, and DPD tracking is written back once the consignment exists.
NetSuite. NetSuite holds the sales order. The DPD consignment is keyed off the warehouse packed event, then tracking is passed back so NetSuite and DPD agree.
Other ERPs, such as Acumatica, Epicor and SAP Business One. We scope against the system you run. The rule does not change: packed status comes from the warehouse, the consignment follows it, and tracking goes back to the order.
None of this is an official DPD app for each ERP. We build the connection from your warehouse state and your own DPD account.
Questions about this system
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?”
We build systems that power growth.
AI agents, integrations and operational software—built around your business.