Container & Yard Management for ERPNext

ECOSIRE builds a proper Frappe app (its own module, installed with bench get-app / bench install-app) rather than a pile of Custom Fields. At its core is a Container DocType carrying ISO number, size/type (20GP, 40HC, reefer, etc.), seal number, ownership, and a status field driven through a controlled lifecycle — Expected → Gated In → In Yard → Under Job → Gated Out. A Yard Slot DocType models your physical layout (block/row/bay/tier), and a Gate Transaction DocType records every gate-in and gate-out with truck, driver, timestamp, and photos. State changes are enforced in hooks.py doc events (validate, on_submit, on_update) and server scripts so a container can never occupy two slots at once or be gated out while a job is open.

Demurrage and detention are handled by a scheduled job: a scheduler_events hook runs a whitelisted method on a cadence, walks containers past their free-day threshold, and computes accruing charges against a configurable Demurrage Tariff (tiered day bands, currency, grace period). Charges post back into ERPNext Sales Invoices so billing stays in one system. Loading and unloading are captured as Container Job documents with line-level cargo, linked to Stock Entries where you also move inventory. Everything is exposed over the Frappe REST API and @frappe.whitelist() methods so your gate kiosks, handheld scanners, or a driver-facing portal can post events in real time, and Client Scripts add in-form validation and quick actions on the desk.

Access is governed by Frappe Role Profiles and permission rules — gate clerks post transactions but cannot edit tariffs, yard supervisors reallocate slots, finance sees the demurrage ledger — with User Permissions to scope operators to a single depot in a multi-location setup. Reports, a yard-occupancy dashboard, and print formats for gate passes ship as part of the build. The app targets Frappe/ERPNext v15 and v16.

Because this is build-to-order, nothing is a black box: after a short scoping call we confirm your yard layout, tariff rules, gate workflow, and integrations, then build to that agreed spec. Typical delivery is 2–4 weeks from confirmed scope. We install it on your bench (Frappe Cloud or self-hosted), run UAT on a staging site, train your team, and hand over the full git repository so you own the source. There is no instant download — you get an app fitted to how your yard actually runs.