Multi Branch PLM | Multiple Branch Unit for PLM | Manage Multiple Branch for PLM
by BROWSEINFO https://www.browseinfo.com$ 124.38
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Product Lifecycle Management (PLM) (mrp_plm)
• Manufacturing (mrp) • Inventory (stock) • Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 1833 |
| Technical Name |
bi_branch_plm |
| License | OPL-1 |
| Website | https://www.browseinfo.com |
| Versions | 15.0 16.0 17.0 18.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Product Lifecycle Management (PLM) (mrp_plm)
• Manufacturing (mrp) • Inventory (stock) • Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 1833 |
| Technical Name |
bi_branch_plm |
| License | OPL-1 |
| Website | https://www.browseinfo.com |
| Versions | 15.0 16.0 17.0 18.0 |
India |
Malaysia
Multiple Branch Unit Operation for PLM Odoo App
PLM with Multi Branch Setup
Branch Unit Management for PLM Odoo App
Multiple Branch Handling for PLM Odoo App
Multiple Branch Unit Operation for PLM Odoo App enhances Odoo's Product Lifecycle Management by introducing seamless multi branch functionality, enabling organizations to manage PLM operations independently across various company branches. This integration ensures that each branch can handle its own product versions, engineering changes, and documentation workflows while maintaining centralized oversight. It supports improved collaboration, traceability, and control across locations, allowing businesses to streamline engineering processes without cross-branch interference. By aligning PLM tasks with branch-specific contexts, this solution empowers companies with distributed operations to drive innovation, consistency, and efficiency throughout their product development lifecycle.
Multi Branch Concept
It allows you to create multiple Branch/Unit, Working as multi branch concept same as Odoo's multi company environment.
Branch-Based Access Control
Users can view and manage PLM records based on branch assignments.
Engineering Change Orders (ECOs)
Branch-specific approval workflows for product modifications.
Version Control & BOM Management
Maintain version histories for products and associated BOMs per branch.
Branch Access Rights
User have to give branch access like User or Administrator, User have to "Multi Branches"
Create Multiple Branch
Branch Administrator can create multiple branch under Settings > Users & Companies > Branch menu, Branch administrator also can set branch details like address, phone, company.
Assign Branch User
Branch administrator can assign a branch for which specific user is belongs.
Multi Branch Feature
Users with "Multi Branches" access rights can see and change multiple branch from header.
On clicking branch on header user can see allowed branches and can select one, on changing branch users branch will also changed under users settings.
ECO Stages List View
Under PLM > Configuration > ECO Stages menu is visible.
In the ECO Stages, users can assign a specific branch, where the branch 'Ahmedabad, India' is assigned.
ECO Types List View
In the ECO Types configuration, users can assign branches to different ECO types, allowing better categorization and management.
ECO Tags List View
In the ECO Tags configuration, users need to define tag names to categorize different ECO stages efficiently.
Bills of Materials Details
In the Manufacturing module, under the 'Bills of Materials' section, the user is viewing the BoM details for a product. The BoM specifies that the product is set to be manufactured, with the branch assigned accordingly.
Engineering Change Order
In the PLM module, under 'Engineering Change Orders,' the user is viewing an ECO. It applies to the Bill of Materials, is set to be effective immediately, and has an assigned responsible person and branch.
The ECO is currently in the 'New' stage, with a revision version assigned and the branch specified accordingly.
This change order applies to the Bill of Materials and is linked to a product set for manufacturing. The assigned branch is specified, and the ECO is currently in an archived state.
After logging in as another user, the ECOs are still visible, showing that they can be accessed by different users when the branch is set.
Version :
18.0.0.0
13 Jun 2025
Initial release of the app.
Can I Use this module with Odoo Online ?
Do I got free support when I buy an App ?
Do I have to buy module for each version ?
How can I install the module I bought ?
The module I bought doesn't work, What should I do ?
Get Support, For Free!
60 Days Free Support
In case any bugs or issue (Except data recovery)
At BrowseInfo we offer end to end solution for Odoo services. Which includes analysis & consultation on the workflows and integration part.
Have Any Question ?
+91-6351620270
Write Email
Sales : sales@browseinfo.in
Support : ticket@browseinfo.in
Must-Have Apps
Best of the Best Apps
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