EU e-commerce sellers running ERPNext hit a wall the moment DPD becomes their carrier. ERPNext core has no concept of a DPD depot, no live rating against your negotiated tariff, no way to mint a compliant DPD label, and no Predict time-slot or pickup-point workflow. Warehouse staff end up re-keying every order into the DPD web portal, copying tracking numbers back by hand, and reconciling shipping costs after the fact. That double entry is slow, error-prone, and it silently breaks the promised-delivery experience that DPD Predict is supposed to deliver.

This connector closes that gap as a proper Frappe app — its own module, DocTypes, and hooks.py doc events — rather than a brittle set of pasted server scripts. We model DPD configuration as first-class records: a DPD Settings single DocType holds API credentials, environment (sandbox/production), and default service, while a DPD Depot child/linked DocType captures your depot and pickup-point mappings. A DPD Shipment DocType (linked from the standard Delivery Note and Shipment) stores the parcel payload, returned label, tracking reference, and status history, so every dispatch is auditable inside ERPNext.

Technically, rating and label creation run through whitelisted server methods (@frappe.whitelist()) that call the DPD API with token/depot authentication, then persist the returned label as a File attachment in both PDF (A4/A6) and ZPL for direct thermal printing. A Delivery Note on_submit hook can auto-generate the shipment and label; a client script adds a "Rate & Buy DPD Label" button and a Predict time-slot / pickup-point picker to the form. Tracking status is kept fresh by a scheduler_events job (Frappe's cron) that polls DPD and writes status transitions plus notifications back onto the shipment — no manual lookups. Everything respects Frappe's permission model via a dedicated role profile, and all endpoints are exposed over the standard Frappe REST API so your storefront or middleware can drive them too.

Because this is build-to-order, nothing ships as a blind download. ECOSIRE starts with a short scoping call to confirm your DPD contract type (national vs. cross-border, Predict vs. classic), your ERPNext version (v15 or v16), your label hardware (A6 thermal vs. A4), and any custom delivery workflow. We build against your exact requirements, deliver installable source for your version, run UAT on a staging bench, then install on production with a rollback plan. Typical delivery is one working week from confirmed scope, and you get the git repository, documentation, a training session, and a post-go-live support window.