Shiprocket Shipping Connector for ERPNext

Key Features

Dedicated Frappe app with its own module, DocTypes and `hooks.py` — no monkey-patching of ERPNext core forms

Token-authenticated Shiprocket API integration stored in a `Shiprocket Settings` DocType (credentials, pickup locations, default weight/dimensions, COD flags)

Serviceability check against Shiprocket's API by delivery pincode, weight and payment mode before any label is generated

Courier recommendation engine ranking options by estimated delivery days, freight charge and courier rating, surfaced on the Delivery Note

One-click AWB assignment via a `frappe.whitelist()` server method tied to the chosen courier

Automatic shipping label and manifest retrieval, attached to the shipment as printable File records

`hooks.py` doc events on Delivery Note submit to trigger order creation and AWB assignment without manual re-keying

Client Scripts adding the courier picker, rate preview and shipment action buttons directly on the ERPNext form

Scheduler event that polls Shiprocket tracking on a configurable interval and writes status transitions back to the shipment record

Whitelisted webhook endpoint for near-real-time delivery, RTO and NDR status updates from Shiprocket

COD remittance reconciliation matching Shiprocket payout data against the originating Sales Order / Delivery Note, flagging shortfalls and pending payouts

NDR management workflow with reattempt, reschedule and return-to-origin actions that call back to Shiprocket

Role profiles and DocType permissions scoping courier selection, COD reconciliation and settings to the correct users

Server-side validation of weight, dimensions and serviceable pincode before dispatch, with error logging via Frappe's Error Log

Built and tested for Frappe/ERPNext v15 and v16

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 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 2-4 weeks 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.

What you get

Installable source code for your ERPNext version (v15 or v16) as a proper Frappe app

Installation and configuration on your ERPNext instance, including Shiprocket credentials and pickup locations

Technical documentation: DocType reference, hooks.py doc events, whitelisted methods, scheduler and webhook setup

End-user guide plus a live training session for your operations and shipping team

UAT on a staging site with your real orders, and a documented rollback plan before go-live

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

Git repository handover with full commit history — you own the code

Configuration handbook for adding pickup locations, courier rules and COD reconciliation settings

Who this is for

D2C brand operations lead

Runs daily dispatch for an Indian direct-to-consumer brand on ERPNext and wants AWB assignment, labels and tracking to happen inside ERPNext instead of copy-pasting into the Shiprocket panel.

E-commerce finance / COD reconciliation owner

Responsible for matching Shiprocket COD remittances against orders. Needs an automated reconciliation view that flags shortfalls and pending payouts against the originating Sales Order or Delivery Note.

Customer-support / NDR manager

Handles failed and returned deliveries. Wants NDR cases to arrive as actionable ERPNext records with reattempt, reschedule and return actions rather than scattered emails.

ERPNext system administrator / implementation partner

Owns the ERPNext instance and needs a maintainable Frappe app — clean DocTypes, hooks, role profiles and a git repo — that survives version upgrades to v15/v16 rather than brittle client-side hacks.

How Shiprocket Shipping Connector for ERPNext Compares

Criterion	ECOSIRE	Custom Build	Competitor	ERPNext Native
Shiprocket serviceability & courier recommendation	Live serviceability check with ranked courier options on the form	Possible, but you design and maintain the ranking logic yourself	Basic rate lookup, ranking often generic or limited	Not available — no Shiprocket awareness at all
AWB, label & manifest inside ERPNext	One-click AWB, printable label and manifest attached to the shipment	Buildable from scratch against Shiprocket's API	Usually included, but tied to the vendor's shipment model	Delivery Note exists, but no AWB, label or manifest
COD remittance reconciliation	Automated matching to Sales Order / Delivery Note with shortfall flags	Custom effort; reconciliation logic is non-trivial to get right	Rarely covered; often a manual spreadsheet step	Manual — no COD reconciliation feature
NDR management	Webhook-driven NDR records with reattempt/reschedule/return actions	You build the webhook handler and workflow yourself	Varies; frequently just a status field, no workflow	Not available
Fit to your existing workflow	Built around your Delivery Note, fields and COD/prepaid split	Fully bespoke but you carry all specification risk	Take-it-or-leave-it; you adapt to the app's assumptions	Generic core behaviour only
Upgrade safety (v15/v16)	Standard Frappe app — module, DocTypes, hooks; tested on v15/v16	Depends entirely on your build discipline	Depends on vendor's upgrade cadence and support	Core upgrades cleanly, but adds no shipping features
Ownership & support	Full source, git repo handover, training and support window	You own it, but also own all maintenance from day one	Licensed; source usually closed, support per vendor terms	Community support only; no shipping integration to support
Time to working shipping flow	2-4 weeks from confirmed scope, UAT on staging before go-live	Often longer; timeline depends on in-house capacity	Fast to install, but customisation and gaps take time	Immediate, but shipping automation simply isn't there

Frequently Asked Questions about Shiprocket Shipping Connector for ERPNext

How long does delivery take?

This is a build-to-order product. Typical delivery is 2-4 weeks from confirmed scope, depending on your ERPNext version, Shiprocket account configuration and any custom fields or workflows we need to accommodate. We lock the timeline during the scoping call before any work begins.

Is this an instant download from a marketplace?

No. It is not an off-the-shelf Frappe Cloud Marketplace download. ECOSIRE builds the app for your specific ERPNext instance and Shiprocket setup, installs it, runs UAT on staging, and supports it after go-live. You receive the source and a git repository at handover.

Which ERPNext / Frappe versions are supported?

We build and test for Frappe/ERPNext v15 and v16. If you are on an older version, tell us during scoping — we will confirm feasibility and whether an upgrade is recommended before committing to a timeline.

How do updates and support work after go-live?

You get a post-go-live support window for defect fixes and questions. Because you own the source and git repo, your own team or ECOSIRE can extend it later. Shiprocket API changes and ERPNext version upgrades can be handled under a separate maintenance arrangement, quoted based on scope.

Do you handle COD remittance reconciliation and NDR cases?

Yes. The connector ingests Shiprocket COD remittance data and matches it against the originating Sales Order or Delivery Note, flagging shortfalls and pending payouts. NDR (non-delivery report) events arrive via webhook as actionable records with reattempt, reschedule and return-to-origin actions.

Will this break when I upgrade ERPNext?

It is built as a standard Frappe app with its own module, DocTypes and hooks rather than direct edits to core files, which is the upgrade-safe pattern. We test against v15/v16, and version upgrades can be validated on staging as part of a maintenance engagement.

Can you adapt it to our existing Delivery Note customisations?

Yes. We review your current Delivery Note, Shipment and any custom fields during scoping and build the courier picker, AWB actions and reconciliation to fit your existing workflow rather than forcing a rewrite of how your team already works.