UoM Category on product and BOM
by CLuedoo https://www.cluedoo.com/shop/lic-clu-set-pcq-0098-uom-category-on-product-and-bom-6770$ 100.57
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Manufacturing (mrp)
• Inventory (stock) • Discuss (mail) |
| Lines of code | 35 |
| Technical Name |
fal_bom_uom_product_category |
| License | OPL-1 |
| Website | https://www.cluedoo.com/shop/lic-clu-set-pcq-0098-uom-category-on-product-and-bom-6770 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Manufacturing (mrp)
• Inventory (stock) • Discuss (mail) |
| Lines of code | 35 |
| Technical Name |
fal_bom_uom_product_category |
| License | OPL-1 |
| Website | https://www.cluedoo.com/shop/lic-clu-set-pcq-0098-uom-category-on-product-and-bom-6770 |
STORY BEHIND THE FEATURE
ODOO BEHAVIOUR
In manufacturing, accurate Units of Measure (UoM) are essential to ensure production consistency and correct cost calculations. However, mismatches between the UoM category in the product and the UoM used in the Bill of Materials (BoM) can lead to confusion, errors in production, incorrect quantity conversions, and ultimately, financial misstatements.
Odoo does not block or warn users when different UoM categories are used between product and BoM, which increases the risk of invalid configurations, especially during mass imports or updates.
CLUEDOO BEHAVIOUR
✅ Prevents UoM inconsistencies between product and BoM by enforcing the same UoM category:
-
On BoM creation :
-
The UoM field only shows UoMs from the same category as the product’s UoM.
-
-
On product UoM change :
-
If you change the UoM of the product to a different category than the one used in the existing BoMs, a warning is displayed.
-
-
On BoM import :
-
During mass import of BoMs, if any UoM mismatch is detected, a warning is raised to notify the user of the issue.
-
✅ Supports multi-BoM setups and continuous validation.
COMPARISON: ODOO AND CLUEDOO
Odoo:
-
No warning when the UoM category in BoM and Product differs.
-
Allows mismatched UoMs that can break production flows.
-
High risk during imports or data migration.
CLuedoo:
-
Restricts BoM UoM to match the product’s UoM category.
-
Displays warnings on BoM update, product UoM change, and import.
-
Ensures consistency and production data integrity.
BUSINESS CASE
A manufacturing company produces items in kilograms, but an employee accidentally creates a BoM with a UoM in liters. Production will miscalculate required inputs, resulting in inventory errors and distorted cost reports.
OUR FEATURES AS SOLUTIONS
Display a warning when the UoM category in BOM is not the same as the UoM category in Product
|
|
|
2. Create
BoM
> fill in the information > you can only select
UoM
that belongs to the same
product category
. The behavior is the same when you create more BoMs
|
|
|
3. If you change the UoM in the product template to a
different
one from the BoM, a warning will display
|
|
|
4. The warning is the same when you import the BoM
|
|
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