Warehouse teams running ERPNext usually discover inventory drift the hard way: a Sales Order confirms stock the bin does not actually hold, or a year-end count writes off value nobody can explain. ERPNext ships a Stock Reconciliation DocType and a Stock Balance report, but that is a manual, all-or-nothing correction tool. It has no concept of a recurring count cadence, no ABC prioritization so high-velocity SKUs get counted more often, no blind-count discipline to stop counters from rubber-stamping the system quantity, and no structured approval before an adjustment posts to your stock ledger and General Ledger. Once you have more than a few hundred SKUs across multiple Warehouse records and bins, the native path effectively forces a full physical stocktake to trust your numbers — which is exactly what continuous cycle counting exists to avoid.

ECOSIRE builds a dedicated Frappe app that installs cleanly onto your bench as its own module, so nothing in ERPNext core is patched and upgrades stay safe. We add DocTypes such as Cycle Count Plan (ABC-class cadence rules, warehouse and item-group scope), Cycle Count Sheet (the count task assigned to an operator), and Count Variance (a per-line discrepancy record). A scheduler_events entry in hooks.py runs a daily job that reads each plan, classifies items into A/B/C bands by consumption or valuation value using ERPNext's own Bin and stock-ledger data, and auto-generates count sheets so the right SKUs surface on the right day — A-class items far more often than C-class.

Counting itself is scan-driven. Operators open an assigned Cycle Count Sheet on a phone or handheld, scan the item barcode (reusing ERPNext's existing barcode field on Item) and the bin, and enter a counted quantity — with the system quantity hidden by default so the count is genuinely blind. A validate doc-event and whitelisted server methods (exposed through the Frappe REST API for the mobile client) compute the variance, and a configurable tolerance triggers a mandatory recount before anything can be submitted. Confirmed variances flow through a Frappe Workflow: a supervisor reviews each Count Variance, and on approval an on_submit hook posts a scoped Stock Reconciliation for only the counted lines, writing a full audit trail of who counted, who approved, and when. Count-accuracy KPIs — hit rate, absolute variance, and value variance by bin and by operator — are delivered as Query/Script Reports and dashboard charts. Role profiles and permission rules keep counters, supervisors, and stock managers cleanly separated, and client scripts streamline the scan-and-count screen.

Because this is build-to-order, you are not downloading a fixed marketplace app. We start with a short scoping call to confirm your warehouse and bin structure, ABC rules, tolerance thresholds, and approval chain, then build against your Frappe/ERPNext v15 or v16 site. You get the installable app source for your version, installation and configuration on your environment, a UAT pass on a staging bench with a rollback plan, and a post-go-live support window. Typical delivery is one working week from confirmed scope, and the full git repository is handed over to you at the end.