Hi Devanshu, I like the idea of adding an inventory inspection workflow after receiving.
I look forward to the document detailing the process flow, data modelling, and use cases. You can also start creating a Jira ticket for this. Thanks -- Divesh Dutta www.hotwasystems.com On Fri, Jul 3, 2026 at 9:06 PM Devanshu Vyas <[email protected]> wrote: > Hello all, > > Currently, in OFBiz, receiving a Purchase Order (PO) typically places > inventory directly into an available state and stores it in standard > warehouse locations (such as Pick or Bulk). As a result, the received > inventory immediately contributes to Available-to-Promise (ATP) and becomes > eligible for reservation and order fulfillment. > > > Many businesses conduct inventory inspections at the time of receipt and > input the results into OFBiz. > > > An Inventory Inspection Workflow plays a vital role in the receiving > process. Its purpose is to ensure that only QA passed inventory is made > available for use. From a financial standpoint, an inspection workflow is > also crucial for maintaining *inventory accuracy, *ensuring* financial > ledger accuracy, *promoting* supplier accountability, *ensuring > * compliance, ˘ *facilitating* auditing*. > > > This is a controlled process which simplifies inventory reconciliation and > reduces the risk of identifying defective inventory in the later stages of > fulfilment. > > > Almost all businesses need an inspection and quality assurance (QA) > process in their warehouses after receiving and before it is ready for the > end-goal usage. The received items need to be verified for quantity, > packaging, physical damage, expiration dates, or compliance with quality > standards before they can be considered usable. > > > Thus, I would like to propose a dedicated* Inventory Inspection Workflow* > in > OFBiz. The objective is to introduce an inspection stage between receiving > inventory and making it available for order fulfillment, while maintaining > complete visibility of inventory movements and status changes throughout > the process. > > > A high-level process flow would look like: > > - *Receiving at Inspection Bay:* When warehouse staff receive a PO, they > receive the items into a dedicated staging area, such as a > *Receiving/Inspection > Bay*, instead of directly into standard warehouse locations (e.g., Pick > or Bulk). Received inventory is assigned to *Unavailable* status. During > this stage, the inventory contributes *0 ATP*, ensuring it cannot be > reserved or allocated to sales orders until the inspection is complete. > - *Quality Assurance (QA) Check:* The QA team inspects the inventory for > quantity accuracy, physical damage, packaging condition, expiration > dates > (where applicable), and overall product quality. > - *Disposition:* > - *Pass:* The inventory passes inspection and is approved for storage > in standard warehouse locations. > - *Fail:* The inventory fails inspection. Its status is updated to > *Defective* (or a similar status), and it can be moved to a > designated *Quarantine* location for furtheraction, such as return to > supplier, disposal, or rework. > - *Putaway (Transfer):* Inventory that passes inspection is transferred > from the *Inspection Bay* to standard *Bulk* storage locations. This > inventory movement is recorded in the system. At this point, the > inventory > status changes to *Available*, and its ATP is updated to match the > available QOH, making it eligible for reservation and order fulfillment. > > > This workflow introduces a controlled quality gate into the receiving > process, ensuring that only verified inventory becomes available for use > while improving inventory integrity, operational traceability, and supplier > quality management. > > I will be working on a document laying out process flow, data modelling > enhancements, use-cases, etc. Once the document is ready, I will share it > here for review. > > I would like to know your thoughts on the proposal and any unique or > specific use cases that might help us in building this workflow in a better > way. > > > Thanks & Regards, > Devanshu Vyas. >
