Retail Stock Transfers: Reconcile What Left and What Arrived
Reconcile stock transfers across two stores: match dispatch and receipts, investigate partials and verify corrections without duplicate posting.
Store A says a transfer has left. Store B has received only part of it. Both teams have updated a screen, but the quantities still disagree. The next decision is not simply which balance to change. It is what each location can establish about the same movement.
A reliable transfer connects the request, actual dispatch, destination receipts and resulting records. This article develops that handoff within our retail inventory-accuracy guide. The method is Retail Sense editorial guidance for ordinary stock movements within a retail business. Adapt it to the approved workflow and actual system.
Give both locations a shared scope and clear owners
Name a dispatch lead at the source, a receiving lead at the destination and one person accountable for unresolved transfer differences. Arrange backups for shift changes. One person may hold several roles, but the source and destination decisions still need to be explicit.
Use one shared transfer reference, linked to the individual shipments and receipts. For each comparison, identify the source, destination, exact item or variant, counting unit and event concerned. A whole transfer request and one partial shipment describe different scopes.
Keep these quantities distinguishable:
- Requested: What the destination asked for.
- Verified dispatched: What the source evidence establishes actually left in this shipment.
- Physically observed: What the destination has verified at its location.
- Accepted for receipt: What the authorized process approves for receiving.
- Successfully recorded: What the relevant system action has actually posted.
A prepared carton or a transfer request does not establish dispatch. An arrival message does not establish the item quantities accepted at the destination.
GS1's Global Traceability Standard, Release 2.0 from August 2017, distinguishes tracking events such as shipping and receiving and the data describing who, what, where, when and why. That framework informs the event-matching discipline here; it is not a legal requirement for every retailer or a certification of this method.
Work through a hypothetical two-store transfer
Imagine Store B requesting 24 individual notebooks of one variant from Store A. For this shipment, 18 are verified as dispatched. At Store B, 15 matching notebooks are physically verified and approved for receipt. No additional physically held units are established in this example.
There are two separate remainders. Six requested units fall outside the verified dispatch scope. Three units from that dispatch remain unmatched against the destination receipt.
Those differences do not establish where the units are. The six are not evidence of a promised further shipment. The three are not automatically stock physically in transit, lost, stolen, rejected or cancelled. The two location owners need to investigate the appropriate events and evidence.
Record the supported events through the actual authorized workflow and verify the results. Keep the unresolved questions owned rather than choosing a convenient explanation to make the transfer look complete.
This is hypothetical arithmetic, not a client event or a test of a particular product.
Investigate the mismatch at both ends
Start by confirming that both teams mean the same variant, unit and shipment. A case count at the source and an individual-item count at the destination need a verified conversion before comparison.
Then inspect the relevant dispatch and receipt evidence. At the source, check the packages and staging or holding areas relevant to that shipment. At the destination, check the corresponding packages and locations. Recount the affected scope where appropriate and review earlier partial receipts and existing transactions.
Ask each lead what their evidence establishes. Was the quantity prepared, dispatched, physically checked, accepted, entered or successfully posted? Keep a possible miscount, wrong shipment match, unit error or incomplete posting as a question until evidence supports it.
Physically present goods awaiting an acceptance decision are different from absent units. Identify those goods and their actual holding location under the business's controlled process. Do not describe them as missing merely because the accepted quantity is lower.
Equally, an open transfer status does not independently locate goods. Avoid counting one physical unit at both stores merely because both records mention the movement.
Verify what the system action actually did
Confirm which action affects which quantity, location and status in the retailer's configuration. Check who can correct an event and what evidence shows that a submitted action succeeded.
Shopify's current transfer documentation, for example, allows specific quantities to be received and leaves a partial transfer In progress while quantities remain outstanding. Those are product-specific workflow definitions, not proof of the physical location of every outstanding unit.
Microsoft Dynamics 365 Commerce documentation, updated January 28, 2026, illustrates another distinction. When asynchronous document processing is used, submitting a receipt and successfully posting it are different stages; a processing failure can leave it unposted. That example depends on the documented configuration. Other systems and setups may behave differently.
The operating question is therefore concrete: what did this transaction do to the relevant records at each end? Inspect the actual result before deciding another action is needed. Do not assume that two differently named stock states are directly comparable physical balances.
Correct existing events and receive later partials once
If dispatch or receipt was recorded incorrectly, inspect the original transaction before changing anything. Give the authorized owner the supported quantity, evidence and references. Retain the before-and-after values and verify the resulting records at both ends through the approved correction route.
Do not receive the entire transfer again or make offsetting adjustments simply to force matching totals. A plausible balance can conceal an incorrect event or a duplicate receipt.
Return to the notebook example. If Store B already recorded a full receipt, that existing event needs investigation. Posting another 15 would add an event rather than explain the first one.
If three matching notebooks later physically arrive and are approved for receipt, connect the new receipt to the original dispatch and the earlier accepted 15. Record only the newly verified event through the appropriate workflow, then reconcile its result. Separately establish whether any of the six requested units will be dispatched in a further shipment. That would be its own event, not an assumed completion of the earlier one.
Keep posting and physical follow-up at their actual statuses
A confirmed receipt can be recorded while a difference remains under investigation. Conversely, finding a physical explanation does not establish that a required record correction successfully posted.
Reuse normal transfer records and add a compact exception record where needed: transfer and shipment references, item and unit, source and destination, compared quantities and evidence times, actual held-stock location if any, receipt and posting references, unresolved question, owner and next check.
An original handover conversation could be:
For [transfer/shipment], the source evidence establishes [dispatched quantity and unit]. The destination physically verified [quantity] and approved [quantity] under [receipt reference], with [posting result]. [Requested remainder] is separate from [unmatched dispatched difference]. We checked [both-end evidence]. [Named owner] will resolve [question] at [next check].
An owner and next check make an open difference accountable; they do not make it resolved. Close the physical follow-up when its explanation or disposition is supported, and verify any required authorized correction separately.
The manager's next step is to choose one unresolved transfer and ask both locations to explain the same shipment. Match the evidence, verify the record actions and leave unsupported conclusions open with a clear next action.