Branch transfers in the POS
Overview
Branches are separate geographic locations where stocks are stored. When goods are sent to your branch from another branch - perhaps from a warehouse - they can be received into stock from the POS.
You can also send stocks back to the warehouse by creating a Branch Transfer in the opposite direction.
Receiving branch transfers
You can receive goods from a branch transfer using the POS. Unlike the backend, the Branch Transfers section of the POS only allows you to see the transfers created or to be received by the branch you are logged in to.
Click on the menu icon, top left, and from the Transfers section click List Transfers.
Find the Branch Transfer that is to be received.
Click on the transaction reference to edit the order.
Add a Completed/Received date. This moves the stock out of holding and into your branch.
Click Save Back to List.
Create a branch transfer
If you wish to transfer products from your store to another branch, you must create a new branch transfer.
Click on the menu icon, top left, from the Transfers section click New Transfer.
Click New Inventory Branch Transfers.
In the Branch field, top left, type in the originating branch from which the stock is being transferred.
Select the receiving branch to which you are transferring stock by selecting from the branch dropdown.
Enter the products to be transferred in the product grid below.
Enter an Approval date if appropriate, then enter a Dispatched Date which will move the stock out of the branch and into holding.
Once complete, Click Approve to finalize the transfer.
FAQs
Can you scan items into a branch transfer?
At this stage, it is not possible to scan items into a branch transfer.
- Notifications.4.log-571783901.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB