Logistics & Courier Management

ECOSIRE builds a proper Frappe application (a real app installed with bench get-app / bench install-app, not a pile of customize-form tweaks) that adds the missing operational spine. We model first-class DocTypes — Consignment, Waybill, Courier Booking, Rate Card, and Proof of Delivery — with child tables for package lines, dimensions, and scan events, and link them cleanly to native Customer, Address, Contact, and Sales Invoice so nothing in your ledger goes off-book. A carrier-allocation engine (a whitelisted server method) ranks eligible couriers against your rate cards and service-level rules and assigns the cheapest or fastest carrier per booking, with manual override. hooks.py doc events drive the lifecycle: on submit, a consignment auto-generates its waybill number and barcode; scan and status transitions fire on_update handlers that stamp an immutable tracking timeline; a scheduler event polls for stuck shipments and SLA breaches.

Tracking is built for the way freight actually moves. Every package and part-load leg carries its own status, so an LTL trip can show ten consignments at different stages on one manifest. Electronic proof of delivery is captured from the field — signature, photo, recipient name, and geo-stamp — through whitelisted REST endpoints your driver app or a Frappe web form posts to, and the POD attaches back to the consignment and unlocks freight billing. Rate cards convert delivered weight and zone into charges, generate the freight Sales Invoice against native ERPNext accounting, and reconcile carrier cost versus customer price so you can see margin per lane. Role profiles and permission rules separate dispatchers, drivers, billing, and carrier-partner access; client scripts add the dispatch-board and scan-entry UX inside the standard Frappe desk. It is built for Frappe/ERPNext v15 and forward-compatible with v16.

Because this is build-to-order, nothing ships blind. We start from your real consignment flow, carrier mix, and billing rules, agree a written scope, then build against it — so the DocTypes, allocation logic, and rate structure match how you dispatch, not a generic template. Typical delivery is 2–4 weeks from confirmed scope depending on courier integrations and rate-card complexity. You receive the full source, install and configuration on your bench, UAT on a staging site, and a post-go-live support window before we hand over the git repository.