Logistics and transportation providers run on quotes, freight orders, yard slots, and jobs — but ERPNext core has no vocabulary for any of it. Teams end up bending the Sales Order and Delivery Note DocTypes into cargo bookings, tracking yard positions in spreadsheets, and reconstructing which driver ran which leg from email threads. Native Stock Entry and Delivery Note model warehouse movements, not multi-leg freight jobs with rail and road segments, cargo quantities in mixed units, and service activities that need to be logged and billed per job. That gap is exactly where this build-to-order app lives.

ECOSIRE builds a proper Frappe app — installed onto your bench as a versioned module, not a pile of customizations — with first-class DocTypes for Cargo Booking, Freight Order, Yard Slot, and Job (plus supporting child tables for cargo lines and service activities). The pipeline is enforced in hooks.py doc events and server scripts: a submitted Cargo Booking generates a Freight Order, which spawns one or more Job records for the rail and road legs, each carrying its own transport configuration, cargo quantity, and status. Job status transitions are validated server-side so a leg cannot be marked delivered before it is dispatched, and on_update/on_submit handlers keep yard occupancy and cargo quantities consistent. Real-time job-status tracking is exposed through whitelisted methods over the Frappe REST API (/api/method/...) so your dispatch board, driver app, or customer portal reads the same source of truth.

Everything is wired into ERPNext's own machinery rather than bolted alongside it. Service activities logged against a job flow into billing through ERPNext's native Sales Invoice, so operations and finance stay on one ledger. Client scripts drive the booking and dispatch forms (dynamic fields, quantity validation, quick actions); scheduler events run periodic sweeps — stale-yard alerts, SLA checks, auto-status rollups. Access is controlled with Frappe role profiles and permission rules so dispatchers, yard staff, drivers, and finance each see only what their role needs. The app targets Frappe/ERPNext v15 and v16 and is delivered as clean, PEP8-conventioned source in its own git repository.

Because this is build-to-order, nothing ships as an anonymous marketplace download. We start from your actual freight flows — which transport modes, which yard layout, which billing model — and build the app to fit. Typical delivery is one working week from confirmed scope. You get the installable source for your version, UAT on a staging bench with a rollback plan, install and configuration on your environment, documentation and a training session, the full git repository handed to your team, and a post-go-live support window to settle real-world edge cases.