Delhivery Shipping Connector for ERPNext

Key Features

`Delhivery Settings` single DocType storing API token, registered client warehouse, and staging/production toggle with credentials held in Frappe password fields (never plain custom fields)

Delhivery One API authentication and a thin, retry-aware HTTP client wrapper with request/response logging to an Error Log-friendly audit trail

Pincode serviceability check exposed as a whitelisted `check_serviceability` method returning COD/prepaid eligibility, expected TAT, and pickup availability before order confirmation

Live rate calculator that surfaces surface and express freight on the Sales Order and Delivery Note, including COD and fuel surcharge components

Automatic waybill (AWB) generation on Delivery Note `on_submit` via a `hooks.py` doc event, writing the AWB back onto the document

Delhivery-formatted shipping label and manifest PDF generated through Frappe print formats, ready to hand to the pickup executive

COD shipment creation with the collectible amount pushed to Delhivery and stored on a dedicated `Delhivery Shipment` DocType

COD remittance reconciliation routine that ingests Delhivery payout data and matches it against the originating Sales Invoice / Payment Entry

Pickup request scheduling against your registered warehouse, with pickup slot and expected count sent to Delhivery One

RTO (Return-To-Origin) detection and a scheduler event that polls tracking status on an interval and updates shipment state

Whitelisted server methods (serviceability, rate, manifest, cancel, track) callable from the desk and the Frappe REST API for storefront/OMS integration

Client scripts adding `Check Serviceability` and `Get Rate` buttons plus inline validation directly on the ERPNext form

Role profile and permission rules scoping carrier configuration to a Shipping Manager role while dispatch staff get action-only access

Cancel/void shipment handling that respects Delhivery's cancellation window and reverses ERPNext-side status cleanly

Built and tested against Frappe/ERPNext v15 and v16, packaged as a versioned, installable Frappe app on its own module

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

Indian ERPNext merchants and 3PL operators hit a wall the moment fulfilment scales past a handful of orders a day. ERPNext core gives you Sales Orders, Delivery Notes, and a Shipment DocType, but it has no native knowledge of Delhivery — no pincode serviceability check, no live freight quote, no waybill number pulled back onto the delivery, no COD remittance matched against your receivables. Teams end up alt-tabbing into the Delhivery One panel, keying AWB numbers into a spreadsheet, and reconciling cash-on-delivery payouts by hand. Every manual step is a mis-shipped parcel, a serviceability surprise at the doorstep, or a COD amount that never gets tied back to the invoice.

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.

What you get

Installable Frappe app source code for your ERPNext version (v15 or v16), packaged as a proper app on its own module

Installation and configuration on your bench, including Delhivery Settings, warehouse registration, and role setup

Technical documentation: DocType reference, hooks/doc events, whitelisted method signatures, and scheduler jobs

User guide plus a live training session for your dispatch and finance teams

UAT on a staging site with a documented test plan and a rollback plan before production cutover

Post-go-live support window for defect fixes and configuration questions

Git repository handover with full commit history and a tagged release

Deployment notes covering environment variables, Delhivery One credentials handling, and update/upgrade guidance

Who this is for

Indian D2C / e-commerce merchant on ERPNext

Runs order fulfilment out of ERPNext and ships primarily via Delhivery. Needs serviceability gating at checkout/order entry, accurate live shipping rates, and one-click waybill generation so the warehouse stops re-keying AWB numbers into spreadsheets.

3PL / fulfilment operations lead

Manages multi-warehouse pickups and high daily shipment volume. Needs bulk waybill generation, manifested pickup requests against registered warehouses, and RTO/tracking status synced back into ERPNext without leaving the desk.

Finance / accounts manager

Owns COD reconciliation. Needs Delhivery remittance payouts matched automatically against the originating Sales Invoice and Payment Entry, so cash-on-delivery collections stop drifting away from receivables at month end.

ERPNext implementation partner or in-house admin

Maintains the bench and integrations. Wants a clean, versioned Frappe app with documented hooks, whitelisted methods, and permissions — not brittle custom scripts — that upgrades cleanly across v15/v16.

How Delhivery Shipping Connector for ERPNext Compares

Criterion	ECOSIRE	Custom Build	Competitor
Delhivery serviceability & live rates	Pincode check and live surface/express quotes on the Sales Order and Delivery Note	Possible but you build the API client and form logic yourself	Often generic rate lookup, may not gate on serviceability
Waybill / label generation	Auto AWB on Delivery Note submit via hooks.py doc event + print-format label	Hand-wired doc events and print formats per project	Usually supported, formatting varies
COD reconciliation	Remittance matched to Sales Invoice / Payment Entry automatically	Bespoke matching logic, significant effort	Rarely reconciles payouts to invoices
Fit to your fulfilment flow	Built to your confirmed scope: multi-warehouse, COD/prepaid, RTO	Fully bespoke — highest effort and cost on you	Fixed feature set, take it or leave it
Source code & ownership	Full git repo handover, tagged release, no lock-in	You own it but also own all the build risk	Often closed or license-restricted
ERPNext v15/v16 compatibility	Built and tested against your exact bench version	Depends on your team's version discipline	May lag ERPNext releases
Delivery model	Build-to-order, 2–4 weeks from confirmed scope, installed for you	Weeks to months depending on in-house capacity	Instant install but no scoping to your process
Support after go-live	Post-go-live support window + optional maintenance	Self-supported unless separately contracted	Vendor tickets, variable SLA

Frequently Asked Questions about Delhivery Shipping Connector for ERPNext

Is this a ready-to-download app from the Frappe Cloud Marketplace?

No. This is a build-to-order product. ECOSIRE builds the Delhivery connector to your confirmed scope, installs it on your bench, and supports it after go-live. There is no instant download — the value is a connector tailored to your fulfilment flows and warehouse setup, delivered as a proper installable Frappe app.

How long does delivery take?

Typical delivery is 2–4 weeks from confirmed scope. After a short scoping call we agree exactly which flows you need — serviceability gating, live rating, waybill generation, COD reconciliation, pickup scheduling, RTO tracking — and build against that spec. Larger or highly customized scopes can run longer, and we tell you honestly during scoping.

Which ERPNext versions are supported?

We build and test against Frappe/ERPNext v15 and v16. Tell us your exact bench version and hosting (Frappe Cloud, self-hosted, or ECOSIRE-managed) during scoping and we target it precisely, including the update path across minor versions.

How does COD reconciliation actually work?

The connector creates COD shipments with the collectible amount pushed to Delhivery and stored on a `Delhivery Shipment` DocType. A reconciliation routine ingests Delhivery remittance/payout data and matches it against the originating Sales Invoice and Payment Entry in ERPNext, so cash-on-delivery collections are tied back to your receivables instead of tracked in a separate spreadsheet.

Do we get the source code, or are we locked in?

You get the full source. We hand over the git repository with commit history and a tagged release, plus technical documentation. It is a standard Frappe app on its own module — you or any Frappe developer can maintain it. No obfuscation and no lock-in.

What about support and updates after go-live?

Every build includes a post-go-live support window for defect fixes and configuration questions. Because Delhivery One's API and ERPNext both evolve, we can also agree an ongoing maintenance arrangement to keep the connector current across Delhivery API changes and ERPNext v15/v16 upgrades. Scope and terms are set during the engagement.

Can the connector be called from our storefront or OMS, not just the ERPNext desk?

Yes. Serviceability, rating, manifest, cancel, and tracking are exposed as whitelisted server methods reachable over the Frappe REST API (`/api/method/...`), so your website, checkout, or external OMS can trigger them directly while ERPNext remains the system of record.