A transfer can leave one stock location without appearing in another. That does not always mean the product disappeared. The issue may be timing, incomplete receipt confirmation, incorrect destination, or a transfer accidentally posted twice.
Treat a transfer as a two-sided transaction. One side is the quantity sent; the other side is the quantity actually received. Record origin, destination, dispatch time, receipt time, item identifier, unit of measure, quantity, and transfer reference. For controlled products, include lot or batch information when required.
Example: Location A sends 24 pieces on Monday afternoon. Location B physically receives 24 but does not complete the receiving transaction until Wednesday. A Monday or Tuesday system report may show stock in transit rather than at B. A count at B on Tuesday could display an overage if physical stock arrived but its system receipt was not posted.
Reconcile the three states separately: requested, shipped, and received. A transfer should not be called complete merely because the source quantity was reduced. Ask the receiving team to confirm physical count, exceptions, and units of measure before closing.
When shipped quantity exceeds received quantity, investigate transit damage, short picks, wrong cartons, counting errors, and any unrecorded split deliveries. Match supporting documents before recording shrinkage. When received exceeds shipped, check for a duplicate receipt or a transfer paired with the wrong source transaction.
For a small operation, maintain a daily open-transfer list sorted by age. Flag transfers that have been shipped but remain unreceived beyond the normal transit window. Assign ownership for follow-up and document the resolution.
The most important design rule is that a transfer must have a clear lifecycle. Source picked, source dispatched, destination counted, and destination posted should be distinguishable statuses. When each team can see where the stock is in that lifecycle, month-end investigations become much more precise.