The need
You sell a 14-hour pack or a package per unit and Odoo sees a single hour. Your teams then plan undersized tasks and tracking of the time sold becomes wrong.
What you gain
Hours carried by the product
Enter on the service product form what one unit sold stands for, for example 14 hours.
Task at the right size
On confirmation, the created task receives the product hours multiplied by the ordered quantity.
Split by percentage
On a project template, each task takes its share of the hours sold and the project adds up its tasks.
Hours sold counted once
When the line also creates its own task in the project, the time is not doubled.
Follows later changes
Changing the line quantity updates the task while a server action recomputes a whole order.
Nothing to do for the rest
Products sold in days or hours and services invoiced by milestones keep the Odoo rule.
How it works
Fill in the product
Enter the allocated hours on every service product that stands for a pack or a package.
Split on the template
If a project template is used, set the hours percentage of each task. The default value is 100%.
Quote and confirm
Show the hours columns in the quotation lines if you wish, then confirm the order.
Check the tasks
The tasks or those of the project carry the allocated time. The Task time initialization action refreshes everything.
Screenshots
Frequently asked questions
Nothing. Leave the field empty: the native Odoo conversion keeps applying. Filling in hours on a product already sold in hours would multiply the time.
Hours per unit multiplied by the ordered quantity. Three packs of 14 hours therefore give 42 hours on the task.
The task follows the new quantity. A context key lets you switch that update off in your own processing.
With the hours percentage of each task of the project template. Subtasks keep their native hours.
Yes, with the Task time initialization action of the order, which recomputes the allocated time of all its tasks.
No. It keeps the native Odoo rule: the module adds no hours to the task nor to plan.
This release targets Odoo 20, Community or Enterprise. It relies on the sales with timesheets, sales projects and project apps.
Only the fields of the module disappear. No native field was redefined and the Odoo rule applies again.
Scope
It completes Odoo sales with timesheets: products without allocated hours keep the native conversion and no standard field is redefined.
Technical sheet
- Technical name
- anor_sale_task_allocated_time
- Odoo versions
- 18.0, 19.0, 20.0
- Application
- Project
- Dependencies
- sale_timesheet, sale_project, project
- Licence
- LGPL-3
- Published by
- ANOR
Disclaimer — This module is provided "as is", without warranty of any kind. ANOR Group shall not be held liable for any direct or indirect damages resulting from its use, its installation or its modification by a third party, nor from its use outside the scope of a contractual ANOR service.









