Deciding whether to create a new branch or a new department depends on how much administrative separation you need. Tradogram operates at a branch level, meaning branches act as distinct divisions, while departments serve to group users for reporting, budgeting, and workflow purposes.

The Hierarchy Structure

Tradogram follows a tiered structure: One Company → Multiple Branches → Multiple Departments.

When to Create a New Branch

A branch is best for entities that require their own operational settings and identity. While often used for physical locations, they can represent separate business units that need independent control.

Key Branch-Level Features:

• Independent Settings: Each branch has its own PO numbering system, operational settings, and default Terms & Conditions.
• Approval Rules: Approval workflows are unique to the branch; what works for one location won't automatically apply to another.
• Security & Access: Users in one branch typically have limited or no interaction with documents in other branches.
• Logistics: Each branch maintains its own billing address and multiple delivery/distribution addresses.

When to Create a New Department

Departments are best used to organize users within a branch for budgeting, reporting, and specific approval triggers.

Key Department-Level Features:

• Dedicated Roles: You can assign a Department Manager (notified when requisitions are created) and an Assigned Purchaser (notified when requisitions are ready for PO creation).
• Spend Controls: You can restrict a department to a specific list of GL Accounts or Item Categories to ensure users only buy what is relevant to their role.
• Approval Filtering: Departments can be used as a filter in your branch's approval rules (e.g., "If the department is Marketing, route to the CMO").

‍