01
Separate legal and operational structure
A company, branch, warehouse and physical location answer different questions. Treating them as interchangeable creates reporting and permission problems later.
Document legal entities, stock ownership, financial responsibility, managers and shared services before configuring the system hierarchy.
02
Design access from responsibilities
Permissions should follow the work a role must perform and the records it must see. Test cross-branch managers, temporary coverage, central purchasing and finance teams explicitly.
Avoid one-off user permissions where role-based groups can express a durable policy.
03
Decide what is shared
Products, price lists, customers, suppliers and employee information may be shared or separated. Each choice affects duplication, reporting and local control.
Use representative transactions to test branch transfers, returns, approvals and consolidated reporting before migration.
04
Plan expansion as a repeatable operation
A new branch should have a documented setup path covering master data, users, warehouses, accounting, devices, training and opening balances. Repeatability turns growth from a special project into an operating capability.