DPD Shipping Connector for ERPNext

Key Features

`DPD Settings` single DocType holding API credentials, sandbox/production toggle, default service, and per-company depot binding — no hardcoded keys in server scripts

Token/depot authentication against the DPD API with credential refresh handled server-side and never exposed to the browser

Live parcel rating against your negotiated DPD tariff, called from a whitelisted method and surfaced on the `Delivery Note` before dispatch

Label generation in both PDF (A4 and A6) and raw ZPL, attached to the `DPD Shipment` as Frappe File records for thermal or laser printing

DPD Predict integration: time-slot / delivery-window selection and end-customer notification triggers written back onto the shipment

Pickup-point (parcel shop / locker) lookup and selection via a client-script picker on the Delivery Note form

`Delivery Note` `on_submit` hook that auto-creates the `DPD Shipment` and requests the label without manual steps

Scheduler event (`scheduler_events` cron) that polls DPD tracking and records status transitions with timestamps on each shipment

Whitelisted `@frappe.whitelist()` methods for rate, buy-label, void-label, and track — all callable over the standard Frappe REST API

Multi-market support: national and cross-border DPD services with per-country depot mapping in a `DPD Depot` DocType

Dedicated DPD role profile and permission rules so only authorized dispatch users can buy or void labels

Structured error handling and Frappe error logging on every API call, with failed shipments flagged for retry rather than silently lost

Custom fields added cleanly via fixtures/`custom_field` so upgrades to your ERPNext site don't clobber them

Idempotent label purchase guard to prevent duplicate parcels/charges when a Delivery Note is resubmitted

Built and tested for Frappe/ERPNext v15 and v16 benches

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your ERPNext.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

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 2–4 weeks from confirmed scope, and you get the git repository, documentation, a training session, and a post-go-live support window.

What you get

Installable Frappe app source code built for your ERPNext version (v15 or v16), pinned to a tagged release

Installation and configuration on your bench, including DPD Settings, depot mapping, and role-profile setup

Technical documentation: DocType schema, hooks, whitelisted endpoints, scheduler jobs, and environment variables

End-user guide plus a live training session for your dispatch and warehouse team

UAT on a staging/staging-bench with sample rating, label, and tracking scenarios before production go-live

Production install with a documented rollback plan (app uninstall + custom-field revert)

Post-go-live support window for bug fixes and configuration adjustments

Handover of the private git repository with full commit history and a tagged build

Who this is for

EU e-commerce operations lead

Runs a DPD-shipping storefront on ERPNext and needs warehouse staff to rate, label, and track parcels inside the Delivery Note instead of re-keying every order into the DPD portal.

ERPNext warehouse / dispatch team

Packs and ships high volume daily; needs one-click label printing (A6 thermal / ZPL), Predict time-slots, and pickup-point selection without leaving the ERPNext form.

Cross-border DPD merchant

Ships across multiple European markets and needs national and cross-border DPD services, per-country depot mapping, and consistent tracking status sync back into ERPNext.

ERPNext system administrator / integrator

Owns the bench and cares about a clean Frappe app with proper DocTypes, hooks, permissions, and fixtures that survives v15→v16 upgrades and hands over as a maintainable git repo.

How DPD Shipping Connector for ERPNext Compares

Criterion	ECOSIRE	Custom Build	Competitor
DPD rating, labels & tracking	Built end-to-end for DPD across EU markets	Depends entirely on your developer	Often single-market or partial
Fit to your DPD contract	Scoped to your tariff, services & depots	Possible but you specify everything	Generic defaults, limited config
ERPNext version support	Built & tested for your v15/v16 bench	Whatever your dev targets	May lag core releases
Predict & pickup-points	Time-slot + parcel-shop workflows included	Extra scope to build	Rarely included
Architecture quality	Proper app: DocTypes, hooks, permissions, REST	Varies with developer discipline	Often server-script bolt-ons
Delivery model	Build-to-order, 2–4 weeks, installed for you	Hire, manage, and wait	Instant but as-is
Source & handover	Full source + git repo + tagged release	You own it if built in-house	Usually closed / licensed
Support & updates	Post-go-live window + ongoing option	You maintain it	Vendor-dependent, tier-gated

Frequently Asked Questions about DPD Shipping Connector for ERPNext

Is this an existing app I can download and install today?

No. This is a build-to-order integration. ECOSIRE builds the DPD Shipping Connector against your exact DPD contract, ERPNext version, and workflow, then installs and supports it. There is no instant download — you request a quotation and we scope it with you first.

How long does delivery take?

Typical delivery is 2–4 weeks from confirmed scope. The timeline starts once we've agreed the requirements on the scoping call (DPD service types, Predict vs. classic, label hardware, ERPNext version) and confirmed the build. Complex cross-border or multi-depot setups sit at the longer end of that range.

Which ERPNext versions are supported?

We build and test for Frappe/ERPNext v15 and v16. We confirm your exact bench version on the scoping call and pin the app to it. If you later upgrade, we can rebuild against the new version as part of a support engagement.

What about ongoing support and updates?

Every build includes a post-go-live support window for bug fixes and configuration adjustments. Beyond that, we offer ongoing support and update engagements — including rebuilding against new ERPNext releases or DPD API changes — quoted separately based on your needs.

Do I need a DPD business account and API access?

Yes. You provide your DPD business contract and API credentials (depot, token/keys, sandbox and production). We configure them in the DPD Settings DocType. Rating uses your negotiated tariff, so pricing reflects your own DPD agreement.

How does it fit into the ERPNext dispatch flow?

It links to the standard Delivery Note and Shipment. Staff rate and buy a DPD label directly from the form (or automatically on submit via a hook), print A4/A6/ZPL, pick a Predict time-slot or pickup point, and tracking status syncs back automatically via a Frappe scheduler job.

Do we get the source code?

Yes. You receive the full installable Frappe app source and the private git repository with commit history and a tagged release, so you're never locked in. Everything is exposed over the standard Frappe REST API and whitelisted methods for your own integrations.