Stock Warehouse Calendar
This module adds a Calendar to the Warehouse. This calendar can then be used as the basis of the proper computation of start/end dates based on lead times in this and other modules.
In this module, the calendar is used to compute the start dates of stock moves and pickings generated from procurements, taking lead times into account.
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Lets you attach a working schedule (calendar) to a warehouse so that stock move and picking dates are planned on working days instead of plain calendar days.
This module adds a Working Schedules field to each warehouse. You pick an existing working schedule (the same kind of calendar used for working hours), and Odoo then uses it whenever it has to shift a date by a number of days for that warehouse.
Where it appears: - On the warehouse form, right after the Company field, you can select a Working Schedules calendar.
What changes automatically: - When a stock rule creates a stock move, the planned date of the move is recalculated backwards from the planned date using the rule's lead time, counting only the warehouse's working days. So a 3-day lead time no longer lands on a weekend or a non-working day. - When a push rule chains a new move after an existing one, the new move's date is calculated forward from the previous move's date, again skipping non-working days. - If no calendar is set on the warehouse, or the rule has no lead time, the standard Odoo behaviour is kept.
The module touches the warehouse configuration (stock.warehouse), the stock rules that generate moves (stock.rule), and the resulting stock moves and pickings. It relies on the standard working schedules model (resource.calendar) and its day-planning logic.
Depends on
Required by other modules
Models and fields (2)
- stock.rule · extends an existing model
- stock.warehouse · extends an existing modelcalendar_id (Working Schedules)
Text generated by AI (DeepSeek) from reading the Odoo 19.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: 8 confirmed, 1 with no information of 9 versions.
Sources · Odoo 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/stock-logistics-warehouse.
terminal Installation and usage
OCA documentation · Odoo 19.0Configuration
Source · Odoo 19.0- Go to Settings and activate the developer mode.
- Go to Settings \> Technical \> Resource \> Working Schedules and define your Working Time.
- Go to Inventory \> Configuration \> Warehouse Management \> Warehouses and assign the Working Schedule.
- Go to Inventory \> Configuration \> Settings and in Warehouse mark 'Multi-Step Routes option'.
- Go to Inventory \> Configuration \> Warehouse Management \> Routes and set up the proper delays in the stock rules where 'action' is 'Pull and Push' or 'Pull'.
Usage
Source · Odoo 19.0When a picking is generated from a procurement evaluation (e.g., from an orderpoint or MTO), the warehouse calendar is used to calculate the expected dates for the picking and its associated stock moves.
For instance, if a stock transfer from another warehouse requires 1 day to complete and the product is needed on a Monday, the system will determine that the transfer must begin on the previous Friday. This ensures the product arrives on time, considering the warehouse operates under a Monday-to-Friday working calendar. Without the calendar adjustment, the system might incorrectly plan the transfer to start on Sunday, a non-working day, which could lead to delays.
It also works for push rules, it will apply the delay defined in the rule respecting the warehouse calendar to schedule the move.
No verified information in OCA: Installation.
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.