ERPNext DHL Express Connector

We build a proper Frappe app — its own module, DocTypes, and hooks.py — that makes DHL Express a native shipping option inside ERPNext. Rate requests call the DHL Express /rates endpoint from a whitelisted server method and return time-definite service options with landed cost, so your team quotes with real numbers instead of estimates. From a submitted Delivery Note, a hooks.py doc event (or a one-click client script button) posts to the DHL /shipments endpoint, receives the tracking number and a base64 label, and stores the label PDF as a File attached to the shipment. A dedicated DHL Shipment DocType records the AWB, piece IDs, declared value, Incoterm, and raw API request/response for audit and re-print.

Customs is handled where it belongs — in the payload. The app maps your ERPNext Item HS codes, country of origin, and declared values into DHL's export-declaration and paperless-trade structure, and generates the commercial/proforma invoice as a Frappe Print Format so the documents that cross the border match the documents in your system. A scheduler_events hook polls the DHL /tracking endpoint (or ingests webhook callbacks where enabled) and writes status milestones back onto the shipment and linked Delivery Note, with optional Notifications to your ops team. Pickup scheduling calls the DHL /pickups endpoint so a courier is booked in the same flow that creates the label — no separate portal visit.

Everything is permission-aware and version-safe: DHL API credentials live in an encrypted single DHL Settings DocType, actions are gated by a Role Profile you approve, and the app is built and tested against ERPNext v15/v16 so it survives bench update. Because it is a real app in its own git repo — not fragile customizations glued onto stock DocTypes — you own the source and can extend it.

This is build-to-order: nothing is a pre-packaged instant download. We start with a short scoping call to confirm your DHL account setup (export account, Incoterms, service types, origins/destinations), then build against your ERPNext instance. Typical delivery is 2-4 weeks from confirmed scope. You get the work validated on a staging copy through UAT before we touch production, plus a rollback plan, documentation, a training session, and a defined post-go-live support window.