HOW-TO · OMNICHANNEL POS

How to transfer stock between store and warehouse

A stock transfer looks simple until the same SKU is also visible in POS, Shopify, marketplaces and a warehouse queue. This guide shows how to move inventory between a retail store and warehouse without creating oversells, phantom stock or unclear transfer ownership, using ChannelDock's stock transfer, POS system and real-time stock workflows.

Request
create the transfer
Reserve
protect online stock
Receive
scan and reconcile
Transfer orderPOS + warehouse
SourceCentral warehousereserved
Transit12 unitsnot sellable
DestinationStore Amsterdamscan receive
request → pick → transit → receive

Most competitor guides explain where to click to create a transfer. The operational gap is what happens while stock is in motion: is it sellable online, reserved for the store, blocked for marketplaces, or already part of a warehouse pick wave?

5 statesrequested, picked, in transit, received, reconciled
2 locationssource and destination both need stock rules
0 guessingvariance must be scanned and explained
1 truthPOS, ecommerce and warehouse share availability

Before you start: stock transfer prerequisites

Treat every warehouse-to-store transfer as a stock state change, not as a manual correction. The goal is to keep cashiers, pickers, ecommerce checkout and marketplace listings working from the same available quantity.

Clean SKUs and barcodes

Every item in the transfer needs the same SKU, barcode and variant mapping in POS, ecommerce, PIM and warehouse workflows. Mismatched size or colour variants are the fastest way to receive the right product into the wrong stock record.

Defined source and destination

Decide whether the source is a central warehouse, another store, a 3PL or a temporary stock zone. Decide whether the destination can sell at the POS, fulfill online orders, support click and collect, or stay hidden until launch day.

A transfer owner

Assign one person or team to approve, pick, dispatch, receive and close the transfer. Without ownership, staff often fix shortages with manual stock edits that never explain where the inventory actually went.

Research gap: Shopify, Square and Lightspeed all document stock transfers or multi-location inventory, but seller forum pain usually starts one layer deeper: stock is counted twice while in transit, online channels keep selling units meant for a store, or received quantities differ from what the warehouse shipped.

Step-by-step: transfer stock from warehouse to store

Use this workflow when a POS location needs replenishment but the same SKUs are also promised to webshops, marketplaces, B2B buyers or warehouse pick tasks.

Create a transfer request, not a stock correction

Start with a transfer order that names the source, destination, SKU list, quantities, reason and required date. A stock correction changes a number; a transfer order explains why inventory is moving and who is responsible.

Common mistake: reducing warehouse stock and increasing store stock manually before the goods are physically picked.

Check available-to-transfer stock

Calculate transferable stock as on-hand minus committed orders, reserved pickup units, damaged stock, marketplace buffers and open warehouse tasks. If a unit is already promised online, it should not be sent to the store.

Common mistake: using on-hand stock instead of available stock, so the transfer steals inventory from an order that has not been picked yet.

Reserve or block stock while the transfer is open

Once the transfer is approved, remove those units from channel-facing availability or mark them as reserved for the destination. The stock is no longer safely sellable from the source, but it should not yet appear as available at the store.

Common mistake: making in-transit stock available online because it exists physically somewhere in the business.

Pick and scan the transfer at the source

Warehouse staff should scan each SKU, barcode or carton before dispatch. Scanning creates an audit trail and catches wrong variants before the box leaves the warehouse. Use pick and pack discipline for high-volume replenishment waves.

Common mistake: letting staff print a list, pick loosely and only discover the missing item when the store receives the shipment.

Move stock into an in-transit state

After dispatch, the transfer should sit in an in-transit state. That state is visible to operations but excluded from normal ecommerce availability unless you have a deliberate pre-sell rule.

Common mistake: treating dispatched stock as already received, which lets the POS sell units before they are on the shelf.

Receive at the POS location

At the store, scan the incoming items and confirm the actual received quantity. If the shipment is short, damaged or split across multiple boxes, record the variance instead of editing the destination stock silently.

