Blue Dart Shipping Connector for ERPNext

ECOSIRE builds a proper Frappe app — a versioned module with its own DocTypes, not a pile of loose server scripts — that lives inside your ERPNext instance. A Blue Dart Settings single DocType holds your license key, login ID, API area/customer codes, and origin details, with credentials stored encrypted via Frappe's password fieldtype and separate sandbox/production endpoints. hooks.py doc events hang the integration off the documents your team already uses: on a Delivery Note you get a "Generate Blue Dart Waybill" action that calls Blue Dart's WayBill API, writes back the AWB number and token, and renders a Print Format label sized for your thermal printer. A Blue Dart Shipment DocType (or extended Shipment) captures product code (Apex/Dart Apex/Ground), COD amount, declared value, weight, and dimensions, all validated before the API call so a bad payload never reaches Blue Dart.

Serviceability is wired in where decisions get made. A whitelisted method (@frappe.whitelist()) backs a client script on the Delivery Note and Sales Order so a user can check the destination pincode's serviceability and transit time (TAT) against Blue Dart's Master API before committing to the express service — and optionally block or warn on non-serviceable pincodes. COD and topay flows are handled explicitly: COD collection amount is pulled from the linked invoice, passed on the waybill, and stored for later reconciliation; topay consignments set the correct payment flag so freight isn't billed to you by mistake. Pickup registration is a first-class action too — raise a Blue Dart pickup request for a date/time window straight from ERPNext and store the returned pickup token against the shipment.

Everything runs through the Frappe REST API and whitelisted methods with proper role-based permissions, so only a Shipping Manager role profile can generate waybills or trigger pickups, and a scheduler event (Frappe's scheduler_events, hourly/daily) polls Blue Dart tracking for in-transit AWBs and posts status updates back onto the shipment timeline. Errors, raw request/response payloads, and rate-limit handling are logged to a dedicated log DocType so failed calls are diagnosable, not silent.

Because this is build-to-order, nothing is a black box. After a short scoping call we confirm exactly which Blue Dart products, payment modes, and workflows you use, then build and test the app against your Frappe/ERPNext v15 or v16 instance on a staging bench first. Typical delivery is 2–4 weeks from confirmed scope. You receive the installable source, UAT sign-off on staging, install and configuration on your production bench, documentation, a training session, and a post-go-live support window — plus the git repository so the code is yours to own and extend.