Blog Posts Full Content List View

Required Product Settings to Set Up Reordering Rules in Odoo

Setting up a reordering rule for a product allows you to automate the replenishment process, ensuring that stock levels remain sufficient. Before creating the rule, make sure the following settings are in place for the product:

The Buy route is enabled.
At least one vendor is assigned.
The Purchase option is activated.
The product type is set to Goods
Inventory tracking is enabled.

In version 17 and older, the Product Type needs to be set to "Storable.”

Functional Inventory Odoo 18

Dec 10, 2024 Posts

How to Generate Separate Purchase Orders for Each Sales Order in Odoo

If you are using the MTO (Make to Order) route in Odoo to replenish products and require each sales order to generate its own purchase order, here’s a quick guide to set it up:

Activate the “Multi-Step Routes” setting in the Inventory configuration page
Open the “Buy” route via the Inventory > Configuration > Routes menu
Update the “Propagation of Procurement Group” setting in the related rule to “Propagate”

That is it! For each sales order, Odoo will now create a separate purchase order.

Functional Inventory Odoo 18 Purchase Sales

Dec 10, 2024 Posts

Use the "Horizon" Option to Replenish Products in Advance in Odoo

Odoo uses a just-in-time strategy for product replenishment. That means products appear in the Replenishment dashboard based on forecasted dates using the system’s lead times. Which ensures minimal storage costs and timely delivery to customers.

However, this approach has a limitation. If you need more of the same product or products from the same supplier for the next day or near future, they won’t appear in the dashboard. This can complicate long-term planning and increase shipping costs.

The "Horizon" option, introduced in Odoo 18, solves this by extending the forecast period to "n" days into the future. This allows businesses to replenish multiple products in advance, which is especially useful for those managing replenishment periodically.

This functionality is also available in Odoo 16 and Odoo 17. You can activate it by adding the system parameter stock.visibility_days in Settings > Technical > System Parameters (developer mode required). Set the number of days you would like the dashboard to display in the future by entering it as the value for the system parameter.

Functional Inventory Odoo 17 Odoo 18

Dec 5, 2024 Posts

How Odoo Time-Tracking Manages Multiple Active Timers

If you’re using Odoo’s time-tracking feature at the task level, here is something to keep in mind:
When you start a new timer on a task, any active timer on another task is automatically paused. This can lead to multiple paused timers without the user realizing. Over time, this can result in inaccurate time tracking because paused timers do not create timesheet logs.

A more efficient approach would be to notify the user about an active timer and automatically stop the active timer when a new timer is started.

This approach keeps time logs accurate and prevents unnecessary paused timers.

Functional Odoo 17 Project

Dec 5, 2024 Posts

Key Points About the “Replenish Location” Option in Odoo

A few important points about the “Replenish Location” option in Locations:

The "Replenish Location" cannot be applied to both parent and child locations simultaneously.
It is used to specify the system's default replenishment location.
If no "Replenish Location" is selected, a manual reordering rule will not be automatically generated for a product with a negative forecasted quantity.

To enable the "Replenish Location" setting, navigate to the Locations using the menu Inventory > Configuration > Locations. The Locations menu is only accessible if the "Storage Locations" option is activated in Inventory > Configuration > Settings > Warehouse.

Functional Inventory Odoo 18

Dec 5, 2024 Posts

Odoo 18 Gantt View: New Features and Areas for Improvement

The Gantt view is a convenient way to plan a project. It provides a complete picture of the project plan and simple interaction with the tasks. In Odoo 18 this is even better with the latest changes that Odoo added to the view.

The planning period is flexible and can be selected from the predefined periods or choose your own custom range. Also, the view for the selected period can be zoom-in and zoom-out during the planning process.

Additionally, it is possible to have all the tasks grouped by assignee, in that way it is possible to see all the tasks assigned to a user below their name.

Even the improvements from the previous version are noticeable the view is missing a few features that may be crucial for some users.

The view does not support sub-task planning at the moment. They are filtered out from the view. This can be a real problem for companies that do the planning on sub-tasks level. Hopefully, Odoo will introduce this functionality in the near future.

Once sub-tasks are introduced would be convenient to have the related sub-tasks just below their parent task so the user can see the parent task and sub-tasks together while planning.

The ordering at the moment is by planned date, which can be helpful in case when there are not many tasks in the view. However, when a task is moved to a different date, if the view contains a lot of tasks, it can be challenging to locate the updated task.

Also having a configurable colour scheme for the tasks would make it possible for the user to recognize the stage of the task or project based on the colour. It can be done by using the project’s color for the “All Tasks” view while a color set per stage in the views per project.

