> For the complete documentation index, see [llms.txt](https://support.ordereazi.com/central/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/central/order-management/settings/organization-setup/system-settings/branch-options.md).

# Branch options

Rename branches to suit your business, and choose how branches are set on projects.

Not every business calls its divisions "branches". The **Branches** settings in System Settings let you use your own word, such as "Store" or "Division". They also decide whether each project is linked to a branch, so its costs and reports follow that branch.

### Before you start

You'll need the **Organization Setup** permission, in the **Settings** permission group. Your branches are set up in [Branch Setup](/central/order-management/settings/branch-setup.md).

### How to change your branch options

1. In the main menu, go to **Settings** > **Organization Setup**.
2. Select the **Configuration** tab.
3. Under **Branches**, change the settings you need.
4. Select **Save**.

You see "System Settings saved successfully".

### The settings

| Setting                          | What it does                                                                                                                                                          |
| -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Branch Label (Singular)**      | The word used for one branch everywhere in OrderEazi, such as "Store". Up to 32 characters. Leave it blank for "Branch".                                              |
| **Branch Label (Plural)**        | The word used for more than one, such as "Stores". Leave it blank for "Branches".                                                                                     |
| **Use Branch on Orders**         | Adds a branch dropdown to projects, so the rep's branch can be chosen. It isn't shown on inter-branch workflows, which already have a from and to branch.             |
| **Branch Required for Products** | Product search on a project stays locked until the project has a branch. A branch taken from the project's sales channel counts.                                      |
| **Fallback Unit Costs**          | A product with no cost for the project's branch uses its standard supplier cost. When it's off, those lines start at zero until a branch cost applies. On by default. |
| **Filter Branches By**           | Which branches can be chosen on a project: those of the **Sales Rep**, those of the client's **Account Manager**, or those matching the **Client Country**.           |

**Branch Required for Products**, **Fallback Unit Costs**, and **Filter Branches By** only show once **Use Branch on Orders** is ticked.

### How the branch is chosen on a project

**Filter Branches By** narrows the branches to the ones that apply. If exactly one branch applies, it's chosen and locked on its own. If more than one applies, the rep chooses. If none applies, every active branch can be chosen.

**Example:** You run three stores, and set **Branch Label (Singular)** to "Store". You tick **Use Branch on Orders** and filter by **Sales Rep**. Lerato works only at the Durban store, so her projects get "Durban" at once and she can't change it. Johan works at Durban and Pinetown, so he chooses the store on each project.

### Related pages

* [System Settings](/central/order-management/settings/organization-setup/system-settings.md): the other settings groups
* [Branch Setup](/central/order-management/settings/branch-setup.md): set up branches, their users, and their prices