Logistics Analytics & Carrier Scorecard for ERPNext

Key Features

Dedicated Frappe app and module installed via `bench get-app` / `bench install-app`, versioned in its own git repo — not a monkey-patch of ERPNext core

Analytics DocTypes (`Carrier Scorecard`, `Shipment Cost Fact`) that denormalize freight, dates, and lane keys for fast reporting instead of heavy live joins

`hooks.py` doc events (`on_submit`, `on_update_after_submit`) on Delivery Note and Shipment capture ship/promised/delivered dates and billed freight as documents progress

Scheduler events (`scheduler_events` cron/daily handlers) roll shipment facts into carrier- and lane-level aggregates so dashboards load without recomputation

OTIF (on-time-in-full) computation comparing promised vs. actual delivery date and ordered vs. delivered quantity, per shipment and rolled up per carrier

Carrier scorecard with weighted SLA-breach counts, average cost-per-shipment, and on-time percentage — sortable and filterable by period

Cost-per-shipment and freight spend-trend charts as native Frappe Dashboard Charts and Number Cards on a dedicated workspace

Zone and lane cost analysis (origin-destination pairs) with cost-per-kg / cost-per-unit breakdowns via drill-down Query Reports

Returns and RTO (return-to-origin) rate analytics tied back to the originating shipment and carrier

Whitelisted methods (`@frappe.whitelist()`) exposing scorecard and KPI data over the Frappe REST API for embedding in other tools or Power BI

Client scripts adding contextual filters and quick actions on Shipment / Delivery Note forms where they speed up daily ops

Role profiles and DocType permission rules scoping visibility by company/warehouse — regional ops see their lanes, finance sees spend read-only

Configurable carrier-to-connector mapping so multiple parcel/freight connectors feed one unified scorecard

Built and tested for Frappe/ERPNext v15 and v16, upgrade-safe against core changes

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

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 2-4 weeks from confirmed scope, and you receive the full source code and git repository so you are never locked in.

What you get

Installable Frappe app source code targeting your exact ERPNext version (v15 or v16)

Installation and configuration on your staging instance, then production, including carrier/connector mapping

Technical documentation: DocType schemas, hooks, scheduler jobs, whitelisted API endpoints, and permission model

User guide plus a live training session for your ops and finance teams

UAT on a staging copy against your real data, with a documented rollback plan before any production install

Post-go-live support window for defect fixes and configuration adjustments

Full git repository handover so you own and can extend the code

Optional REST/Power BI integration notes for embedding scorecards in external dashboards

Who this is for

Logistics / Ops Manager

Owns freight spend and carrier relationships. Needs one place to see cost-per-shipment, OTIF, and which carrier is missing SLAs on which lane — instead of rebuilding it in spreadsheets every month.

Supply Chain / Fulfillment Director

Runs multi-warehouse or multi-region fulfillment on ERPNext. Wants lane and zone cost analysis plus RTO trends to renegotiate carrier contracts with hard data and scope-limited visibility per region.

Finance / Controller

Needs read-only, auditable freight spend trends tied to shipments and carriers for cost allocation and budgeting, without edit access to operational documents.

ERPNext Administrator / Implementation Lead

Responsible for a clean, upgrade-safe install. Cares that it ships as a proper Frappe app with its own module, hooks, and permission rules — not core patches — and that the git repo is handed over.

How Logistics Analytics & Carrier Scorecard for ERPNext Compares

Criterion	ECOSIRE	Custom Build	Competitor	ERPNext Native
Delivery model	Build-to-order, scoped to your instance, 2-4 weeks	You hire/allocate developers and manage the build	Instant install, generic to everyone	Already in ERPNext, nothing to deliver
Carrier scorecard & SLA breaches	Purpose-built scorecard DocType with weighted breach scoring	Possible but you design and build it from scratch	Rarely included; basic if present	Not available — no scorecard concept
OTIF tracking	Promised vs. actual date + qty, per shipment and per carrier	Buildable with in-house effort	Usually absent or shallow	No OTIF metric out of the box
Lane & zone cost analysis	Origin-destination cost-per-kg/unit drill-down reports	Depends entirely on your team's design	Generic shipping report, not lane-level	Document lists only, no lane rollups
Fit to your data & connectors	Mapped to your exact carriers and DocTypes	Fully custom but all effort is yours	One-size-fits-all, adapts poorly	Limited to core fields as-is
Upgrade safety	Separate Frappe app, hooks not core patches	Depends on your engineering discipline	Varies by vendor quality	Core, upgrades cleanly but no features
Support & ownership	Post-go-live support window + full git repo handover	You own and maintain everything	Vendor support tiers, closed source common	Community/ERPNext support only
Total cost to first dashboard	Fixed scoped quote, predictable	Uncertain — internal dev time and rework risk	Low license fee but heavy config/gap-filling	Free but you still build the analytics yourself

Frequently Asked Questions about Logistics Analytics & Carrier Scorecard for ERPNext

Is this an instant download from the Frappe Cloud Marketplace?

No. This is a build-to-order product. ECOSIRE builds the Frappe app against your specific ERPNext instance, carriers, and KPI requirements, then installs and supports it. There is no instant-download package — the work starts after a scoping call and a confirmed scope.

How long does delivery take?

Typical delivery is 2-4 weeks from confirmed scope. The clock starts once we have agreed the exact carriers, connectors, DocTypes, KPIs, and breakdowns on the scoping call. Larger or multi-connector scopes may run longer, and we tell you honestly before you commit.

Which ERPNext versions are supported?

We build and test for Frappe/ERPNext v15 and the v16 line. Tell us your exact version on the scoping call and we target it. If you are on an older LTS, we will advise whether an upgrade is needed first.

How do you get carrier on-time and cost data into the dashboards?

We capture ship date, promised date, delivered date, and billed freight from your Delivery Notes, Shipments, and existing carrier connector payloads using `hooks.py` doc events, then roll them up with scheduler jobs. Where a carrier exposes tracking, whitelisted methods and the Frappe REST API pull delivery confirmations for true OTIF.

Will this modify ERPNext core or break on upgrade?

No core patching. It ships as a separate Frappe app with its own module, DocTypes, hooks, and scheduler events, installed via `bench install-app`. That keeps it upgrade-safe and cleanly removable. We test against your target version before go-live.

What support and updates do I get after go-live?

You get a post-go-live support window for defect fixes and configuration adjustments, plus the full git repository so your team (or ours, on a later engagement) can extend it. Version-upgrade or feature-expansion work beyond the support window is quoted separately.

How is data visibility controlled across regions and teams?

We ship role profiles and DocType permission rules. Regional ops leads see only their company/warehouse scope, finance gets read-only spend visibility, and admins retain full access — all enforced by ERPNext's native permission system, not client-side hiding.