Why a transfer is a record, not an edit
Stock is held per shop. When goods move from one branch to another, both shops' figures have to change together — one down, one up, by the same amount.
Doing that as two manual adjustments means two chances to mistype, and no link between them. Recorded as a transfer, the movement is one event with a trail: what moved, when, between which shops, and who did it.
Recording one
Choose the source shop, the destination, and the items with quantities. The stock leaves the source and arrives at the destination.
Record it when the goods actually move, not when somebody remembers. In between, the source shop thinks it still has stock it cannot sell and the destination cannot sell stock it already has on the shelf.
Checking it worked
Look at the stock figure in both shops afterwards. If only one changed, the transfer did not complete.
When the shelf and the system disagree
If a branch is persistently short, look first at whether transfers out are being recorded and transfers in are not — an unrecorded arrival looks exactly like shrinkage at the destination and exactly like theft at the source.
When you do correct a figure, record it as an adjustment with a reason. "Stock was wrong" with no reason is how real shrinkage becomes invisible.
The stock chapter of the POS Cloud manual covers purchases, batches and expiry.