Multiple branches
Connect branches through an accepted distribution relationship
Connecting branches helps teams review supported shared distribution workflows. It starts with a request to the intended branch and requires acceptance by the receiving distribution. A pending request does not merge records, and a connection does not turn every account into an administrator of the other branch.
See the current packages and allowances before you choose.
What should both branches agree first?
Agree which branches are connecting, who reviews orders and how delivery work will be handled. Check each branch's identity and account code before sending a request. Keep business currency, stock records and staff responsibilities clear rather than treating two independent record sets as automatically interchangeable.
Test a small set of orders after acceptance before relying on merged views for a full working day. A branch connection should be deliberate and limited to the real business relationship.
How do you connect another distribution?
Use Merge Branches to find the intended distribution by its code and send a merge request. The receiving branch reviews its pending requests and accepts the correct incoming request. Both sides can then check the accepted relationship before using the supported merged workspaces.
Find and verify
Open Add Merge Request, locate the other branch and verify its identity. You cannot request a connection to your own account.
Review the incoming request
The receiving branch checks the requester in Pending Merge Requests. Sending a request alone does not activate access.
Accept and test
After the intended recipient accepts, check Accepted Merge Requests and review a known order in the applicable merged pages.
What should you check in merged order pages?
Check the branch, customer, order status and responsible seller before acting on an order. Use merged unconfirmed and confirmed views according to the enabled permissions and workflow. A shared view should not be mistaken for every branch sharing the same product record, balance or staff permissions.
What happens when a branch relationship ends?
Review accepted connections and remove the relationship when shared work should end. Removing a connection does not delete the branches' customers or orders. Check remaining shared delivery work before removal and confirm the resulting access from both sides.
Your next step
Try the workflow with your own business
Start with a small product list and a trial customer. Check stock, delivery, receiving and any local requirements before a wider rollout.