Interlink Express / DPD Local Integration
Interlink Express (DPD Local)CourierOne-hour Predict window, next-day UK parcel delivery with full tracking integration — the loop between your warehouse and every carrier Interlink Express fronts, now branded DPD Local.
Interlink Express (now DPD Local) sits between your ERP and UK parcel delivery — one API for one-hour Predict window slots, next-day parcel booking, labels and tracking. The awkward part is keeping Sage 200 in sync with the rebranded service: queries still use the old Interlink Express brand, carrier service maps need both names, and getting tracking numbers back onto the despatch so 'order despatched' in Sage actually means 'DPD Local has it'. We build that loop — Sage 200 sales orders become Interlink Express (DPD Local) consignments at despatch time, service selection honours Sage's delivery methods (Predict vs next-day), and tracking + confirmation flows back so SOP despatch notes stay the single source of truth.
Data Flows
- 1
SOP → consignment
Orders released for despatch in Sage 200 create Interlink Express (DPD Local) consignments within the one-hour Predict window: delivery address, parcel count, weight and dims pulled from SOP + stock item data. Service is chosen from Sage delivery method via a mapping table — no re-keying in Interlink Express/DPD Local Manager.
- 2
Labels & manifest
Interlink Express returns the carrier label PDF and consignment reference at pack-station time; end-of-day manifests are generated inside DPD Local as normal. Sage never holds label data — it holds the consignment reference and carrier/service used, regardless of the Interlink Express brand.
- 3
Tracking → Sage
Tracking number + carrier ID write back onto the despatch note (or a custom tracking table per despatch line), so despatch confirmation emails from your e-commerce store or CRM carry real DPD Local links. The tracking events are labelled under the original Interlink Express queries for consistency.
- 4
Exceptions
Failed bookings (address rejection, service unavailable, weight mismatch) raise a queue entry — user fixes in Sage or Interlink Express, consignment retries. No silent drops. Both Interlink Express and DPD Local branding tracked for customer support.
Where These Integrations Go Wrong
The failure modes we design around — most Interlink Express (DPD Local) ↔ Sage projects hit at least two of these.
Book after pick, not after save
Booking consignments on order save produces cancelled consignments every time an order is edited. The trigger should be despatch-complete (or a packing confirmation), not SOP creation — especially with the Predict window timing.
Weights and dims are rarely in Sage
Interlink Express/DPD Local wants parcel weight/dimensions; most Sage 200 installs have them blank. 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.
Brand mapping in queries
Queries still use the Interlink Express brand, but the service is now DPD Local. The Sage side needs to handle both names in error messages and customer-facing content to avoid confusion.
Predict window timing
One-hour Predict slots require tight timing between Sage despatch completion and carrier booking. If the despatch trigger happens near slot boundaries, bookings may need to rollover to next-day, causing customer service queries around the Interlink Express/DPD Local transition.
What's Included
- SOP despatch → Interlink Express (DPD Local) consignment booking with one-hour Predict window
- Delivery-method ↔ Interlink Express/DPD Local service mapping table, editable without code
- Label printing at pack bench (PDF or ZPL direct to carrier printers)
- Tracking number + carrier writeback to Sage despatch records with brand preservation
- Exception queue with retry for failed bookings (Interlink Express vs DPD Local handling)
- End-of-day manifest with cut-off handling and Predict slot rollover
Who It's For
Distributors and e-commerce businesses using Interlink Express Predict window services and evaluating DPD Local as their primary courier — typically high-velocity parcels needing one-hour Predict slots for next-day UK delivery. Those migrating from Interlink Express brand but still querying under the old name. Works whether Sage 200 is on-prem or hosted, provided we can reach the Interlink Express/DPD Local API.
FAQ
Does this replace Interlink Express's Sage connector?
Interlink Express doesn't ship a maintained Sage 200 connector — their integrations target SAP/Dynamics/NetSuite or plain CSV import. This is the bespoke layer most Interlink Express + Sage 200 shops end up building anyway, now extended for DPD Local.
Can Predict window slots be chosen by cheapest quote?
Yes — Interlink Express/DPD Local's shipping/quote API can drive auto-selection (cheapest service meeting the Predict window). The Sage delivery method then acts as the service-level constraint (one-hour Predict vs next-day), and Interlink Express/DPD Local picks the cheapest carrier inside that rule.
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, with Interlink Express/DPD Local branding preserved for customer awareness.
Scope Your Interlink Express (DPD Local) Build
Fixed quote once we know your Sage version, the flows you need and the volumes.