Multiple Branch Unit Operations

It adds multi-branch (multi-unit) operations under one company: branch masters, user access, navbar/mobile switcher, branch on commercial documents, inventory, accounting, CRM/MRP/POS/Project/HR, PDF branding and branch sequence prefixes.

The technical name is branch_nexgen. Install it from Apps after updating the apps list on Odoo 19.

No. Branches sit under a company. Users without access to a company cannot see its branches. Multi-branch lets several units share one company while keeping records segregated by branch.

A company is Odoo’s legal/accounting entity. A branch is an operating unit inside a company (store, warehouse site, region). One company can have many branches; documents and stock can be tagged by branch without creating extra companies.

Yes. Create several branches per company. Company rules apply first; then branch rules filter within the allowed companies.

Yes — Odoo 19 Community and Enterprise on Odoo.sh and on-premise.

No. Third-party Apps Store modules cannot be installed on Odoo Online. Use Odoo.sh or your own on-premise / hosting server.

No. Create branches, assign users and groups, then operate. Optional technical help is available if you want unused app dependencies trimmed.

Copy the module into your addons path, update the Apps list, then install Multiple Branch Unit Operation Setup for All Applications (technical name branch_nexgen).

Security groups, branch menus, views, record rules and the branch switcher assets are loaded. Create your first branches under Settings → Users & Companies → Branches, then assign them on users.

Go to Settings → Users & Companies → Branches (or the Branches menu provided by the app). Branch managers can create and edit branch masters.

Name, company, address (street, city, state, country, ZIP), phone, logo, and optional sequence prefix settings for document numbering.

Yes. Upload a logo and set the full address and phone. These details are used on PDF reports when the document belongs to that branch.

Branch User (own branch records only), Branch Manager (all branches), and Multi Branches (desktop/mobile branch switcher). Record rules enforce visibility.

A Branch User can access records of the branch(es) they are allowed to use. They cannot manage all branches unless they are also a Branch Manager.

A Branch Manager can view and manage records across branches (subject to company access), and typically maintain the branch master data.

It enables the branch switcher in the navbar (desktop) and the Branches menu in the mobile / burger account menu so users can change their active allowed branches.

Open the user form → Access Rights. Set Allowed Branches and Default Branch (placed after Default Company). Also assign Branch User / Manager / Multi Branches as needed.

Allowed Branches are the units the user may work in. Default Branch is the starting / preferred branch used when creating new documents (and kept in sync with the switcher).

Yes. Add multiple Allowed Branches. With Multi Branches, the user can switch or activate the branches they need from the header or mobile menu.

Yes. Branches are company-specific. The switcher and domains only show branches for companies the user can access.

Users with Multi Branches open the branch menu in the systray/header, see allowed branches (company-filtered), and select the active branch. The user’s default/active branch updates accordingly.

Yes. Open the account / burger menu. Branches appears similarly to Companies so users can select allowed branches on phone or tablet.

No. Switching branch affects the user context for new work and filtering. Existing documents keep the branch already stored on them unless you edit those records.

Contacts, products, sales, purchase, pickings, scraps, invoices/bills, payments, bank statements, journals/items, warehouses, locations, quants, valuation, CRM, manufacturing, POS, projects/tasks and employees.

Yes. Views place branch_id immediately after company_id, and Branch visibility follows Company visibility (groups, optional, invisible / column_invisible).

The login user’s branch is set by default. Warehouse can follow the selected branch. Confirming the order propagates branch to delivery and customer invoice.

The login user’s branch is set by default. Confirming the RFQ/PO propagates branch to the incoming shipment and vendor bill.

Yes. Pickings created from sales or purchase inherit the parent document’s branch.

Yes. Invoices/bills created from SO/PO inherit the order branch. Manual invoices use the login user’s branch.

Yes. Journal items follow the accounting move’s branch.

Yes. Payments inherit from related invoices/moves when available. Bank statements and statement lines can also carry branch.

