Cold-storage and public-warehouse operators run a business ERPNext core was never modeled for: they hold other people's goods, bill for rent rather than sell inventory, and must answer at any moment "whose lot is in which chamber, since when, at what temperature, and how much rent has accrued." ERPNext's native Warehouse and Stock Ledger track your own stock at a warehouse node — they have no concept of an owner (depositor), no chamber/rack/bin hierarchy below a warehouse, no gate-pass workflow for inward/outward movement, and no rent engine that prices storage by weight × days × space. Operators end up running the actual business in spreadsheets and WhatsApp, then re-keying totals into ERPNext for invoicing, which is where the disputes and revenue leakage begin.

ECOSIRE builds a proper Frappe application — a versioned app with its own module, installed onto your ERPNext site — that models the cold-storage business as first-class DocTypes. A Chamber DocType carries temperature band, capacity, and rack/bin child rows; a Storage Lot links a depositor (Customer), commodity (Item), inbound weight/quantity, and its current chamber allocation; a Gate Pass DocType handles inward and outward movement with weighment, so every kilogram in and out is a submittable, auditable document. Rent is computed by a server-side engine driven by a configurable Rent Plan — flat per-bag, per-kg-per-day, per-pallet-per-month, or slab-based — so the same app can bill a potato cold store and a pharma warehouse without code changes.

Technically, the automation lives where Frappe expects it. hooks.py doc events (on_submit, validate) fire when a Gate Pass is submitted to move stock between chambers and update the owner-wise ledger; a scheduler_events daily job accrues storage rent and flags lots crossing free-period or expiry thresholds; whitelisted methods (@frappe.whitelist()) expose rent calculation, current-occupancy, and lot-lookup over the standard Frappe REST API so weighbridge software, a gate kiosk, or a customer portal can integrate cleanly. Temperature and humidity readings are captured as their own logged DocType (manual entry or REST push from IoT sensors) and surfaced per chamber. Owner-wise stock ledgers, occupancy dashboards, and an "outstanding rent" report are delivered as Query/Script Reports. Role profiles and permission rules separate Gate Operator, Chamber Supervisor, and Billing/Accounts so the person at the gate cannot alter rent plans, and client scripts keep the data-entry forms fast at the weighbridge.

Because this is build-to-order, nothing ships until we understand your facility. We start with a scoping call, confirm your chamber layout, commodities, rent rules, and gate workflow in a written spec, then build the app against ERPNext v15 or v16, test it on a staging copy of your site, and hand over installable source plus a git repository. Typical delivery is one working week from confirmed scope. We install it on your ERPNext instance, run UAT with your team, train your gate and billing staff, and stay on through a post-go-live support window — there is no instant download, because the value is in fitting the app to how your cold store actually runs.