Delhivery Shipping Connector for ERPNext

We build a proper Frappe app — its own module, not a pile of loose customizations — that makes Delhivery a first-class carrier inside ERPNext. Authentication to the Delhivery One API is handled through a single Delhivery Settings single DocType holding your API token, client warehouse registration, and environment (staging vs production), with secrets stored as password fields, never in plain custom fields. A check_serviceability whitelisted method validates a destination pincode and returns COD/prepaid eligibility and expected TAT before the order is even confirmed. A rate calculator surfaces live freight on the Sales Order and Delivery Note so your team quotes shipping accurately instead of guessing.

Technically, the connector leans on standard Frappe extension points rather than fighting the framework. Doc events registered in hooks.py (for example on_submit of the Delivery Note) trigger waybill generation and push package weight, dimensions, and COD amount to Delhivery, then write the returned AWB back onto the document and generate a printable shipping label PDF. Whitelisted server methods expose serviceability, rating, manifest, and cancel actions to both the desk and the Frappe REST API, so your storefront or OMS can call them over /api/method/.... Client scripts add serviceability and "Get Rate" buttons directly on the form. A scheduler event polls tracking and RTO status on an interval and updates a Delhivery Shipment DocType, while a COD reconciliation routine ingests Delhivery remittance data and matches it against the originating invoice. Role profiles and permission rules keep carrier configuration locked to a Shipping Manager role while dispatch staff only get the actions they need. Everything targets ERPNext and Frappe v15 and v16.

Because this is build-to-order, there is no instant download — and we do not pretend otherwise. After a short scoping call we confirm exactly which flows you need (serviceability gating, surface vs express, multi-warehouse pickup, COD vs prepaid, return orders), agree the spec, and build against it. Typical delivery is 2–4 weeks from confirmed scope. We install and configure on your bench, run UAT on a staging site with a rollback plan, hand over the git repository and technical documentation, train your team, and stand behind it with a post-go-live support window.