Moving stock between a shop, a back room, and a second stockroom sounds like a simple handoff—until the sending list says 12 units, the receiving shelf has 11, and nobody knows whether the missing unit was never packed, damaged on the way, or put away somewhere else. A small transfer log prevents that uncertainty by recording what was requested, what actually left, what arrived, and what still needs attention.

The key is to treat dispatch and receipt as separate checkpoints whenever stock travels or changes hands. A transfer is not complete just because someone packed a box or updated a spreadsheet. Confirm the item and unit at both ends, keep an exception visible until it is resolved, and avoid entering the same movement twice as unrelated quantity adjustments.

Choose the right level of tracking

For a quick move between nearby shelves in one room, a single logged movement may be enough: record the item, quantity, source location, destination location, and person who moved it. Update both locations as one deliberate transaction. A transfer that travels between sites, spends time with a courier, or passes between teams needs a middle status such as in transit. That status shows that the goods have left the source but have not yet been confirmed at the destination.

This distinction appears in inventory software documentation, but the software’s process is not a universal rule for every small operator. Microsoft Learn describes transfer orders with shipping and receiving steps, including an in-transit option. Oracle NetSuite’s transfer-order guide likewise explains how a transfer can be followed through fulfillment, transit, and receipt. Use these as examples of why the stages matter; a simple paper sheet or shared log can capture the same handoffs without adopting an enterprise system.

Set up a transfer record before picking

Give each move a short unique reference, such as TR-2026-014. Before anything is packed, agree on the item identity, unit of measure, requested quantity, source, destination, and a person responsible for receiving it. If “case” could mean different pack sizes, write the exact case size or item identifier rather than relying on a familiar nickname. Use consistent shelf addresses; this guide to mapping and labeling stockroom locations can help make the source and destination unambiguous.

Keep the record simple enough to use during a busy shift. A useful copy-ready log can be a paper form, spreadsheet row, or another record your team already maintains:

  • Transfer ID: one reference that follows the move from request to closeout.
  • Item and unit: item name or SKU, variant, and unit or pack size.
  • From / to: source and destination location codes.
  • Requested / dispatched / received: separate quantities, not one number reused for every stage.
  • People and timestamps: who picked, who handed off, who received, and when.
  • Status and notes: requested, dispatched, in transit, received, exception, or closed, plus any damage or shortage details.

Count at dispatch, then record the handoff

At the source, pick the requested item and verify its unit before counting. If the request is for 12 individual bottles, do not record 12 cases; if it is for two sealed cases, note the case size when that matters. Record the quantity actually packed, not only the quantity requested. If fewer units are available, write the short-pick quantity and tell the destination before dispatch so the receiving team does not expect a package that was never sent.

When the stock leaves, record the dispatch date and time, the person handing it over, and the carrier or staff member taking custody if relevant. For a move that takes time, change the status to “in transit” and keep the transfer open. In a basic location-by-location record, reflect that stock has left the source, but do not increase the destination’s received quantity before someone there confirms it. If your system has a dedicated in-transit record, follow its instructions rather than creating a second manual adjustment.

Receive by recounting, not by copying the dispatch figure

At arrival, the receiver should use the transfer reference to check the item, unit, packaging, and physical quantity. Count before putting the stock away, and compare the result with the dispatch note. Record the quantity received and note any shortage, extra item, substitution, or visible damage. A well-defined location code also helps the receiver put the goods in the intended place instead of leaving them in an unrecorded overflow area.

For example, Stockroom A dispatches 12 cartons of cups to Stockroom B. The log records 12 dispatched. B counts 11 cartons on arrival. Record 11 received and a shortage of 1; do not mark all 12 as received just to make the log balance. If the missing carton is later found on the delivery vehicle, record the later receipt against the same transfer. If it cannot be found, document the investigation and close the exception according to the business’s normal loss or adjustment process.

If one carton is wet or crushed, record that it arrived but keep its condition separate from usable stock. Photograph the damage when appropriate, notify the sender or carrier, and follow your own supplier, insurance, or safety procedures. The broader receiving checklist for short, damaged, or extra shipments covers similar checks at delivery. The principle is the same for an internal move: verify first, record the actual result, and only then update the usable quantity at the destination.

Reconcile the two location records

Once the receiver confirms the shipment, update the source and destination records from the same transfer reference. The source should reflect what actually left; the destination should reflect what was actually accepted into its stock. Keep any unresolved balance visible as in transit or under investigation rather than silently adding it to one location. This makes it easier to distinguish a transit exception from a counting error or a put-away mistake.

Do not “fix” a mismatch by independently adding stock to one location and subtracting a different quantity from another without linking the entries. That can create a false total or conceal the cause. If you use a basic list that does not track transit, maintain the transfer log as the bridge: note the dispatch deduction, the amount received, and any remaining exception, then document the final adjustment after the facts are known.

Use a short weekly exception check

Once a week, filter or review transfers that are not marked received or closed. For each one, confirm its last known custodian, expected arrival, and any carrier or staff follow-up. Ask the destination to check the receiving area and nearby shelves before treating a package as missing. When the discrepancy is settled, record the outcome—late arrival, short shipment, return to source, damage, or confirmed loss—and who approved any quantity correction.

If the physical count still does not match after transfer records are reconciled, investigate it through your normal count process instead of changing numbers without a reason. The small-stockroom cycle-counting guide offers a repeatable way to check discrepancies and record follow-up. Over time, recurring problems may point to unclear units, weak handoffs, confusing locations, or a carrier issue; use the log to improve the process, not just to close the current line.

A simple transfer checklist

  • Confirm item, variant, unit, source, destination, and requested amount before picking.
  • Assign one transfer reference and keep it through dispatch, receipt, and closeout.
  • Count and record the actual quantity leaving the source.
  • Mark goods in transit when a separate handoff or journey makes that status useful.
  • Have the destination recount before recording stock as received or usable.
  • Record shortages, extras, substitutions, and damage as exceptions; do not overwrite the original dispatch quantity.
  • Reconcile both locations and review open transfers regularly.

This method can live in a basic log or fit around the inventory records your team already uses. If you are evaluating tools, review Ququ’s current product overview and confirm its present capabilities against your specific transfer workflow. The procedure above is a team operating practice, not a claim that any particular product provides transfer orders, live multi-location syncing, or automatic quantity updates.