Stock Picking Late Activity
This module adds a 'scheduled action' that periodically checks that the 'scheduled date' of the pickings belonging to certain 'operation types' is prior to the datetime that these checks are performed. For each of the pickings that meet this condition, an activity will be created indicating that the 'scheduled date' must be updated.
The operation types that will be taken into account are those that you determine by checking a specific checkbox for that.
auto_awesome What this module does
AI-generated from the code · Odoo 16.0Automatically creates an activity on transfers whose scheduled date has passed, so the responsible person is reminded to update the planned date. You choose which operation types are monitored and who is responsible.
This module adds an automatic reminder for transfers (pickings) that are running late. On each operation type (for example Receipts, Delivery Orders or Internal Transfers) you get two new fields: a checkbox to enable the control, and a "Late picking activity responsible" user. The responsible user field only appears and becomes mandatory when the checkbox is ticked.
A scheduled action runs every 2 hours. It looks for transfers that are not in draft, done or cancelled, whose operation type has the checkbox enabled, and whose scheduled date is earlier than the current date and time. For each of those late transfers it creates an activity of type "Late picking" with the summary "Update scheduled date", assigned to the responsible user configured on the operation type. The activity is marked as automated and is only created if the transfer does not already have an activity of that same type, so it is not duplicated on every run.
The activity appears in the usual Odoo activity list of the transfer and in the activities of the assigned user. The module touches the stock.picking and stock.picking.type models and adds the new fields to the operation type form.
Depends on
Models and fields (2)
- stock.picking · extends an existing model
- stock.picking.type · extends an existing modelcreate_late_picking_activity, late_picking_activity_user_id (Late picking activity responsible)
Text generated by AI (DeepSeek) from reading the Odoo 16.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 3 confirmed, 6 with no information of 9 versions.
Sources · Odoo 16.0
Confirmed on 2026-11-03 in branch 16.0 of OCA/stock-logistics-workflow.
terminal Installation and usage
OCA documentation · Odoo 16.0Configuration
Source · Odoo 16.0To configure this module, you need to:
- Go to Inventory > Configuration > Warehouse Management > Operations Types
- Open the operation type for which you want late picking activities to be generated.
- Check 'Create Late Picking Activity' checkbox, select the user who will be responsible for the generated activity and save the form.
- From time to time, your system will check if exist late pickings ('scheduled date' is before current date) and will create an activity for them, with the user selected in the corresponding operation type as responsible.
This module generates a 'scheduled action' to create the late picking activities when is needed. To adjust the parameters for that:
- Go to * Settings > Technical > Automation > Scheduled Actions *
- Finds the 'scheduled action' named 'Picking: activities for late pickings'
- Edit it and adjust the parameters if you need and save the form.
The late picking activities created will be associated with a new 'activity type'. If you want to adjust the parameters of that:
- Go to * Settings> Technical> Email> Activity Types *
- Find the 'activity type' named 'Late picking'
- Edit it and adjust the parameters if you need and save the form.
Note: The summary and note of the created activities will be the same defined as summary in the 'activity type' named 'Late picking'.
No verified information in OCA: Installation, Usage.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.