Project Task Advanced Stock

When a project consumes goods and builds items, material and production are usually managed on one side and the schedule on the other. Whoever runs the site then spends the day reconciling the two by hand.

Who is it for

Companies delivering projects that consume material and produce items on order.

How it works

The project declares its warehouse and the operation used by default; every new activity inherits both.
Each activity owns its deliveries and its production orders, reachable from the activity itself.
The progress of an activity follows the deliveries that have been completed.
Entering a percentage of progress launches the production of the corresponding quantity, splitting the order when needed.
A template project can declare the goods to ship for each phase, turned into a delivery as soon as the order is sold.

The result: The activity becomes the single place to see and drive both goods and production.

More Information

Per maggiori info sui nostri moduli non esitare a contattarci

Project Task Advanced Stock

Drive stock pickings and manufacturing orders from project tasks

Turns a project task into the operational unit that consumes goods and produces items: it carries its own operation type and locations, owns its pickings and manufacturing orders, and its progress can be driven from either side.

Features

Warehouse and Default Task Operation Type on the project; every new task inherits the operation type and the default locations.
Stock Pickings and Manufacturing stat buttons on the task, switched by the operation type (mrp_operation or not).
Task progress fed by the pickings that are done, through an automation rule on the picking state.
Current Task Progress – writing it launches the production of the corresponding share of the task quantity, splitting the manufacturing order into a backorder when needed.
All the manufacturing orders of a task must build the same product (constraint).
Products To Send on a service product: the products to ship for each template task, matched by task Code, turned into a picking when the task gets its sale order.
Operation types can be excluded from project tasks with Allow in Project Tasks.

Main fields

Model	Field	Type	Description
project.task	picking_type_id / default_location_src_id / default_location_dest_id	—	Operation type and locations of the task
project.task	stock_picking_ids / mrp_order_ids	One2many	Pickings and manufacturing orders of the task
project.task	mrp_production_progress / current_task_progress	Float	Production progress, readable and writable
project.task	code	Integer	Code matching a template task with the products to send
project.project	stock_warehouse / default_task_picking_type_id	Many2one	Warehouse and default operation type of the site
product.stock.service	—	Model	A product to send for a service, tied to a template task
stock.picking	task_id	Many2one	Task the picking belongs to
mrp.production	task_id	Many2one	Task the manufacturing order belongs to

Demo data

The Showroom Fit-out project driving its goods from the tasks, plus a dedicated Palazzo Mercanti Site warehouse used further up the stack.
Two pickings on the delivery task, one validated and one still open, which puts the task progress at 50 %.
A production task carrying a manufacturing operation type and a confirmed order of 6 units.
A Fit-out Template project sold through the Demo Fit-out Service product, with the products to send matched to the template tasks by their Code.

Changelog

Version	Notes
19.0.1.0.0	Migration to Odoo 19.0: unit tests, demo data, Italian translation and documentation.

Developed by STeSI Consulting — Francesco Moccia <moccia.f@stesi.consulting>