Yes. You can set a branch on account journals so accounting documents align with the unit.

Yes. Set Branch on the partner (Sales & Purchases / company area). Visibility follows the Company field rules.

Yes. Set Branch on the product template; variants inherit. Product lists can show Branch after Company.

Yes. Define branch on warehouses and stock locations so inventory ownership stays clear per unit.

Yes. Valuation, scraps and quants support branch so stock value and adjustments can be analyzed by unit.

Yes. Leads and opportunities include Branch, with Group By Branch in search views.

Yes. Manufacturing orders carry Branch; related moves and MO reports can follow the production branch.

Yes. Set Branch on the POS config; sessions and orders inherit. Lists can show company then branch.

Yes. Projects and tasks include Branch for unit-level delivery tracking.

Yes. Employees can be linked to a branch on the Work information page (after Company).

Enable Apply Branch Sequence Prefix on the branch and set a short code (e.g. AMD). Document numbers use that prefix (e.g. AMD-S00025). Sequences are created lazily per branch and document type.

Sales, purchase, pickings, invoices/bills, payments and related flows that use branch-aware sequences. The same prefix helps identify the unit on PDFs.

Documents still store Branch. Numbering continues with standard Odoo sequences without the branch code prefix.

Yes. When a document has a branch, layouts can print branch logo and address. Footer can show Branch: Name and Phone.

Sales, purchase, picking/delivery, invoice/bill, payment and manufacturing reports that use the shared report layouts.

Yes. Sales analysis includes Branch so you can pivot/graph performance by unit.

Yes. Purchase analysis includes Branch for spend and vendor activity by unit.

Yes. Group By Branch is available on sales, purchase, invoices, pickings, payments, statements and other supported models.

Yes. Account invoice report supports Group By Branch for revenue analysis by unit.

Yes. They keep their Default / Allowed Branches and create documents for those branches. They simply will not see the switcher UI.

They should be assigned at least one Allowed Branch and a Default Branch. Without that, new documents may not get a meaningful branch context.

Yes. Branch field visibility is aligned with Company (multi-company group, optional show/hide, invisible / column_invisible where applicable).

Yes. The package targets a full business stack (Sales, Purchase, Inventory, Accounting, plus CRM, MRP, POS, Project, HR). Contact support if you need unused dependencies removed.

Propagation keeps related documents aligned with the parent order’s branch. Prefer setting the correct branch on the source document before confirmation.

The switcher and multi-branch groups are designed for internal users. Portal users are not the primary audience for branch switching.

This is a NexGen Odoo 19 module. Migration from third-party branch apps depends on your database; contact support for a migration plan if needed.

The module follows Odoo’s translation system for menus, fields and messages. Additional languages can be added on request.

OPL-1 (Odoo Proprietary License v1.0). Purchase grants usage rights per the Apps Store terms.

Yes. Starting from common Apps Store practice, each major version is sold separately. This listing is for Odoo 19.

90 days free support for bugs or issues with the module (excluding data recovery / custom development). Email nexgensolutionsodoo@gmail.com.

Write to nexgensolutionsodoo@gmail.com with your Odoo version, database type (Community/Enterprise), and steps to reproduce.

Confirm Odoo 19, correct addons path, Apps list updated, dependencies installed, and your user has Branch groups. Then contact support with logs/screenshots.

Yes — if you do not use a specific application, contact NexGen Solutions and we can guide removal of unused dependencies where feasible.

Branch tags documents inside a company for operational control and reporting. Legal consolidation remains at company level; use Branch in analysis for unit KPIs.

No. Each branch belongs to one company. Create separate branch records per company even if names are similar.

Contact nexgensolutionsodoo@gmail.com for a demo walkthrough of multi-branch setup and document flows.

NexGen Solutions — website nexgensolutions.odoo.com, support nexgensolutionsodoo@gmail.com.