Stock Transfer not Impacting FIFO

started a topic over 4 years ago

When you do an internal stock transfer e.g. Move product A from Bin 1 to Bin 2, Dear treats this as left the warehouse completely and arrived as the "Last In" in regards to FIFO, even though it could be out oldest batch.

This is really not practical, is there anyway of changing it so that "internal stock movements" do not impact on the FIFO ordering?

In reality, we are not able to move stock at all in our warehouse currently as it impacts our FIFO and autopick functions.  This is a HUGE flaw in the system, making it almost unusable for us.  If this is not rectified, we have no choice other than to move to a new ERP system.

3 people like this idea
  • We, too, are having an issue with this. Not only is the issue with internal stock movements, but also when creating inventory using the zero-stock adjustment option.

    An example is: After an inventory audit, we've found product with a batch number that shows as out of stock, however, we have some on hand and available. When creating the inventory in DEAR using the zero-stock adjustment function, the batch number and expiration date are older than the current inventory. Assuming a FIFO method, these products should then be the first to be allocated to incoming orders. However, they are not and in fact, are the last to be allocated because DEAR's FIFO method is based on the date the product was entered into the system, not based on batch/expiration dates entered.

    This results in the risk of sending out old/expired (food) product as a result of improper FIFO function.

    1 person likes this
  • This is also something that has prompted us to consider a different ERP system and we need a fix! 

Login or Signup to post a comment

3 people like this idea
Log in or Sign up to post a comment