How to Track Shopify Inventory Transfer Shipments

Create the transfer for a real inventory movement between named origin and destination locations or between a location and an external source. Record the operational reason, transfer reference, owner, expected arrival, and planned quantities by variant. Shopify uses transfers to track stock as it moves and supports full or partial receiving. Keep the transfer as the inventory system's owner instead of using a spreadsheet as a second source of truth.

Review available and committed quantities at the origin before the move is approved. Confirm that the destination, units, and packaging plan match the physical work. If several cartons or dispatch dates are needed, keep them inside one transfer only when they share the same approved movement. Separate unrelated replenishment decisions so one delayed shipment does not hide the state of another location's stock.

Shopify creates and manages shipments as a transfer is processed. Use the shipment record to represent the cartons or batches that physically leave the origin. Add only the item quantities assigned to that shipment, then record the carrier, tracking number, and expected arrival when known. If the transfer moves in separate batches, create or manage multiple shipments so each physical handoff has its own state and evidence.

Do not mark the entire transfer in transit because one carton received a carrier label. Confirm the item list, quantities, packaging count, and first carrier acceptance for each shipment. Preserve the packing document or scan reference without copying customer information into the transfer. A shipment is the bridge between Shopify's planned movement and the carrier's physical evidence, so identifiers must match on both sides.

Use draft while the movement is still being prepared, ready to ship when the transfer is approved for dispatch, and in progress when physical movement has begun. Shopify lists transferred and canceled as other transfer outcomes. Define the internal event that authorizes each change, such as packing completion, carrier acceptance, destination count, or cancellation approval. A status should describe what happened, not what the team hopes will happen next.

Record status time, actor, and evidence reference in the transfer timeline or operating ledger. If a third-party app created the transfer, Shopify identifies its source and places it in ready-to-ship status. Verify that the app's quantity and location logic match the physical plan before staff act. Do not assume the third-party source has already confirmed a carrier handoff.

Shopify allows edits to draft or in-transit shipments, including quantities, products, tracking number, carrier, and expected arrival. Use that capability to correct the operating record when the physical shipment changes. If quantities move between shipments on the same transfer, document why and verify both resulting item lists. Shopify notes that an empty shipment can be deleted automatically after its items move elsewhere.

Do not rewrite history to conceal a packing error or missed dispatch. Preserve the original plan in the transfer reference or exception log, then make the supported edit that matches reality. If a received shipment has the wrong quantity, use the receiving workflow instead of changing the planned shipment as if the original handoff never occurred. Planned, shipped, received, accepted, and rejected quantities answer different questions.

At the destination, identify the transfer and shipment from the carrier label or packing record before counting. Count units by variant and classify the result before updating Shopify. Receive only the quantities physically present and accepted. Keep missing units outstanding, and record rejected or damaged units according to the supported receiving options and the company's inventory policy. A carrier delivery scan does not replace an item-level receiving count.

For a partial receipt, leave the remaining shipment quantities unresolved until another package arrives or an exception owner decides the disposition. Capture photos or damage evidence only in the approved private system. Do not place private warehouse images or supplier details in public content. The Shopify transfer should show what the destination accepted, while the exception record explains why any planned quantity did not become available stock.

Compare Shopify's transfer and shipment quantities with carrier tracking and the destination's physical count. Each layer can disagree for a different reason. Shopify can contain an entry error, the carrier can miss or delay a scan, and receiving can count the wrong variant or carton. Use the transfer ID, shipment tracking, variant SKU, and event times to align the records before creating an inventory adjustment.

Classify exceptions as not shipped, in transit, delivered not received, received short, received damaged, rejected, misrouted, or data-entry error. Assign one owner and next check time. Avoid closing a transfer by forcing the numbers to match. An unexplained adjustment may make available inventory look correct while erasing the operational cause that needs prevention.

Close the transfer only when every planned unit is received, rejected, canceled, or otherwise resolved with evidence. If the movement no longer needs to happen, Shopify permits cancellation while a transfer is in draft or ready-to-ship status. Shopify states that canceling returns committed items to available inventory at the origin. Confirm that no physical package has left before using cancellation as the remedy.

Retain the transfer reference, final quantities, last tracking state, receiving evidence, exceptions, adjustments, owner, and completion time. Review recurring delays or discrepancies by origin, destination, carrier, and process step. Do not treat one transfer as proof of a systematic cause. Use repeated, verified patterns to decide whether packaging, scanning, carrier handoff, or receiving controls need to change.