Bin Tree and Movement Ledger: From Receipt to Custody
Stock tracked at warehouse total and bin level
Each warehouse has a corridor–rack–slot bin tree; bin stock holds shelf quantity, stock level holds the warehouse total. The ledger records receipts, issues, transfers, returns, scrap and adjustments with cost centre and bin. Inter-site transfer runs ship then receive. Work-order part demand becomes pick lists confirmed by scan. Custody tracks PPE and tools per person. One movement engine updates both levels.
Bin tree and codes
RACK, FLOOR, RECEIVING, SHIPPING, QUARANTINE types; qrToken and barcode for field selection.
Movement ledger
All movements with supplier, receipt, count and cost centre links.
Two-step transfer
Shipped qty in transit; receiving warehouse completes stock.
Custody
Open custody per person; return and loss close with movements.
Pick lists
Material request or WO lines become picks; kits explode to components.
Barcode in the field
Scan API fills forms; user–warehouse scope limits access.
Operations
/mass/movements filters history; warehouse detail shows bin stock. POSTED receipts create IN movements.
Work-order consumption still draws Mass stock; Axis inventory routes to /mass when Mass is licensed.
- 1
Build warehouse and bins
Create warehouses and bin locations; label critical bins.
- 2
Post movements and transfers
Post IN/OUT, two-step transfer or custody from the relevant form.
- 3
Pick and scan
Confirm pick lines by scan; reservation decreases stock.
FAQ
Warehouse vs bin consistency
One movement engine updates stock level and bin stock together.
Movements during count
Open count sessions lock the warehouse to protect variance.
Negative stock
Controlled by the Mass negative-stock setting; default is off.