Common mistake: receiving the full transfer because the paperwork says it shipped, even though one carton is still with the carrier.

Release sellable stock by channel

After receipt, decide what becomes POS sellable, click-and-collect stock, ecommerce fulfillment stock or display-only stock. ChannelDock stock-level sync can then publish safe availability back to connected channels.

Common mistake: exposing every received unit to marketplaces even when store staff need a display buffer or pickup reserve.

Reconcile exceptions within 24 hours

Close the loop by reviewing partial receipts, damaged items, missing cartons, late transfers and manual edits. The transfer should end with a clear status: completed, partially received, cancelled or investigated.

Common mistake: leaving open transfers unresolved until the next stock count reveals a mystery variance.

The operating rule: in-transit is not sellable by default

A transfer has two inventory truths at once: the source can no longer rely on the units, and the destination cannot sell them until they are received. The safest model separates on-hand, reserved, in-transit and available-to-sell stock.

If a transfer changes two location totals without an in-transit state, your team loses the only moment where mistakes are easiest to catch.

Request
Pick
Transit
Receive
Available to sell = on hand − committed − reserved − in transit − safety buffer

Common stock transfer pitfalls

  • Publishing transferred units online before the receiving store has scanned them.
  • Approving transfers from warehouse stock that is already reserved for marketplace or webshop orders.
  • Letting store staff receive the full quantity without recording shortages, damage or split shipments.
  • Using stock corrections instead of transfer orders, which removes the audit trail.
  • Forgetting display stock, safety stock and click-and-collect reservations at the destination.
  • Leaving transfer requests open so teams cannot tell whether stock is missing or simply still moving.

Manual transfer tracking vs. ChannelDock stock transfers

A spreadsheet can list what should move. An operational transfer workflow protects availability while the stock is moving and gives every team the same transfer status.

Without ChannelDock

  • Warehouse and store teams update stock totals in separate tools.
  • In-transit goods are either invisible or accidentally counted twice.
  • Ecommerce keeps selling units that are being moved to a retail location.
  • Short shipments become manual corrections with no clear cause.

With ChannelDock

  • Stock transfers connect source, destination, SKU, quantity and status in one workflow.
  • POS, webshop, B2B and marketplace availability can exclude reserved and in-transit units.
  • Barcode scanning confirms what was picked and what was received.
  • Variance handling keeps stock history explainable for operations and finance.

Explore ChannelDock stock transfers →

Stock transfer between POS and warehouse FAQ

Create a transfer order, confirm available-to-transfer stock, reserve the units, pick and scan at the warehouse, move them to in transit, receive them at the store and reconcile any variance before releasing stock to sales channels.

Usually no. In-transit stock should be visible to operations but excluded from normal channel availability until the destination receives it. Only expose it online if you have a controlled pre-sell or future-availability rule.

A transfer records movement from one location to another. A correction changes a stock number to fix a count. Use transfers for planned movement and corrections only when the physical stock count is wrong.

Yes, if the transfer workflow updates available-to-sell stock immediately. The key is to remove transfer quantities from source availability before they are sold online or in store.

Receive the actual quantity scanned, mark missing or damaged items as a variance, and keep the transfer open or investigated until the source, carrier or warehouse team explains the difference.

ChannelDock stock transfers manage movement between locations, while POS system and stock-level sync keep in-store sales, warehouse stock and ecommerce availability aligned.

Related POS and inventory guides

Stock transfers work best when POS inventory, click and collect, endless aisle and reservations follow the same availability logic.

POS inventory sync

Connect store and ecommerce stock.

Read how-to

Click and collect

Reserve pickup stock correctly.

Read how-to

Endless aisle

Sell warehouse stock from the store.

Read how-to

Stock transfer feature

Move stock between locations.

View feature

Move store stock without breaking online promises

Use ChannelDock stock transfers to keep POS locations, warehouse teams, ecommerce checkout and marketplaces aligned while inventory is moving.