Mid-market retailers running ERPNext outgrow its native shipping quickly. ERPNext core gives you a Shipment DocType, a handful of Shipping Rule records, and manual tracking-number fields — but it has no concept of rule-based carrier selection, no live status ingestion, and no structured way to work a non-delivery. When you ship across five or ten couriers, teams end up allocating orders in spreadsheets, pasting tracking IDs into carrier portals one at a time, and chasing failed deliveries over email. The cost is real: higher RTO rates, WISMO tickets, and working capital stuck in packages that will never be delivered. ClickPost solves the aggregation and intelligence layer, but nothing connects it cleanly into ERPNext's order-to-cash flow.

ECOSIRE builds that connection as a proper Frappe app — a dedicated clickpost_connector module with its own DocTypes, not a pile of custom fields bolted onto stock forms. We add a ClickPost Settings single DocType holding your API credentials (stored encrypted via Frappe's password fieldtype), environment toggle, and default account mappings. Courier allocation is driven by a Courier Allocation Rule DocType — priority-ordered rules matching on pincode/zone, weight, payment mode (COD vs prepaid), SLA, and serviceability, resolved server-side so the cheapest serviceable carrier wins automatically. Outbound calls to ClickPost's API run through whitelisted server methods and Frappe's enqueue background jobs so the UI never blocks on a carrier timeout, with ret/backoff on transient failures.

On the ERPNext side, hooks.py doc events fire the integration at the right moments: on Delivery Note submit we register the shipment, request an AWB, and pull back a Shipment Package record with the label PDF and manifest attached to the document. A scheduled event (scheduler_events) polls ClickPost's tracking endpoint on a cadence you choose, writing normalized status transitions into a Shipment Tracking Event child table and surfacing the predicted ETA on the Sales Order and Delivery Note. When ClickPost reports an NDR (non-delivery report) or NPR (non-pickup report), a webhook received by a whitelisted endpoint opens an NDR Resolution DocType — a workflow with states like Open, Reattempt Requested, Address Updated, RTO Initiated, and Closed — assigned to your ops role profile so failed deliveries become a tracked queue instead of lost email. Client scripts add action buttons (Generate Label, Reprint Manifest, Track Now, Raise Reattempt) directly on the ERPNext forms your team already uses.

Because this is build-to-order, nothing ships until we agree on scope. We start with a short scoping call to confirm your ClickPost account setup, carrier mix, allocation logic, and which ERPNext documents drive the flow. We then build against your Frappe/ERPNext v15 or v16 instance, deliver on a staging site for UAT, and only promote to production once you sign off — with a rollback plan and the full git repository handed to you. Typical delivery is 2–4 weeks from confirmed scope, followed by a post-go-live support window.