AWRA OpsHub Search

AWRA Help Center

Copy link
Inventory Stock Reports
01 Inventory Module Guides 02 Receiving Stock Step-by-Step Workflows 03 Stock Mismatch Troubleshooting

Transfers On The Floor: Pick, Pack, Photos & Discrepancies

Pick and pack a transfer before it leaves, photograph each handover, and when a delivery arrives short, open a case that has to say where the missing units went. The In-Transit Ledger checks that every dispatched unit is accounted for.

A transfer is still requested, approved, dispatched and received as described in Transfers. This page covers the warehouse floor steps around those stages. They are on the transfer page on the web and on the transfer screen in the AWRA mobile app, and the app can queue them while offline.

Pick

  • Before dispatch, a pending transfer line can be picked: enter how much was actually taken off the shelf.
  • The quantity picked becomes the quantity that will be dispatched. If you pick less than was requested, that is recorded as a short pick. You cannot pick more than was requested, or more than the source has available.
  • To send nothing at all, reject the line instead of picking zero.

Pack

A picked line is packed into a number of packages: a count, not a description. Once a line is packed, it cannot be picked again, because that would change a sealed package. Picking and packing are optional. A transfer without them is dispatched exactly as it was before.

Photos At Each Handover

Attach photos at the pack, dispatch, receipt and discrepancy stages, up to 24 for each transfer. Each stage accepts photos only while it is still open. If a photo fails to upload, the handover itself still goes through.

When A Delivery Arrives Short

  1. Receive what actually arrived. If it is less than was dispatched, AWRA asks why (the reason is required) and who is responsible, and opens a discrepancy as part of the same receipt. A short receipt cannot be saved without one.
  2. The missing units left the source at dispatch and did not reach the destination, so they are on neither shelf. Investigate records notes while you find out what happened. It does not move any stock.
  3. Resolve by saying where the units are: found at the destination (they go onto its shelf), sent back to the source (they go back onto that shelf), or written off. The three numbers must add up to the missing quantity, so nothing is left unexplained. For serial-tracked items you name which serials were found or returned.
  4. A write-off is the point where the inventory account is reduced. It posts against the same loss account a count shortage uses, at the cost fixed when the units were received. If the request is retried, the loss still posts only once.

A short delivery received before discrepancies existed can have a case opened for it from the transfer page, so it can be worked to a resolution in the same way.

The In-Transit Ledger

Reports → In-Transit Ledger lists every dispatched transfer line and checks it three ways:

  • The line balances: dispatched equals received plus returned plus still in transit plus short.
  • The movement trace agrees: the stock movement records at both ends match the transfer. Lines older than movement tracing are marked as untraced, not as wrong.
  • Every short unit is accounted for: a shortfall with no discrepancy, or with one still open, is flagged.

Filter it by date, status and warehouse, and export it to CSV. It is also in the mobile app.

Which End Does What

Picking and packing are done at the source warehouse, and a discrepancy is worked at the destination. A phone assigned to a different warehouse, or an account restricted to a different warehouse, is refused, and the message names both warehouses. Investigating is only a note, so it can be done from anywhere. See Warehouse Map, Storage Rules & Assigned Phones.

Offline

In the app, pick, pack, discrepancy steps and photos are queued while offline and sent when the phone reconnects. A queued step is never applied twice. If the transfer has changed in the meantime, for example it was dispatched from the web while the phone was offline, the step is reported back as a conflict instead of being applied to the new state. See Offline Operations Center.

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.

Open support guide