Warehouse Stock Transfer SOP
A warehouse stock transfer SOP exists because informal moves break the ledger. Someone loads ten cartons onto Van 2 “because the job needs them”. Main DC on-hand still shows the ten. Van 2 sells from memory. By Friday, Stock counts invent a mystery variance and nobody remembers which Tuesday the van left.
This SOP covers Transfers in VORQ from create through shipped, in-transit, received, and partial receipts. Pair it with the product walkthrough for Transfers and the planning view in how to track stock across multiple warehouses.
Purpose and scope
Purpose: move quantity from one Storage site to another with a single auditable trail, so pickable on-hand never double-counts and never silently disappears.
In scope: Main DC to satellite sites, site to van, van to site, and warehouse to warehouse moves of labelled stock.
Out of scope: supplier inbound (that is Purchase orders and Receive stock), customer dispatch (Scan to deduct), and cycle adjustments (Stock counts).
Roles
- Requester: names SKU, quantity, from-site, to-site, and why (job, Low stock on destination, balancing).
- Shipper: picks and confirms the outbound quantity at the source Storage site.
- Receiver: counts and books what arrived at the destination, including short receipts.
- Supervisor: resolves partials, damaged units, and transfers left in transit too long.
Status language (use these words on the floor)
| Status | Meaning | On-hand effect |
|---|---|---|
| Draft / open | Transfer created, not yet shipped | Source still holds stock |
| Shipped | Source confirmed dispatch of the transfer | Quantity leaves source on-hand |
| In transit | Goods are between sites | Neither site should treat it as pickable local stock |
| Received | Destination booked the full remaining quantity | Destination on-hand increases |
| Partial receive | Destination booked some, not all | Received portion lands; remainder stays outstanding / in transit |
Do not invent a parallel status on WhatsApp. If the system says in transit, planners must treat it as in transit.
SOP: create and ship
- Confirm destination need. Check destination on-hand and any open incoming Purchase orders so you do not transfer stock that is already arriving there.
- Create a Transfer: from Storage site, to Storage site, SKU, quantity. Example: Main DC → Van 2, FLR-120 × 10.
- At source, pick only labelled stock. Prefer the batch you intend to move; if the destination must burn a specific lot later, align with dispatch from a specific batch habits.
- Ship the Transfer. Quantity leaves Main DC on-hand and enters in transit.
- Load the vehicle. Physical cartons must match the shipped quantity. If you can only load 8, do not ship 10 in the system.
- Notify the receiver with Transfer id (TR-118) and ETA. Short message, not a spreadsheet rewrite.
SOP: receive and partial receive
- At destination, open the in-transit Transfer before unloading guesses begin.
- Count what is on the vehicle. Damaged cartons are not “received as good stock”.
- Full receive: if 10 of 10 arrived sound, receive 10. Van 2 on-hand rises by 10. Transfer completes.
- Partial receive: if 8 arrived sound and 2 are missing or crushed, receive 8. Record a note (“2 cartons missing on TR-118”). Outstanding 2 stay visible for the supervisor.
- Put away or stage received units on the destination Storage site so Scan to deduct can find them.
- Escalate shortfalls the same day. Do not leave Transfers in transit for a week as a parking lot for unresolved theft, damage, or admin error.
Partial receive on Transfers mirrors partial Purchase order receipts: book truth, leave the remainder open, never inflate the receive to “close the line”.
Worked example: TR-118 Main DC → Van 2
| Step | Event | Main DC on-hand | In transit | Van 2 on-hand |
|---|---|---|---|---|
| 0 | Before transfer | 55 | 0 | 25 |
| 1 | Ship 10 on TR-118 | 45 | 10 | 25 |
| 2 | Partial receive 8 on Van 2 | 45 | 2 | 33 |
| 3 | Supervisor writes off or recovers the 2 | 45 | 0 | 33 (or +2 if recovered) |
At step 2, nobody at Main DC should promise the in-transit 2 as local stock. Nobody at Van 2 should promise 35 when only 33 are booked.
Rules that keep the SOP boring
- No stock rides without a Transfer id.
- Ship quantity equals physical load quantity.
- Receive quantity equals physical sound quantity.
- Partials are allowed; silent closes are not.
- In-transit older than your SLA (for example 48 hours for local vans) triggers a supervisor review.
- Transfers are not a substitute for Purchase orders. Buying from a supplier still uses POs to the right destination site.
Failure modes and fixes
- Shipped in system, never loaded: reverse or correct before the van leaves sight. Otherwise destination will partial-receive zero forever.
- Loaded without ship: source still shows stock; destination may receive into the wrong process. Stop and ship properly.
- Receive without count: you import the source’s hope into the destination’s ledger. Count first.
- Using Transfer to hide damage: damaged units need a clear disposition, not a permanent in-transit ghost.
Checklist (print beside the dock)
- Transfer created with correct from/to Storage sites
- Source pick matches labels and quantity
- Ship confirmed; source on-hand dropped
- Vehicle load matches shipped quantity
- Destination count completed before receive
- Full or partial receive posted the same day
- Outstanding quantity escalated if not zero
- Destination stock put away and available for Scan to deduct
Follow this warehouse stock transfer SOP and multi-site stock stops being a rumour. For the system screens behind each step, stay with Transfers. When you are ready to run Main DC and Van 2 on one ledger, use signup or review pricing.
