This tutorial explains how to create and manage inventory documents in BRAINR.• Define locations and (optionally) materials to count. • Choose inventory type (Guided or Blind) and whether to account for tare weights. • Use the document statuses to control the process and ensure accurate counting.
On the Homepage, navigate to the "Inventory Documents" module in the Warehouse Inventories section.
In the upper right corner, click on "Create Inventory. "
Fill in the required fields.
Description to identify the inventory.
Inventory Date (different from the creation date).
Type:
Guided: During counting, we have visibility of the expected quantity and weight.
Blind: When counting, there is no visibility of the expected quantity and weight.
Tare accounting: Adds an extra step to enter tare weights on the web and validate them on mobile. If tare weights are configured, they will be automatically classified.
☐ Does not consider tare weights in inventory.
☑️ Considers tare weights in inventory.
Force Empty Location Accounting (currently not functional).
We can do two types of inventories:
Warehouses/Locations: The system searches for the expected materials in these locations or allows you to specify locations to inventory.
Warehouses/Locations and Materials: The system considers the materials expected in the assigned locations.
Note: The system does not allow picking from warehouses/locations other than those specified.
Could not display content
Add warehouse or location to be inventoried, with the option to apply filters.
Optionally, specify the materials to be inventoried in the warehouses, with filters available. The system will still allow you to pick other materials.
When the inventory is configured, click "Save. " The system will retrieve all expected materials if no material has been specified.
After creating the inventory document, you can edit, cancel, or pass the document. When you switch to "Open," it becomes available to start counting on mobile and web.
When a status change is made, the document goes through an intermediate state where the necessary calculations are performed. This ensures fewer errors in the system and a better experience. If a failure occurs during counting, the user will see the status in red and can return to the previous status to resolve the issue.
