You are right on everything. But giving an optional check on a minimum quantity can be a first step to have a better control on the inventories.
Yes, I strongly agree on this. A minimum quantity level will alert you that you should create PO for that specific item.
Any update sir
2 Likes
Maybe this helps to make stock orders easier but as Custom fields can be exported to Excel the minimum inventory or Reorder Point (ROP) can maybe be solved that way. At least I gave it a shot and seems usable
If five new Custom fields are made for Inventory items, see picture, then ROP can be compared to Qty owned to see if replenishment is due and how much stock needs to be ordered.
For example:
Line 1: ROP is 1 but Qty owned is 0 so reordering is needed.
Line 2: ROP is 10 and Qty owned is 12 so no reordering is needed.
The key ingredient for such a decision is regular (weekly?) manual input into column 2 “Estim. usage NOW for replenishment lead time” (which can be done in Excel) as it can vary widely during the year for Inventory items which number is used. For example for some retail companies they can maybe sell as much in December as the total sales for all the other months in the year. For other companies a static ROP may do but this of course depends on the business and required precision.
If this is constantly updated no alerts would likely be needed as only the review of the table would do. But lets say if update is weekly, the table can still be exported to Excel, lets say every 1-2 days, fairly easily with only updated Qty owned column to compare it to ROP to see if there are any new unforeseen issues.
Column 4 ROP has to include the Excel formula SUM() for the total to update correctly
Topmost Item code can hold the single date (column 5) for the update of the whole table to keep track of updates. There is no need to add the date to all Inventory items.
For information about other columns, Lead time and Safety stock, see https://en.wikipedia.org/wiki/Reorder_point
The Excel table is then imported/updated back into Manager
1 Like
@Tor’s process is a very good example of why the export function and custom fields exist. The program developer could never anticipate all users’ desires for management information and reports. Even if he took you 90% of the way to what you wanted, you might still be frustrated. And the more needs that are catered to, the more bloated and difficult to use the program becomes. The philosophy has been to provide basic information and recognize that outside analysis and display will always be necessary. I’ve worked for Fortune 100 companies with all the resources in the world for customized accounting and management information systems. In every case, there were many things routinely handled with spreadsheets.
1 Like
Is there any update about this topic? Thanks
1 Like
@meesam, as you know, this suggestion already exists in the ideas list as a result of a topic started by you. Bombarding the developer with the same request in multiple threads does nothing to encourage implementation. Instead, it gives you a reputation as an impatient forum member, possibly causing your request to be ignored or delayed.
it will be very helpfull and it is needed
@lubos We initiated a request more than two years ago relating a feature of Re-order Q’ty/Level in Inventory Item. Since then, many users asking for this feature have been patiently waiting. Meantime, the software development had been very impressive with addition of so many significant features.
I wonder if this feature is in your work flow chart sometime in near future. An update will be appreciated.
3 Likes
Good Job
I was thinking the same use custom feilds as columns and export data in Excel to calculate like a report
Yes, Promo_Brick you can export to Excel and view report there. You don’t have to import back into Manager unless its beneficial like if there are other employees wanting to see the information inside Manager