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 > > > > > >
