Default Sales UoM
by CLuedoo https://www.cluedoo.com/shop/lic-clu-set-sal-0037-default-sales-uom-6603$ 100.57
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Manufacturing (mrp)
• Purchase (purchase) • Sales (sale_management) • Invoicing (account) • Discuss (mail) • Inventory (stock) |
| Lines of code | 61 |
| Technical Name |
fal_default_sol_uom_product |
| License | OPL-1 |
| Website | https://www.cluedoo.com/shop/lic-clu-set-sal-0037-default-sales-uom-6603 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Manufacturing (mrp)
• Purchase (purchase) • Sales (sale_management) • Invoicing (account) • Discuss (mail) • Inventory (stock) |
| Lines of code | 61 |
| Technical Name |
fal_default_sol_uom_product |
| License | OPL-1 |
| Website | https://www.cluedoo.com/shop/lic-clu-set-sal-0037-default-sales-uom-6603 |
STORY BEHIND THE FEATURE
ODOO BEHAVIOR
In Odoo, the Purchase Unit is used as the default unit of measure (UoM) for purchase orders, but there is no dedicated UoM for sales orders generated from intercompany transactions. This can cause discrepancies when a purchase order automatically creates a sales order in the vendor company, leading to mismatched quantities and UoMs.
CLUEDOO BEHAVIOR
Cluedoo introduces a UoM Sales Order (UoM SO) feature to ensure that sales orders generated from intercompany purchases reflect the same quantity and UoM as in the purchase order. When a user selects a UoM SO, it is applied to the sales order in the vendor company, preventing inconsistencies and ensuring seamless data synchronization in Make-to-Order (MTO) and intercompany transactions .
CLUEDOO RECOMMENDATION
Install on 100% of your database.
OUR FEATURES AS SOLUTIONS
Add default Sales UoM in SO line with MTO/intercompany transactions
HOW TO USE THIS MODULE
|
1. Go to Settings in both companies and checkbox Inter-Company Transactions , Generate Sales Orders , Generate Purchase Orders |
|
|
2. Go to Sales > Configuration > Unit of Measure > Unit of Measure Categories > Create a new UoM that is smaller/bigger than the reference UoM e.g. I create a Box of 10 Units |
|
|
3. Create a new product or choose an existing one > Set Purchase Unit under Purchase tab and UoM SO under Sales tab |
|
|
Note: Purchase Unit and UoM SO must be in the same category as the default UoM |
|
|
4. Under the Inventory tab, set the Routes to Buy and MTO |
|
|
5. Create a new Purchase Order > Choose the Vendor and add the product > Confirm Order |
|
|
6. Go to the Vendor's Sales Order , the information from the Purchase Order has been transferred with the correct Quantity and UoM |
|
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