If you sell across marketplaces and your own storefront out of ERPNext, the fulfillment desk is where the day gets lost. ERPNext core can raise a Delivery Note and record a tracking number in a text field, but it has no native concept of carrier rate-shopping, AWB generation, label/manifest printing, or the reverse-logistics reality of South-Asian e-commerce — non-delivery reports (NDR) and return-to-origin (RTO). Teams paper over this with the eShipz web dashboard in a second browser tab, re-keying addresses and order lines by hand, exporting CSVs, and reconciling shipment status against ERPNext manually. That double-entry is slow, error-prone, and it means the ERP never holds the true state of a shipment.

We build a proper Frappe app — its own installable module with a clean hooks.py, not a pile of ad-hoc Server Scripts — that makes eShipz a first-class part of the ERPNext order-to-delivery flow. The app ships new DocTypes such as eShipz Settings (a Single DocType holding your API credentials, default warehouse pickup addresses, and courier preference rules) and eShipz Shipment (a child of the Delivery Note that stores the AWB number, courier partner, label PDF, and a live status timeline). Doc events registered in hooks.py — on_submit of the Delivery Note, validate for address completeness — call whitelisted server-side methods that hit the eShipz REST API to fetch live rates, book the shipment against your chosen or rule-selected courier, and pull back the AWB and label. Credentials never touch the browser; every outbound call runs server-side under a dedicated eShipz Manager role profile so warehouse staff get exactly the buttons they need and nothing more.

Around that core we build the operational surface your team actually works from. A Client Script adds a "Book Shipment" and "Print Label" action to the Delivery Note; a bulk manifest tool lets a packer select many delivery notes and generate a single carrier manifest and a batched label PDF for the day's dispatch. Real-time tracking is handled by a Scheduler Event (a scheduler_events cron entry) that polls eShipz webhooks/status for in-transit AWBs, writes each status change onto the shipment timeline, and can drive a branded, customer-facing tracking page rendered by a Frappe web view on your own domain. The NDR & RTO management dashboard is a Frappe Workspace with number cards and a list view of failed-delivery and return shipments, so your team can re-attempt, update the delivery instruction back to the courier, or flag an RTO — all as auditable actions inside ERPNext.

Because this is build-to-order, nothing is guessed. We start from a short scoping call to confirm your courier mix, marketplace channels, warehouse/pickup structure, and which order documents trigger a booking. We then build against your ERPNext version (Frappe/ERPNext v15 or v16), test the full flow on a staging bench with your real courier accounts in eShipz sandbox where available, run UAT with your fulfillment team, and only then install on production behind a rollback plan. Typical delivery is one working week from confirmed scope, and you receive the full git repository and source so the app is yours to keep, audit, and extend.