Thank you Arun, Ratnesh, and Devanshu for reviewing the proposal and sharing your inputs.
I am trying to start with a basic foundation for inventory cycle counting, and the points you shared on concurrent inventory changes, recount handling, multiple counting levels, and temporary location locks are very helpful. These will help improve the design further. The staging-layer approach is to keep adjustments controlled and properly reviewed before updating the core inventory records. As the next step, I will work on an initial plugin design covering the data model, workflow, and service flows so we can review it further with the community. Please feel free to share any other suggestions or use cases. Kind Regards, Chandan Khandelwal On Wed, Apr 22, 2026 at 6:20 PM Devanshu Vyas <[email protected]> wrote: > Hello Chandan, > > The Data Model for the Staging layer for the Cycle Counting process look > good. > > Ratnesh correctly pointed out handling concurrent inventory changes during > active counting sessions. > One of the practices many warehouses follow is to lock the location for any > new reservations or proposed stock movements. > > We should consider this during the feature design and modelling. > > > Thanks & Regards, > Devanshu Vyas > *HotWax Systems* > > On Tue, Apr 21, 2026 at 6:47 PM Ratnesh Upadhyay < > [email protected]> > wrote: > > > Hi Chandan, > > > > Thanks for sharing the details, the data model plan looks good to me. > > > > A few more points to consider: > > - - Handle concurrent inventory changes during active counting sessions. > > - - Recounts/multiple entries in InventoryCountItem for discrepancies. > > - - Multiple counting granularities. > > > > The staging-layer approach looks good for maintaining control and > > auditability before applying adjustments. > > -- > > > > Best Regards, > > Ratnesh Upadhyay > > > > *HotWax Systems* > > *Enterprise open source experts* > > > > http://www.hotwaxsystems.com > > > > On Tue, Apr 14, 2026 at 10:57 AM Arun Patidar <[email protected]> > > wrote: > > > > > Chandan, > > > > > > Thanks for sharing the details. Data modeling makes sense to me. > > > > > > > > > Regards > > > --- > > > Arun Patidar > > > > > > > > > > > > > > > On Tue, Apr 14, 2026 at 10:39 AM Chandan Khandelwal < > > > [email protected]> wrote: > > > > > > > Thank you Arun and Ratnesh. > > > > > > > > Following up on the earlier discussion, here’s a quick outline of a > > data > > > > model we could use for the Inventory Cycle Count (ICC) plugin. The > goal > > > is > > > > to introduce a staging layer for the counting workflow before any > final > > > > adjustments are applied to the core inventory. > > > > > > > > Definitely, as an initial step, we can implement this as a separate > > > plugin > > > > and later evaluate aligning it with the core framework based on > > community > > > > feedback. > > > > > > > > *Proposed Entities:* > > > > > > > > 1. *InventoryCount* > > > > Acts as the main session header. It manages the lifecycle > (Created, > > > > Assigned, Submitted, Approved) and can optionally link to > WorkEffort > > > for > > > > scheduling. > > > > 2. *InventoryCountItem* > > > > Stores the physical count along with a snapshot of the > > systemQuantity > > > at > > > > the time of counting. This ensures accurate variance calculation > > even > > > if > > > > inventory changes afterward. > > > > 3. *InventoryCountVariance* > > > > Captures discrepancies along with reason codes (e.g., damaged, > > found) > > > > before final approval. > > > > 4. *InventoryCountStatus* > > > > Maintains a simple audit trail of status changes. > > > > > > > > Once a counting session is approved, a service will trigger the > > standard > > > > OFBiz logic. This allows us to reuse the existing framework audit > > > > mechanisms while adding the required staging workflow needed for > > > real-world > > > > warehouse operations. > > > > > > > > I would appreciate any feedback on whether this approach aligns or if > > > there > > > > are any suggestions. > > > > > > > > > > > > Kind Regards, > > > > Chandan Khandelwal > > > > > > > > > > > > > > > > On Mon, Apr 13, 2026 at 6:32 PM Ratnesh Upadhyay < > > > > [email protected]> > > > > wrote: > > > > > > > > > Hi Chandan, > > > > > > > > > > Thanks for kicking off this discussion! This looks really > > > useful—looking > > > > > forward to your initial design to gain more insights into the cycle > > > count > > > > > feature implementation. > > > > > > > > > > I’d love to be involved in the implementation—please let me know > how > > I > > > > can > > > > > contribute. > > > > > > > > > > Regards, > > > > > > > > > > Ratnesh Upadhyay > > > > > > > > > > On Wed, Apr 8, 2026 at 5:45 PM Arun Patidar < > [email protected]> > > > > > wrote: > > > > > > > > > > > Hi Chandan, > > > > > > > > > > > > The requirements you outlined for a standardized cycle count > > process > > > > look > > > > > > solid. This functionality will be very beneficial for businesses > in > > > > > > maintaining inventory accuracy. > > > > > > > > > > > > Best regards, > > > > > > --- > > > > > > Arun Patidar > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Apr 6, 2026 at 3:45 PM Chandan Khandelwal < > > > > > > [email protected]> wrote: > > > > > > > > > > > > > Hello Dev, > > > > > > > > > > > > > > I would like to start a discussion about inventory cycle > counting > > > and > > > > > how > > > > > > > it can be effectively supported within OFBiz. > > > > > > > > > > > > > > Cycle counting is a common warehouse practice used to maintain > > > > > inventory > > > > > > > accuracy through periodic counts, typically involving: > > > > > > > > > > > > > > - Planning or scheduling count runs > > > > > > > - Assigning counting tasks to warehouse associates > > > > > > > - Recording physical counts against system quantities > > > > > > > - Requiring manager review before applying variances > > > > > > > - Maintaining an audit trail of count and approval decisions > > > > > > > > > > > > > > In practice, many warehouses handle these steps outside the > > system > > > > > (e.g., > > > > > > > spreadsheets) and later apply adjustments. > > > > > > > > > > > > > > In the context of OFBiz, while it provides the foundational > > > entities > > > > > > > required for inventory adjustments, such as: > > > > > > > > > > > > > > - InventoryItem (quantity on hand) > > > > > > > - PhysicalInventory (inventory audit event) > > > > > > > - InventoryItemVariance (recording adjustments) > > > > > > > > > > > > > > there appears to be only *limited support* for a complete cycle > > > > > counting > > > > > > > workflow. > > > > > > > > > > > > > > I also came across the earlier proposal OFBIZ-10577 (Inventory > > > Cycle > > > > > > > Count), which appears to be unresolved. It would be helpful to > > > > > understand > > > > > > > whether there were design considerations behind this or if > > similar > > > > > > efforts > > > > > > > are currently in progress. > > > > > > > > > > > > > > As a next step, I have started working on a basic design and > > > > > > > implementation. I will keep it as a separate plugin for now and > > > share > > > > > it > > > > > > > with the community once I have something ready. > > > > > > > > > > > > > > If the community finds this valuable, we can further evolve the > > > > design > > > > > > and > > > > > > > implementation collaboratively. > > > > > > > Kind Regards, > > > > > > > Chandan Khandelwal > > > > > > > > > > > > > > > > > > > > > > > > > > > >
