ERPNext Shiprocket Connector

ECOSIRE builds a proper Frappe app (erpnext_shiprocket_connector) that closes that gap. We add first-class DocTypes — a Shiprocket Settings single for API credentials and channel mapping, a Shiprocket Shipment linked to the Delivery Note, plus child tables for rate quotes and tracking events — and drive the whole flow through Shiprocket's REST API. A whitelisted method (@frappe.whitelist()) calls Shiprocket's courier/serviceability endpoint to pull live rates across every enabled courier for the order's pickup pincode, weight, and dimensions, then ranks them by cost, rated delivery days, or your own business rule. A hooks.py doc_events handler on Delivery Note on_submit can auto-create the shipment and assign an AWB, while a client script adds a "Compare Rates" and "Generate Label" action right on the Delivery Note toolbar so ops staff never leave ERPNext.

Under the hood the connector authenticates against Shiprocket, caches the token, and handles label/manifest PDF generation, pickup scheduling, and AWB assignment as atomic, idempotent operations that write back onto the linked documents. A Frappe scheduler event polls tracking for in-transit shipments (or consumes Shiprocket webhooks where available) and appends each scan to the tracking child table, updating shipment status. NDR (non-delivery report) and RTO (return-to-origin) events are surfaced as their own records with action fields — reattempt, update address, or accept return — so exceptions are worked inside ERPNext instead of a separate portal. All access is governed by Frappe permissions and a dedicated role profile, so warehouse users, CX agents, and finance each see only what they should. The app targets Frappe/ERPNext v15 and v16.

Because this is build-to-order, nothing ships as a blind marketplace download. We start with a short scoping call to confirm your courier mix, pickup locations, channel/marketplace setup, weight-and-dimension source fields, and NDR/RTO policy, then build against your exact ERPNext version and workflow. Typical delivery is 2 to 4 weeks from confirmed scope. You get the installable source for your version, UAT on a staging bench with a rollback plan, a training session for your ops team, and a post-go-live support window — plus the git repository handover so the code is genuinely yours.