Calculation of Available, On Hand and Allocated Stock quantity
For reach product in the system, Cin7 Core keeps track of the following quantities:
On Hand
Allocated
Available
On Hand
On Hand quantity is always calculated based on actual transactions, operations and/or inventory cards. On Hand quantity is the quantity you expect to see in your warehouse. This includes products from sale orders which have yet to be fulfilled. This does not include products from purchase orders that are yet to be received.
Allocated
Allocated quantity represents the quantity of the product reserved to be used in the pending sale and/or work orders. These orders are not yet completed yet but are authorized, and for successful completion, items are reserved to avoid double selling. Allocated quantity is used to determine Available quantity for Quoting, Ordering, and Picking.
Available
Available quantity is always a difference between On Hand quantity and Allocated quantity.
Available quantity = On Hand – Allocated
There are two ways that Available quantity is calculated:
General Available quantity per product, regardless of the batch info (the actual result depends on the Available quantity is limited to either all or selected locations parameter on the General Settings page).
Available quantity specific to the defined location, batch, and expiry date.
Value of Stock on Hand
To find the value of stock on hand on a certain date, run the Inventory Movement Summary report for that required date.
This Stock on Hand value is calculated from stock that has been received. Please note, the Inventory figure on financial reports such as the Balance Sheet is calculated from when purchase invoices are authorized.
If you have goods invoiced not received or goods received not invoiced, you may see discrepancies between these figures. If you see discrepancies, you can then run the Transactions Vs Stock on hand difference on the same date to find them and reconcile the reports.
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB