Module guide
Workflow
Reports
Warehouses, Transfers & Scanner Guide
Use this guide to manage warehouse structure, transfer states, scanner steps, offline expectations, device assumptions, and exception handling.
Warehouse work turns AWRA records into physical action. Transfers, receiving, picking, counts, and scanner flows help teams keep stock aligned across warehouses, branches, locations, counters, vehicles, and field stores.
Warehouse Setup Basics
- Use branch and warehouse names that match how staff speak about physical locations.
- Add locations or bins only when users can maintain them accurately.
- Assign users to the warehouses they actually work with.
- Confirm scanner users are logged into the correct workspace and warehouse.
Transfer States
| State | Meaning | User Action |
|---|---|---|
| Draft / Requested | A transfer is being prepared or requested. | Confirm item, source, destination, quantity, and reason. |
| Approved | The transfer can proceed according to policy. | Warehouse team prepares goods for dispatch. |
| Dispatched / In transit | Stock has left the source but is not yet received. | Destination team should expect and verify the items. |
| Received | Destination confirms what arrived. | Record shortages, damage, or differences immediately. |
| Cancelled / Rejected | The transfer will not proceed. | Confirm whether any physical stock moved before closing. |
Scanner Flow
- Log in with your own account on the approved device.
- Confirm organization, branch, warehouse, and location context.
- Scan item barcode, asset label, bin label, transfer reference, or document code depending on the task.
- Confirm the item name, SKU, unit, quantity, and destination before saving.
- Add notes or evidence for damaged, missing, unlabelled, or substituted goods.
- Sync or confirm upload when the device returns online if offline mode was used.
Offline And Failure Behavior
- If offline mode is available, users should know which tasks can be saved while offline and which require connection.
- Do not repeat scans blindly if the network is unstable. Check whether the first scan is pending, saved, or failed.
- If a scan cannot find an item, search by name or SKU and report missing or damaged labels.
- If a device is shared, each user should still work under their own login.
- After reconnection, confirm sync status before assuming the stock movement is complete.
Common Exceptions
- Transfer dispatched but destination did not receive the same quantity.
- Barcode scans the wrong item or does not scan at all.
- Stock is physically in one location but assigned to another in AWRA.
- Offline device has pending records that have not synced.
- Goods are damaged, substituted, expired, short, or missing documents.
Warehouse rule: Always confirm item, quantity, warehouse, location, transfer reference, and device sync status before treating a movement as complete.
Support escalation
Open support guide
Need help with this topic?
Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.