Ops and logistics managers running ERPNext usually know their freight spend is leaking, but they cannot prove where. Native ERPNext gives you Delivery Note, Shipment, and Pick List DocTypes, plus whatever your Parcel Service / carrier connectors write back, but there is no consolidated view of cost-per-shipment, on-time-in-full (OTIF), SLA breaches, or which carrier is quietly eroding margin on a given lane. The stock reports stop at document-level lists and a couple of stock analytics; the moment you ask "what did carrier X cost me per kg on the Karachi-Dubai lane last quarter, and how often did they miss the promised date?" you are exporting to spreadsheets and rebuilding the answer by hand every month.

This build-to-order product is a proper Frappe app (its own module, installed via bench get-app and bench install-app) that ECOSIRE builds against your actual ERPNext instance. We add analytics DocTypes — a Carrier Scorecard and Shipment Cost Fact (or a Query/Script Report layer, depending on your data volume) — and populate them from your existing Delivery Notes, Shipments, and carrier connector payloads. Server-side hooks.py doc events (on_submit, on_update_after_submit) capture ship date, promised date, delivered date, billed freight, and zone/lane keys as documents move; scheduler events (cron/daily handlers registered in scheduler_events) roll facts up into carrier-level and lane-level aggregates so dashboards stay fast without recomputing on every page load. Where a carrier exposes tracking, whitelisted methods (@frappe.whitelist()) and the Frappe REST API pull delivery confirmations to compute true OTIF instead of assumed on-time.

On top of that data layer we build the dashboards you actually asked for: cost-per-shipment and spend trend charts, OTIF tracking, a carrier scorecard with SLA-breach counts, zone and lane cost analysis, and returns / RTO rate analytics — rendered as Frappe Dashboard Charts, Number Cards, and drill-down Query Reports so a manager can go from a KPI tile straight to the underlying shipments. Client scripts add contextual actions and filters on the Shipment/Delivery Note forms where useful. Everything respects ERPNext permissions: we ship role profiles and DocType permission rules so a regional ops lead sees only their own company/warehouse scope, and finance sees spend without edit rights on operational records. It is built for and tested on Frappe/ERPNext v15 and the v16 line.

Because this is build-to-order, nothing ships until we have agreed scope. It starts with a short scoping call to confirm your carriers, connectors, DocTypes, and the exact KPIs and breakdowns you need. We then build on a staging copy of your instance, run UAT against your real data, and only after sign-off do we install to production with a documented rollback plan. Typical delivery is one working week from confirmed scope, and you receive the full source code and git repository so you are never locked in.