🏢 Branch Management

In the Branch Management page you define the list of stores/branches you work with, link them to the warehouse/store code in the ERP, and add/edit/delete branches. The branch list here affects all other pages in the system (store selection at the top of management pages, summary exports, locations, etc.).

🏁 How to Access

• On phone: ☰ at the top right → Branches.
• On computer: Hover over the menu on the left → Branches.

🧠 What the Page Does

• Displays a table of all stores/branches in the account.
• Allows: adding a new branch, bulk importing branches, editing branch details, and deleting a branch (carefully).
• For each branch you can save a store/warehouse code – this is the identifier by which your ERP recognizes the branch (used in summary exports).

💡 Why is "Store/Warehouse Code" important? This is the ERP matching key. When exporting a count summary, the system inserts this code into the relevant column, so the ERP import knows to associate the data with the correct store/warehouse.

✨ Top Area – Main Actions

• ➕ Add New Branch (green button): Enter branch name (required) and store/warehouse code (highly recommended). Saving adds a row to the table.
• 📥 Import Branches (gray button): For quick setup/update of a large list.
  • If you have an ERP integration with branch import support – a live import (direct pull from external system) will be offered.

🗂️ The Table – Fields and Actions

Common columns:

• Branch Name – e.g. "Main Branch", "Tel Aviv Branch".
• Store/Warehouse Code – the precise ERP code (if not entered, "Not entered" will appear).
• 🎯 Count Goals – opens the Count Goals management dialog for this branch (create, edit, delete, bulk create). See full details on the 🎯 Count Scope Management page.
• Edit Data – ✏️ change name and code.
• Delete Branch Actions – 🗑️ careful deletion.

Edit (✏️)

• Changing name/code saves immediately and affects future summary exports.
• Recommended to align the code here to the exact ERP identifier (including leading zeros if present).

Delete (🗑️)

• In most accounts, deletion is only allowed if there is no count data/locations/users associated with the branch.
• If there is history – clean/transfer the data first or contact support.
• It is always better to correct the name/code than to delete a branch with history.

🧭 Impact on the Rest of the System

• Store selection at the top of management pages (Overview, Recent Counts, Locations, Catalog/ERP balances by store) relies on this list.
• In count summary exports, the store/warehouse code will appear – therefore it's important for it to be precise.

🔐 Permissions and Store Access

Not every user has access to every store. Store permissions are set at the user level (detailed on the User Management page). The practical meaning:

• In store selection dropdowns, only stores assigned to the user will be shown.
• Views, summary exports and management actions will apply only to stores the user has permission for.
• System admins can assign/remove access to specific stores for each user.

💡 Tip: Before starting a count in a new store, verify that all relevant counters have permission for that store – otherwise they won't see it in the selector.

✅ Best Practices

• Coordinate names/codes with the ERP before starting a count.
• Consistent coding: If the ERP requires leading zeros (e.g. "002"), save it exactly like that.
• Periodic import: If there are many branches – perform periodic imports to avoid manual typing.
• Don't delete a branch with history – it damages audit integrity. Better to leave it and mark "not in use" in internal notes or in the name.

Summary

Branch Management is the organizational layer of OpticCount: here you define the "organization map" vs. the ERP. Maintaining a clear name and precise code ensures that summary exports are imported smoothly, that store filtering works correctly, and that the entire counting process is organized and fast.