Before setup, decide what a location represents
First distinguish a bin move inside one working area from a transfer between separately managed locations. Your location design determines who can promise or pick the stock. A shelf label, warehouse, shop and service vehicle may require different handling even when the same product moves between them.
For a transfer, write the source, destination, product, unit, quantity, sender and receiving owner. Add a dispatch reference when goods travel outside the immediate work area. If a transfer has no receiving owner, it is easy for a delivered carton to sit unrecorded while the source team assumes the work is finished.
Count the handoff twice for different reasons
In a fictional transfer, Warehouse A sends 24 filters to Shop B. The sender verifies 24 before dispatch. Shop B counts 23 on arrival and records the shortage as an exception. The second check is not redundant: it establishes what reached the destination.
Keep the disputed unit attached to the transfer while you investigate the dispatch count, packaging and receiving area. Do not quietly add one to Shop B just to match the paperwork. Avoid also re-adding it to Warehouse A without evidence that it stayed there. A transfer discrepancy needs one coordinated resolution, otherwise the same missing unit can be repaired twice.
Verify the actual software transfer workflow
InFlow's standard transfer documentation distinguishes sending from receiving and includes an in-transit state. It notes that the feature depends on selected plans or add-ons. By contrast, its Stockroom integration documentation says Stockroom transfer workflows complete in one step and skip that in-transit stage.
That difference matters if a vehicle spends hours between locations or receiving is done by another shift. Test the workflow that the team will actually use rather than assuming every interface has the same handoff. For a one-step method, decide how an arrival exception will be recorded outside that immediate transaction. Do not describe transit controls as present where they are not.
Make outstanding transfers visible
At shift handover, review sent transfers that have no confirmed arrival. Compare the expected travel time with the dispatch reference and identify which person should investigate. A transfer that remains open may represent delayed transport, missed receiving or an actual shortage; the status alone cannot distinguish them.
For nearby shelves with one custodian, a simpler move record may be sufficient. Separate premises or teams justify stronger checks. After the move, sample the affected SKU at both locations and confirm that neither side includes goods it no longer controls. Your next action is to map one routine transfer from request through receipt, including what happens when the destination receives less than the source sent.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- inFlow: transfer stock between locations — Merchant documentation · inflowinventory.com · Merchant-controlled · checked 2026-09-24
- Current inFlow Stockroom guide — Merchant documentation · inflowinventory.com · Merchant-controlled · checked 2026-09-24