Multi-Branch Management for Odoo
by DevIntelle Consulting Service Pvt.Ltd https://www.devintellecs.com$ 33.76
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
CRM (crm)
• Inventory (stock) • Invoicing (account) • Project (project) • Purchase (purchase) • Sales (sale_management) • Calendar (calendar) • Contacts (contacts) • Discuss (mail) |
| Lines of code | 1230 |
| Technical Name |
dev_branch |
| License | See License tab |
| Website | https://www.devintellecs.com |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
CRM (crm)
• Inventory (stock) • Invoicing (account) • Project (project) • Purchase (purchase) • Sales (sale_management) • Calendar (calendar) • Contacts (contacts) • Discuss (mail) |
| Lines of code | 1230 |
| Technical Name |
dev_branch |
| License | See License tab |
| Website | https://www.devintellecs.com |
| Versions | 17.0 18.0 19.0 |
Branch Management
Branch Management Odoo App lets a single Odoo company operate as several branches — different shops, offices, divisions or regional locations — while keeping each branch's paperwork, stock and visibility separate. Once a branch is set up, you can stamp it on every Sale Order, Purchase Order, Invoice, Payment, Delivery, Receipt, Warehouse, Location, Operation Type, Putaway/Pull Rule, Route, Sales Team, CRM Lead, Customer, Product and Project Task.
Each user gets a Current Branch plus a list of Allowed Branches, and Odoo filters lists, dashboards and search results so people only see what belongs to their branches. The branch carries forward automatically across the paper trail: Sale Order to Delivery and Invoice, Invoice to Payment, Purchase Order to Bill and Receipt — so finance, warehouse and sales teams all read the same branch on every related document.
A two-tier security model gives Managers full visibility while Users stay scoped to their allowed branches, and a built-in guard prevents users from accidentally posting documents against the wrong branch. Printed Sale Order, Purchase Order, Invoice, Payment and Stock PDFs all show the branch in the header. Useful for retailers with multiple shops, service providers with regional offices, distributors with branch warehouses, and any company that wants branch-wise reporting without splitting into separate companies.
Features
- Dedicated Branches Master: A new Branches list under Users & Companies lets you create each branch with name, logo, address, mobile, email and website.
- Per-User Branch Assignment: Every user gets a Current Branch and a list of Allowed Branches, so their work is automatically scoped to the right places.
- Branch on Every Key Document: A Branch field is added to Customers, Leads, Sales Teams, Products, Sale Orders, Purchase Orders, Invoices, Payments and Project Tasks.
- Branch on All Inventory Records: Warehouses, Locations, Routes, Putaway/Pull Rules and Operation Types all carry the branch they belong to.
- Auto-Flow Across the Paper Trail: Branch carries forward from Sale Order to Delivery and Invoice, Invoice to Payment, and Purchase Order to Bill and Receipt automatically.
- Branch on Journal Entries: Every journal entry created by an invoice or a payment inherits the branch, so accounting can report profit and loss per branch.
- Two-Tier Security Model: Branch Managers see everything; Branch Users only see documents that match their allowed branches — across CRM, Sales, Purchase, Inventory and Accounting.
- Wrong-Branch Guard: A warning blocks users from posting a document against a branch that is not their current branch, preventing cross-branch mistakes.
- Default Branch on New Records: New Sale Orders, Purchase Orders, Invoices, Payments, Warehouses and Stock Rules pick up the user's current branch automatically.
- Branch on Printed Reports: Sale Order, Purchase Order, Invoice, Payment and Stock PDFs print the branch in the header so external recipients see the right office on every document.
- Multi-Company Compatible: Branches are scoped per company, so a holding company with several subsidiaries can keep its branch lists clean and separate.
Create Your Branches
Go to Settings > Users & Companies > Branches to set up each shop, office or division as its own branch — here three sample branches are already in place.
Assign Branches to a User
A new Branches tab on every user record lets you pick a Current Branch and the list of Allow Branches they may work in.
Branch on Customers and Vendors
Every partner record gets a Branch field, so each customer or vendor is tied to the branch that owns the relationship.
Branch on CRM Leads
CRM leads also carry a Branch, so your pipeline can be filtered, grouped and reported by branch.
Branch on Sales Teams
Sales Teams can be assigned to a specific branch so each team's leads and orders stay grouped under the right office.
Branch on Products
Products carry a Branch too — useful when certain items are only sold or stocked at specific branches.
Branch on Sale Orders
A new Branch field on the Sale Order's Other Info tab records which branch is responsible — and this value carries through to Delivery and Invoice automatically.
Branch on Purchase Orders
Purchase Orders also carry the branch and pass it on to the resulting Vendor Bill and Receipt with no extra steps.
Branch on Invoices
Customer Invoices and Vendor Bills show the branch that produced them — and the same branch lands on the journal entry behind the document.
Branch on Payments
Each payment is stamped with a branch and the same value is copied to the journal entry, so cash and bank movements can be reported per branch.
Branch on Warehouses
Each warehouse can be tagged with the branch that runs it — here the main warehouse is linked to Branch 1.
Branch on Stock Locations
Stock Locations also carry the branch, keeping on-hand stock segmented by the office or shop it belongs to.
Branch on Putaway and Pull Rules
Inventory rules can be assigned to a branch so replenishment logic stays scoped to the right location.
Branch on Operation Types
Receipt, Delivery, Internal Transfer and other Operation Types inherit the branch from their warehouse, so every picking is correctly tagged.
Branch on Inventory Routes
Routes can also carry a branch, so multi-step flows like buy-to-stock or make-to-order respect branch boundaries.
Version 1.0 | Released on : 3rd October 2023
-
Is this app compatible with Odoo Enterprise?
- Yes, our app works with Odoo Enterprise as well as Community.
-
If need of customization in this app, How can i contact ?
- Please contact us on odoo@devintellecs.com
-
Do i get free support?
- Yes, you will get free support for 90days.
-
Do i get free updates?
- Yes, you will get free updates for lifetime.
-
Do i have to buy this module for each version ?
- Yes, you have to buy this module for each version.
Support
Why Us?
Devintelle Odoo Services
Connect Us
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module