Skip to content
Stock & purchasing

Transfers between branches

Send stock to another branch of your business, count it in at the other end, write off anything short in transit, and follow each transfer in the owner portal.

A business with two shops often moves stock between them: the main depot sends school-season stock to the smaller branch, or one branch returns slow titles. In BooksPOS the sending branch sends, BooksPOS Cloud carries the document, and the receiving branch counts it in. Each branch's stock and books stay right while the goods are on the road.

What you need

  • Both branches set up as branches of one business, each paired with BooksPOS Cloud. See Joining a new branch to your business.
  • Both store PCs syncing. A transfer travels only through the cloud; there is no direct link between the shops.

Until another branch has joined and this store has synced, the send window says: "No other branch is known here yet. Branches are listed after this store syncs with BooksPOS Cloud and another branch of the business has joined."

How to send stock

  1. On the sending branch's store PC, open Stock or Transfers and choose Send to branch ("Send stock to another branch of the business").
  2. Choose To branch, and From which place (usually the shop floor).
  3. Add each item (Add an item: title, ISBN or SKU) with its Unit and Qty.
  4. Add a Note, for example school season stock for Cantt.
  5. Choose Send.

"MAIN-BT000002: Rs 38,400.00 sent to CANTT. It reaches the other branch at the next sync with BooksPOS Cloud."

The goods leave the sending branch at once, at their average cost. While they travel, their value sits in an Inter-branch transfers account, so the sender's stock value drops but nothing is lost from its books.

The Send stock to another branch dialog sending 5 copies to Cantt branch (demo)

Sending stock to a branch. Stock leaves at its cost; the other branch receives it at its next sync. Screenshot of the current build (28 Sep 2026), synthetic demo data.

How to count it in at the other branch

  1. At the receiving branch, after its store PC has synced, Transfers in the menu shows how many transfers are waiting as a count beside it, the Dashboard lists them under Needs attention, and the From branches button on Stock shows the same count, for example From branches (1).
  2. On Transfers, choose Count in from branches (or open the waiting transfer and choose Count in). The Transfers between branches window lists what is Arriving, from which branch.
  3. Choose the transfer and count what actually arrived, line by line.
  4. If anything is short, type what happened in Note (needed if anything is short), for example two copies missing from the carton.
  5. Choose Count in.

What arrived goes onto the receiving branch's shop floor at the sending branch's cost. Anything short is written off at the receiving branch as a loss in transit, with the note. You cannot count in more than was sent, and a transfer can be counted in only once.

The receiving branch's count goes back through the cloud, and the sender's window shows it under Sent from here, with Sent, Arrived and Status.

The Transfers page

Transfers (in the menu under Stock) lists every transfer of the branch together: moves between the shop floor and the godown, goods sent to other branches with what arrived there, and goods from other branches, waiting ones first. Each row shows when, the number, where the goods went, the status (Moved, On the way, To count in, Received or Received short), the lines and the value. Choose Every transfer, Between places, Sent to branches, From branches or Waiting to be counted in, or type a number, place or branch, to narrow it.

Choose a transfer to open its own page: where it went, when and by whom, its value, what the other side counted in and anything short, and each line with its quantity, value and what was received. Excel, CSV, PDF and Print save or print the list or a transfer.

Items the other branch does not have

If the receiving branch has no such item yet, counting in adds it there with the sender's details: title, edition, ISBN, publisher, category, unit and prices, and its tax rate, PCT code and Third Schedule setting (a transfer sent by an older version of BooksPOS carries no tax, and the item starts at 0 %). It keeps the same identity, so the next transfer of that title finds the same item. Check its prices at the receiving branch afterwards.

In the owner portal

Branch transfers in BooksPOS Cloud lists every transfer between your branches with when it was sent, from and to which branch, the document, its value and its status, with what was received. "Stock leaves the sending branch when it sends, at its average cost, into an inter-branch account. The receiving branch counts what arrived; anything short is written off there as a loss in transit. The two branches' inter-branch accounts cancel out."

Rules worth knowing

  • Transfers travel at sync time. If either store PC is offline, the transfer waits; nothing is lost.
  • Stock moves in base units (copies or pieces) and lands on the receiving branch's shop floor.
  • A transfer cannot be recalled once sent. If goods went to the wrong branch, count them in there and send them back.
  • Who can send and count in: owners, managers and warehouse staff.
  • Consigned copies cannot be sent: only the shop's own stock.

Common questions

Why can the other branch not see the transfer?

Both store PCs must have synced since it was sent: the sender to deliver it, the receiver to pull it. Check Sync & FBR on both. See Cloud sync problems.

Why does the transfer show at the sender's cost and not the receiver's?

The copies were bought by the sender. Keeping their cost means stock value is right across the business, and the two inter-branch balances cancel out.

What if some copies arrive damaged?

Count them in as arrived, then mark them damaged with Adjust › Mark as damaged at the receiving branch.

Can a branch receive a transfer from a different business?

No. Transfers go only between branches of the same business in BooksPOS Cloud.

Last updated 27 September 2026. Still stuck? Contact us.