Indian D2C and e-commerce sellers running ERPNext hit the same wall the moment volume grows: ERPNext core has a clean Delivery Note and a Shipment DocType, but it has no idea which Shiprocket courier will actually service a given pincode, no way to pull a real-time rate card, no AWB, no shipping label, no manifest, and no visibility once a COD parcel leaves the warehouse. Operations teams end up living in two tabs — the ERPNext order and the Shiprocket panel — re-keying addresses, manually reconciling COD remittances against a spreadsheet, and chasing NDR (non-delivery report) cases over email. That copy-paste layer is where errors, RTO losses and unhappy customers come from.

The Shiprocket Shipping Connector closes that gap as a proper Frappe app (its own module, DocTypes, and hooks.py), not a fragile script bolted onto an existing form. We add configuration DocTypes such as Shiprocket Settings (token-authenticated API credentials, pickup locations, default package dimensions and weight, COD toggles) and per-shipment DocTypes that store the AWB, courier, rate, and live tracking status. A serviceability and courier-recommendation engine calls Shiprocket's serviceability API for the delivery pincode, weight and payment mode, then surfaces ranked courier options — by expected delivery days, freight charge and rating — directly on the Delivery Note or a custom Shiprocket Shipment DocType so your team picks with full context instead of guessing.

Technically, the flow is driven by hooks.py doc events and whitelisted server methods. When a Delivery Note is submitted (or a picker clicks "Assign AWB"), a frappe.whitelist() method authenticates to Shiprocket, creates the order, assigns the AWB from the chosen courier, and pulls back the shipping label and manifest as File attachments — printable straight from ERPNext. Client Scripts add the courier-picker and one-click actions to the form; server scripts and controller logic enforce validation (weight, dimensions, serviceable pincode) before anything is sent. A Frappe scheduler event polls tracking on a configurable interval and writes status transitions back, and Shiprocket webhooks land on a whitelisted endpoint so delivery, RTO and NDR updates arrive in near real time. COD orders get a reconciliation workflow: we ingest Shiprocket's remittance data, match it against the originating Sales Order or Delivery Note, and flag shortfalls or pending payouts. NDR cases become actionable records with reattempt / reschedule / return actions that call back to Shiprocket. Role profiles and permissions keep courier selection, COD reconciliation and settings access scoped to the right people, and everything is built for Frappe/ERPNext v15 and v16.

Because this is build-to-order, nothing ships blind. We start with a short scoping call to confirm your exact Shiprocket account setup, order volume, pickup locations, COD vs prepaid split and any custom Delivery Note fields you already use. We then build against your ERPNext version on a staging site, run UAT with your real orders, and hand over the app after you sign off. Typical delivery is one working week from confirmed scope, and you receive the full source, a git repository, documentation, training and a post-go-live support window — you own what we build.