Limble’s part management (Inventory) system gives users and managers an easy way to see how many parts they have available to use in a task. This includes visibility into how many parts are reserved or “on hold.”
Limble uses this information to determine when to generate a task to order new parts if the inventory has fallen below the minimum threshold.
This article explains how reserved parts count toward minimum part thresholds.
Table of Contents
How Reserving Parts Impacts Inventory & Minimum Threshold Tasks
When a user adds a part to a Limble task, the system temporarily reserves it and tells other users how many parts are on reserve. That way, users know how many parts are “available” to use.
Once a user completes a task, Limble will confirm if the parts were used and then check to see if there are any reserved parts on other tasks. If the parts used plus the parts currently reserved bring the part quantity below the minimum threshold, Limble will generate a minimum threshold task.
Candy needs to use a filter to complete a task. Currently, there are 10 on hand, but there are a total of 5 tasks that need to use that same part. This means there are a total of 5 reserved parts.
When Candy completes their task, Limble will remove the filter from the inventory and update the number of reserved parts. As you can see below, the quantity on hand is now 9, and the number of reserved filters is 4.
Next, Limble checks the part’s minimum threshold.
Limble will assume that you will use all 4 filters on reserve, so if you have 9 on hand and you plan to use 4, the system will generate a task to reorder that part because the inventory will fall below the minimum threshold of 6.