Skip to main content

Stock movements due to theft, breakage, expiration or others

Stockagile allows you to make stock movements, as well as to indicate the reason for the movement. In this case, you would have the option to indicate if it was due to theft, expiration, breakage or others. It is an interesting function to have a control of what happens with the stock you have.

Requirements to indicate the reason for stock movement:

Steps to indicate the reason for stock movement:

  1. Go to the INVENTORY section in the STOCK section. Or you can do it ina producto entering in CATALOG > PRODUCTS and selecting the stock window in it.

  2. On the screen, in the row where the product appears, there is a three-dot icon in the blue product bar.

  3. Click this button and you will have the option to edit the stock; therefore, to make stock movements. The Chart cross-references data between the first variant, the second and the location. Make sure you modify the correct box accordingly.

  4. When you modify the stock, you must click on the screen to save the changes and a pop-up will appear indicating that the product has been updated and, offers the option to INDICATE THE REASON.

  5. In this case, go to the INDICATE REASON and click on the button.

  6. A window will appear where you must enter the reason for the movement (You can also add additional notes to the stock movement):

    1. Breakage

    2. Expiration

    3. Robbery

    4. Various uses (for store samples; course / showroom; internally)

    5. manual adjustment

    6. Loss

    7. Various gifts (Press / Influencer, worker, worker welcome, client, owner)

    8. Others

  7. To see the stock movements with reason, go to the PRODUCTS section and click on the product you have updated.

  8. Go to the STOCKS tab and, within STOCKS, click on MOVEMENTS and you will see in the third column TYPE a box with the reason for the movement.

Step 2: Edit the stock quantity of the products

Step 6: Pop-up to indicate the reason for stock movement

Step 10: Display transaction history

Did this answer your question?