Retail Stock Transfers: Treat In-Transit as a Third Location
A practical stock-transfer workflow for multi-location retailers, from request and dispatch through receiving, exception handling, and daily reconciliation.
A retail stock transfer is not complete when the sending store packs the box. It is complete when the receiving store counts and accepts it. Treat in-transit merchandise as a third location, assign one owner at each handoff, and reconcile exceptions the same day. That keeps availability honest and prevents two stores from claiming the same units.
Why transfers create phantom inventory
Moving merchandise between stores looks simple: one location has too much, another has too little, so a manager sends a box. The trouble begins when the system quantity changes before the physical handoff is complete. The sending store may believe the units are gone while the receiving store believes they are already available. A customer sees “in stock,” but the product is still in a car, stockroom, or shipping carton.
The fix is not a longer spreadsheet. It is a transfer state that everyone can understand: requested, picked, dispatched, received, and reconciled. Each state answers a different question. What should move? What actually left? What arrived? What needs investigation?
Start with a transfer request, not a hallway promise
A useful request identifies the sending location, receiving location, SKU, quantity, reason, needed-by date, and requester. “Send more blue cases” is not a request; it is an invitation to move the wrong variant. Use the exact item identifier and count.
Add the reason because it affects priority. A transfer that fills a confirmed customer hold is different from one that balances a slow shelf. If two stores ask for the same item, the owner or inventory lead needs enough context to choose. The request is also the first audit point: it proves that the movement was intentional.
Before approving, look at demand and shelf capacity in both locations. Do not drain the sending store just because its quantity is higher. The goal is not equal stock. The goal is the right stock for each location’s actual selling pattern.
Pick and count away from the sales floor
The sending employee should pick against the approved request and record what was actually found. If the request says six and the shelf holds five, dispatch five and log the shortage. Never change the record to six just to make the request look complete.
Count the units in a staging area, label the container, and keep it separate from sellable stock. The label should carry a transfer number, origin, destination, date, and number of packages. For high-value or look-alike products, a second scan or count can catch a variant error before it travels.
Once packed, the merchandise is no longer available to the sending store. But it is not yet available to the receiving store either. This is the moment when “in transit” earns its place as a real inventory location.
Dispatch creates custody, not a sale
Record who took custody, when, and how the package is traveling. That could be an employee, courier, or parcel carrier. Keep the process proportionate: a ten-minute drive may need a name and departure time; a commercial shipment may also need a tracking number and package count.
Do not record a transfer as a sale, purchase, loss, or manual quantity adjustment. Those actions answer different accounting and operational questions. A transfer changes location, not company ownership. Mixing transaction types can distort location performance and hide shrink.
The employee who dispatches should not mark the transfer received. Separating those actions creates a clean handoff and makes discrepancies visible.
Receive by counting, not by clicking
The receiving employee should open the package, count the units, and inspect obvious condition before accepting the transfer. The screen quantity is a prompt, not the answer. If five units were dispatched and four arrived, receive four and record one as an exception.
This is where many stores create phantom inventory: someone clicks “receive all” before the carton is checked. The problem may not surface until a customer asks for the missing unit. A thirty-second count at receipt is faster than reconstructing a week of movements later.
If the shipment arrives during a rush, place it in a clearly marked receiving zone. Do not put units on the shelf until the count is posted, and do not post receipt until someone can count. Physical and digital availability should change together.
Reconcile exceptions the same day
Every mismatch needs one owner and one next action. Common categories include short dispatch, wrong SKU, damaged item, duplicate scan, or package still in transit. Avoid a vague note such as “inventory off.” Name the event that must be resolved.
Start with the transfer trail: requested quantity, picked quantity, dispatch record, receiving count, and any partial receipt. Then check the staging and receiving areas. If the item is still missing, follow the store’s loss or carrier-claim procedure without rewriting the original transfer history.
Same-day review matters because memories, packages, and staff schedules move quickly. The objective is not blame. It is preserving the sequence so a manager can tell where custody changed.
Use a location view before deciding what moves
A cross-location view helps managers spot an imbalance before they approve a transfer. The image below is an authentic English stock screen covering three real retail locations. It uses July 2026 historical sales-period context with current stock valuation at capture; it should not be read as current-month performance.
VoVi POS supports per-location inventory and a two-step transfer that remains in transit until the receiving store counts it in. The current inventory feature list confirms that transfers and full change history are included. The screenshot is used because the topic depends on comparing real locations; the other approved images show sales comparison and customer history, which would distract from the stock-control decision.
Set one daily exception window
Transfers become manageable when someone reviews open exceptions at the same time each day. The list should include overdue requests, dispatched packages not received, partial receipts, damaged units, and transfers waiting in staging.
Keep the meeting or review short. Assign an owner and deadline to each item. A store manager can handle local staging issues; an operations lead may need to resolve recurring courier failures or approve a replacement shipment.
Watch aging, not just volume. Ten transfers completed today are less concerning than one package that has been “in transit” for four days without a tracking update.
Measure the process without rewarding bad behavior
Three practical measures are enough:
- Median time from approval to dispatch.
- Median time from dispatch to receipt.
- Percentage of transfers received with an exception.
Do not reward speed alone. A team can produce fast numbers by skipping counts or clicking “receive all.” Pair timing with exception quality and periodic physical checks.
Review trends by route and location. If one route is consistently slow, the pickup schedule may be wrong. If one store has repeated SKU mismatches, its staging labels or product organization may need attention. The metric should point to a process change, not a leaderboard for blame.
Build a one-page transfer standard
Write the rule in plain language and keep it where staff can use it. A solid standard answers these questions:
- Who may request and approve a transfer?
- Which identifier and quantity must be recorded?
- Where are outgoing and incoming packages staged?
- When does custody change?
- Who may dispatch and who may receive?
- How are partial, damaged, or missing units recorded?
- Who reviews open exceptions and when?
Train with one real box. Have one employee request and dispatch it, and another receive it. Then introduce a mismatch on purpose. If the team can show the item’s status without asking around, the process works.
Connect transfers to replenishment
A transfer is a short-term answer, not a purchasing strategy. If the same item moves along the same route every week, ask whether location minimums, order quantities, or assortment decisions are wrong. The earlier guide to the reorder point formula can help separate vendor lead time from store-to-store balancing.
Likewise, a transfer cannot replace accurate on-hand counts. If you are repeatedly moving stock that the shelf does not contain, use the out-of-stock operating guide to examine the event before changing replenishment.
The rule that keeps every location honest
A transfer has two confirmations: what left and what arrived. Between them, the merchandise belongs to an in-transit state, not to either store’s sellable shelf. Use exact SKUs, separate dispatch from receipt, count before accepting, and resolve exceptions the same day. That simple custody chain protects availability, location reporting, and the customer promise.
What else do people ask?
When should inventory move out of the sending store?
Move it out of sellable stock when the package is counted, labeled, and dispatched. Place it in an in-transit state until the receiving store physically counts and accepts it.
Who should mark a retail transfer as received?
A person at the receiving location who can count the actual units. The dispatcher should not complete the receipt, because separate handoffs make shortages and wrong-SKU errors visible.
What should a store do with a partial transfer?
Receive only the quantity that physically arrived, record the difference as an exception, and keep the original request and dispatch history intact while the missing units are investigated.
Which stock transfer metrics are worth tracking?
Start with approval-to-dispatch time, dispatch-to-receipt time, and the share of receipts with exceptions. Review aging as well, because one long-open transfer can hide a serious availability problem.