Monitor inventory and branch stock
To monitor inventory and branch stock, start with inventory access, the intended branch, and verified item, unit, cost, or quantity information. In Admin, review inventory summary, filter stock, search stock, and inspect movement. Verify the item, unit of measure, branch, quantity, and cost before saving any stock change.
Before you start
- Inventory access, the intended branch, and verified item, unit, cost, or quantity information
- Search before creating records and preserve the item unit of measure
Steps
- Open /inventory for the summary or /inventory/stock for stock detail, then confirm the active branch.
- Set the available stock-state filters and search for the item by its recorded name or identifier.
- Open the matching item or movement history and compare unit, quantity, and latest movement time.
- Investigate a low-stock signal from its underlying item record before creating an adjustment or changing reorder controls.
Expected result
The inventory summary or stock list shows records for the selected branch and filters, including the item’s unit, current quantity, and movement evidence where available. Opening a low-stock signal leads to the underlying item rather than creating an adjustment automatically.
Permissions
- Inventory summary and stock routes accept inventory.read or inventory-v1.read; quantity-changing actions require their separately authorized mutation.
Troubleshooting
An expected item is absent from stock results.
Confirm branch, search text, stock-state filter, and item unit, then clear the narrowest filter. Check the item record before creating or adjusting anything; a hidden row may still exist.
Quantity differs from movement history.
Stop any new adjustment, compare the latest movement time and unit with the displayed quantity, and refresh once. Escalate the item, branch, unit, quantity, and safe movement reference.
Related articles
Open in TajerGo
Sign in with the appropriate role and confirm your Business Account and branch before continuing.
Read as Markdown · Guidance for support agents
Last reviewed 2026-09-06 · Send documentation feedback