Companies and branches solve different problems
A company in an ERP commonly represents a legal or accounting entity with its own business details, ledgers and financial records. A branch is usually an operational location or business unit working within an approved company structure. These definitions affect invoice identity, tax configuration, stock ownership and management reporting. Putting every new store into a new legal company can make ordinary inventory transfers and consolidated operational review unnecessarily difficult.
Plan accounting and stock boundaries
List each legal entity, GST registration, warehouse and physical branch. Decide which documents need company-level numbering and which must show the active branch. When stock moves between warehouses, record its physical origin and destination; when it moves between legal entities, a different commercial process may be needed. Do not assume a branch transfer has the same tax or accounting treatment as a company-to-company supply.
Give staff only the access they need
A cashier should normally work with the correct selling company and permitted branch. An accounts user may need broader access, while a manager might require cross-location reports without permission to change financial configuration. Test switching companies, creating invoices, running reports and downloading documents using realistic sample user accounts. Permission design matters as much as the menu layout.
Scale without confusing daily operators
Use short, recognisable company and branch labels in the interface. Establish who creates new entities, users and warehouses, and review the limits attached to the chosen subscription. XlinkONE includes a company switcher and branch-oriented workflows, with availability and allowances depending on configuration. Start by mapping legal and operational boundaries; clean structure now prevents difficult corrections later. Keep the organisation chart updated when staff transfer between business locations.