Functional Odoo 18 Project

Dec 5, 2024 Posts

Default Values in Context and Potential Issues

When passing a default value for a field via context, you need to consider that this value can be passed on to models initially not planned for.

For example, when passing the product_qty as a default value in the manufacturing order, the value will propagate to the stock move as well, which may cause some unexpected issues, since it has the same field.

In such cases, the issue can be resolved by removing the default values from context, once they reach the initially intended model.

Odoo 17 Technical

Dec 5, 2024 Tips

Understanding Routes in Odoo: 3 Key Basics

Understanding Routes in Odoo can be challenging. Here are three basics that may help to make sense of them:

Routes are just groups of rules
They help to organize and assign one or multiple rules to a product
Routes without a rule assigned to them don’t do much.

Functional Inventory

Dec 5, 2024 Posts

Odoo Community vs Enterprise Edition: Which One to Choose?

Odoo Community even though is open source and available for everyone to install, there are associated costs for running it such as:

Server
Maintenance
Upgrade

Some of them overlap if you decide to have Odoo Enterprise on your own server, however, with enterprise, it is easier to keep the system up to date with the newest version and some of the additional features there can be a big plus.

In the end not always open source means a better option for your budget, before going further with the project evaluate the needs of your company and what would best match them.

A more in-depth overview of both versions is available here.

Functional

Dec 5, 2024 Posts

Default Value Issues Caused by the "onchange" Method

A default value for a field may not be set on the creation of a new record, even provided in the field definition

In many cases, the reason for that is an onchange method that is resetting the value for the field. Steps that can help in resolving the issue:

Identify the method that is causing the issue by searching by the field’s name, and seeing where the field’s value is reset.
Try to understand the current logic and how your change will affect it.
Override the method using super and apply your custom logic

Technical

Dec 5, 2024 Tips

Categorize Projects and Tasks Using the "Project Type" Module

Very often businesses that have a portfolio of projects within different industries need the option of categorizing the projects. However the core version of Odoo does not support such functionality, even though in some cases can be used the Tags option, however in that case it is difficult to group the project by category since the Tag field is many2many.

The “Project Type” module makes this functionality possible. It is a very simple module that introduces the Type field in the Project and Task models. Each Project or Task can belong only to one Project Type. Once the projects are categorized they can be grouped using the Group By: Type option.

Group By Project Type

The different project types can be set up in the Project > Configuration > Project Types. Each Project Type can have multiple Subtypes. The available fields for each Project Type are:

Name
Code
Parent Type
Description
Can be applied for Projects
Can be applied for Tasks

The last two listed options are used to configure the Project Type where to be shown in Projects and/or Tasks. In the tab "Subtypes" can be found all the related Subtypes. Additionally, can be created new directly from there.

Project Type Form View

The Project Manager group has full access rights to the Project Types, while every user in the system can see them in the projects and tasks.

One possible improvement for the module can be when a certain type is selected in a project, on creation of a related task the same Type to be selected as the default value, with option to be edited if needed. Because from a business perspective, it can be expected that the project's related tasks would have the same Project Type. To provide more flexibility this option can be customizable per Project Type.

The module is maintained by Odoo Community Association (OCA) and the latest available version is 17.0.1.0.0.

Functional Odoo 17 Project

May 20, 2024 Modules Review

How to Store Different Values in a Field per Company

In multi-company mode, there are cases when one field would need to store different values for each company.

An example of such fields are some of the accounting settings per product, such as Income Account and Expense Account.

In order for a field to be able to store different values per company it is required in the field definition to be set the attribute company_dependent to True.

Part of the definition of the standard_price field which is another example in Odoo of such a field is shown below:

standard_price = fields.Float(
    string='Cost',
    company_dependent=True,
)

While from a user perspective, this functionality depends only on one parameter, the technical side of it is a bit more complex. These fields do not store their values in the related model’s table. Instead, they are using the ir.property table for that. When the value is set in the field, the backend will try to find an existing ir.property record that matches the model’s record, field and company. If there is no one it will create a new record with the following information:

name: The name of the field
fields_id: The ID of the field that holds the value
res_id: The ID of the related model’s record
company_id: The ID of the company
value_: The value will be stored in one of the available value fields, depending on the type of the field. For example, the standard_price field's value will be stored in the value_float column.

Company-dependent fields are searchable and when a value is requested for them the system queries the ir.property table.

The list of all company-dependent values can be found at Settings > Technical > Parameters > Company Properties, developer mode needs to be activated in order to see the Technical menu.

Odoo 17 Odoo 18 Technical

May 7, 2024 Posts