Stock Value Inventory Aging Report
Stock Value Inventory Aging Report shows how long products stay in stock in 7 aging buckets. Aging interval can be changed from 30 days to 360 days with a maximum reporting period of over six years. This report displays the stock quantity and stock value in each aging interval.
Note: Inventory Age is measured from stock received date, not purchase date. In the case of finished goods, inventory age is measured from the assembly date. If stock is moved during a Stock Transfer, the transfer date will be the new received date.
Prerequisites
Data from this report can be exported in Excel, PDF or RTF format.
Input:
Layout |
Set to the Default layout. Allows selection of saved layouts, if any. |
Save Layout As |
Allows saving of a layout for potential future use. |
Reset Layout |
Resets layout to the default layout or selected saved layout. |
Aging Bucket |
Select the number of days in each aging bucket. Minimum interval is 30 days and maximum interval is 360 days. |
Select Apply Filter to set filter fields for the report and Update to refresh the output with any new changes. See Managing Cin7 Core Reports - Filtering Reports for more detailed information about using filters.
Output:
The following output fields are available for this report. You may have to open the Configure Layout menu to add some of them to your report.
Fields | |
SKU |
Product SKU. |
Product |
The name of the product. |
Batch # |
Batch or Serial Number. |
Expiry Date |
Expiry Date of the batch. |
Brand |
Product brand. |
Category |
Product category. |
Tags |
Comma-separated product tags. |
Unit |
Product unit of measure. |
Family |
Product family. |
Bin |
Bin where stock is located within Location. |
Location |
Location where stock is stored. |
Product Additional Attribute 1-10 |
Values of product additional attributes. |
Data Headers | |
Quantity |
Quantity of item in this aging bucket. |
Value |
Stock value of all units of this item in this aging bucket. Stock Value is the sum of the exact purchase cost of each unit in the aging bucket. |
FAQs
When I run the inventory aging report, the aging appears to reset when stock item is moved from one location to another. I want the report to show aging from the date the stock was acquired to present regardless of movement between locations. Is there a way to modify the report to achieve this?
Unfortunately, this is the limitation when using stock transfer. The stock transferred to a new location will have the transfer date as new date received. As a workaround, use the Inventory Movement Details report instead to get the receive date in the PO. You could filter the report to exclude Stock Transfers and Stock Adjustments to be able to get actual inventory aging.
Is there a way to generate the Inventory Aging Report as at a certain date?
Unfortunately, no. Once you pull up the Inventory Aging Report, it pulls up the current age status of the products. This can be added as a feature request in the forum. You can run Inventory Movement Details report to view product movement by time interval.
Still no answer to your question? Please do not hesitate to get in touch with Cin7 Core support.
- 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