> For the complete documentation index, see [llms.txt](https://support.ordereazi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.ordereazi.com/sales-features/branches.md). # Branches *** ### 🏢 What is a Branch? A Branch is a named organisational unit within your OrderEazi account. Each branch represents a distinct part of your business - whether that's a physical location, a regional office, a sales division, or an internal department. Each branch has: * A name and optional short code * Its own currency * Shipping and postal addresses * An optional branch manager * A defined set of users * Linked warehouses * Optional product cost price overrides Branches are managed and configured centrally, but they operate independently when it comes to stock, pricing, and order fulfilment. *** ### ⚙️ How Branches Work When branches are active in your account, users are assigned as members of one or more branches. A user's branch membership determines which data they can see and interact with across the system. **User membership:** * A user assigned to a branch is a branch member - their view of clients, projects, and warehouses is scoped to that branch * A user with no branch assignments is a main-branch user - they can see all data across every branch * Branch visibility access can also be granted separately, allowing a user to view another branch's data without being a full member **Warehouses:** Each branch can be linked to one or more warehouses. This controls which stock locations are available when creating orders or projects through that branch. A warehouse can be shared across multiple branches. **Branch manager:** You can nominate a branch manager for each branch. The manager is a user record associated with the branch for reporting and assignment purposes. A branch manager must be an active user, and disabling a user who manages a branch requires that assignment to be updated first. **Display labels:** The word "Branch" is configurable. If your business uses a different term - such as "Division", "Region", or "Office" - you can update the display label in settings. This change flows through to all menus, headings, and messages in the system. *** ### 🔗 Branches and Orders When your account has the **Use Branch on Orders** setting enabled, a branch selector is shown when creating or editing a project. This allows you to tag each project to a specific branch, which in turn determines which warehouses and unit cost for the branch will be available. This setting is separate from inter-branch workflows. When a branch is assigned to a project directly, it acts as a filter and grouping mechanism - not as a trading party. *** ### 🔄 Inter-Branch Workflows The inter-branch workflow enables one branch to sell goods to another branch within the same organisation. This is used when internal stock transfers or cross-branch fulfilment need to be tracked as formal transactions. When a workflow is configured as an inter-branch flow: * The client selector on a project switches from your external client list to your branch list * You select a **From Branch** (the selling branch) and a **To Branch** (the receiving branch) * The To Branch's address and currency populate the project's delivery and billing fields automatically * Pricing is calculated using the From Branch's configured profit settings **Profit calculation on inter-branch orders:** The From Branch can be configured with a profit calculation mode and percentage. Two modes are available: * **Margin** - Selling price is calculated as: Cost / (1 - Profit %) * **Markup** - Selling price is calculated as: Cost x (1 + Profit %) This is applied automatically when a line is added to an inter-branch project. You can still override the selling price on any individual line if needed. **Cost price overrides:** Each branch can have product-level cost price overrides configured. When an inter-branch project is created from that branch, the override cost is used instead of the standard supplier or warehouse cost. This lets you set internal transfer prices per branch without affecting your main pricing structure. *** ### 🔒 Managing Branches Branches are created and managed in **Settings > Branches**. From here you can: * Create new branches with name, code, currency, addresses, and a branch manager * Edit existing branches including their linked warehouses and cost price overrides * Assign users to branches * Disable branches that are no longer in use Disabling a branch is a soft action - the branch record is retained and its historical data is preserved. You cannot disable a branch that still has active projects or sales channels referencing it. **API management:** Branches and their associated data can also be managed via the OrderEazi API. The API supports: * Batch creation and update of branches * Adding and removing users from branches * Linking and unlinking warehouses * Setting product cost price overrides per branch * Controlling which branches an API key has access to > Speak to your OrderEazi representative if you'd like to configure branches or inter-branch workflows for your account. *** ### 💡 Why Use Branches? Branches are particularly useful for: * **Multi-location businesses** - Manage separate stock, warehouses, and teams per physical site without running multiple accounts * **Regional divisions** - Segment your sales, costs, and performance reporting by division or territory * **Internal transfers** - Use inter-branch workflows to formally record stock movements and internal sales between parts of your business * **Scoped user access** - Limit what each user sees to only the branch they work in, keeping large teams focused on relevant data * **Per-branch pricing** - Set internal transfer prices at the product level for each branch, independent of your external pricing structures * **Branch-specific fulfilment** - Link each branch to its own warehouses so orders are fulfilled from the right location automatically * **Consistent terminology** - Rename "Branch" to match the language your business already uses internally *** ### ✅ Summary Branches give you a structured way to divide your organisation and manage each part independently. With branches you can: * Assign users, warehouses, and addresses to distinct parts of your business * Scope order creation and fulfilment to the correct branch automatically * Run inter-branch sales with automatic cost and profit calculation * Manage all branch configuration via the UI or the API This feature is designed for growing businesses where a single flat structure is no longer sufficient, without requiring the complexity of running separate accounts. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://support.ordereazi.com/sales-features/branches.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.