DPD UK ↔ Sage 200 Integration
DPD UKCourierDPD UK collection booking, labels and tracking integration — Sage 200 despatch triggers DPD collection, pack-station prints labels, tracking writes back to the despatch note.
DPD UK is the UKs largest multi-parcel network with contract collection rates and a suite of value-added services. For distributors and e-commerce already using Sage 200, the pain is in getting Sage 200 despatch data into DPDs consignment booking system and bringing tracking numbers back into Sage so 'order despatched' in Sage actually means 'carrier has it'. We build that loop — Sage 200 sales orders become DPD consignments at despatch, service codes and rates are mapped from Sage delivery methods, and tracking events push back into the despatch record for shipping confirmation. The integration is bespoke against DPDs UK API, not through an intermediary, to get the best rates and control over collection timing and service selection.
Data Flows
- 1
Despatch → consignment
On despatch-complete in Sage 200, DPD UK consignment API is called with parcel count, weight/dimensions (from a packaging rules table if missing), delivery address and recipient contact pulled from the despatch. Carrier service comes from Sage delivery method mapping — we support next-day, timed, 2-day and economy on the same integration, with surge rate overrides for special zones.
- 2
Collection booking
DPD books the collection for the next available time slot — we map the 'despatch window' (e.g. day-only, after 2pm) from Sage users into DPD scheduling API. If the despatch is after cut-off, we auto-roll to next-day collection unless override allowed in Sage.
- 3
Labels & manifest
The consignment API returns label PDF/ZPL for the pack station, and the consignment number links back to the Sage despatch record the moment it's created — before the truck arrives, so despatch confirmation emails go out with real tracking numbers. End-of-day manifests close in DPD; if a consignment fails to manifest, a queue entry with DPD error code surfaces for manual fix.
- 4
Tracking → Sage
Delivery status events (in transit, out for delivery, delivered, failed) push back into Sage — either onto the despatch record or a tracking table per despatch line. Failed attempts and 'failed' statuses trigger an alert in Sage (email or dashboard). We also capture DPD exceptions (e.g. 'address not found', 'no one at address') into a rejected-consignment queue with DPD incident code.
- 5
Exceptions
Failed bookings (size too big, address validation, service unavailable) raise a queue entry — user fixes in Sage (correct weight, revalidate address) or DPD (service override), consignment retries. No silent drops. If the retry limit hits, the despatch is marked 'manual review needed' in Sage to avoid double-book attempts.
Where These Integrations Go Wrong
The failure modes we design around — most DPD UK ↔ Sage projects hit at least two of these.
Sage lacks parcel weights/dimensions
Most Sage 200 installs store stock items without weight/dim fields. We default from a packaging rules table (carton type per order value/line count) and let the pack station correct it — rather than blocking on missing data. If the table is empty, we set default 1kg / 30x30x30cm for lines with no rule.
Cut-off time surprise
DPD's collection cut-off varies by service and depot. We enforce a configurable cut-off window (e.g. 4pm) based on the service being booked — if the despatch is after cut-off, the consignment rolls to next-day and Sage shows the 'cut-off exceeded' flag on the despatch note.
Service-code drift
DPD updates service codes and product levels constantly (new timed services, price bands). We keep the Sage delivery-method ↔ DPD service-code mapping as editable data (not baked into code) — if you sell 'next-day' in Sage, we map to 'DPD Next-Day' service code, but new service-code updates require data migration, not code change.
Northern Ireland & customs
NI shipments need customs data post-Windsor Framework. If you ship NI/EU from GB, line-level commodity codes and values have to flow from Sage stock items — that means the customs data model has to be right in Sage first. We block on missing customs codes unless you have an override queue.
What's Included
- Despatch-triggered DPD UK consignment booking with service-code mapping
- Label printing at pack bench (PDF or ZPL direct to carrier printers)
- Collection booking with cut-off handling and next-day rollover
- Tracking writeback into Sage despatch records
- Failed-booking queue with validation errors surfaced for fixing
- Test-company UAT against your live DPD UK account
- Packaging rules table for default weight/dimension fallback
- Customs data validation for NI/GB-EU cross-border shipments
Who It's For
Businesses shipping UK parcels on DPD contracts where a delivery-management platform would add unnecessary per-parcel fees. Good for medium-volume shippers who want control over DPD service selection, packaging rules and despatch timing, but don't need multi-carrier rate-shopping — that's what the Metapack integration is for. Works whether Sage 200 is on-prem or hosted, provided we can reach the DPD API and your Sage database.
FAQ
Does DPD offer B2B or trade pricing in the API?
Yes — DPD's UK API surfaces trade/contract pricing for existing accounts. We pull your rate account level via a negotiated partner identifier (which you provide). If you want to sell 'DPD Next-Day' at a customer discount, the price mapping lives in Sage on your delivery-method table — we don't hardcode rates.
Can customers pick DPD services themselves (e.g. timed delivery)?
We can expose DPD's service options in Sage — timed-by-10, by-12, Saturday, named-day. A despatch staff can override the Sage default mapping, with the cost difference shown before confirm. This is useful for B2B customers who control service selection.
What about customer collections (returns)?
Return consignments can be booked the same way — a returns authorisation in Sage creates a reverse consignment with a pre-addressed label emailed to the customer. The returns flow in Sage 200 handles the credit side. DPD's return network is integrated — we use the same API for reverse collections.
Scope Your DPD UK Build
Fixed quote once we know your Sage version, the flows you need and the volumes.