2
2
Lead times
3
3
==========
4
4
5
- .. |MO | replace :: :abbr: `MO ( Manufacturing Order ) `
6
- .. |MOs | replace :: :abbr: `MOs ( Manufacturing Orders ) `
5
+ .. |MO | replace :: :abbr: `MO ( manufacturing order ) `
6
+ .. |MOs | replace :: :abbr: `MOs ( manufacturing orders ) `
7
7
.. |BoM | replace :: :abbr: `BoM ( Bill of Materials ) `
8
8
.. |BoMs | replace :: :abbr: `BoMs ( Bills of Materials ) `
9
- .. |RFQ | replace :: :abbr: `RFQ ( Request for Quotation ) `
9
+ .. |RFQ | replace :: :abbr: `RFQ ( request for quotation ) `
10
+ .. |PO | replace :: :abbr: `PO ( purchase order ) `
10
11
11
12
Accurately forecasting delivery dates is vital for fulfilling customer expectations. In Odoo, the
12
- **Inventory ** app allows for comprehensive lead time configuration, allowing coordination and planning
13
- of manufacturing orders, deliveries, and receipts.
13
+ **Inventory ** app allows for comprehensive lead time configuration, allowing coordination and
14
+ planning of manufacturing orders, deliveries, and receipts.
14
15
15
16
Lead time types
16
17
===============
@@ -75,7 +76,7 @@ Odoo issues a warning message if the set delivery date is earlier than the expec
75
76
not be feasible to fulfill the order by that time, which would impact other warehouse operations.
76
77
77
78
.. example ::
78
- A :abbr: `SO ( Sales Order ) ` containing a `Coconut-scented candle ` is confirmed on July 11th. The
79
+ A :abbr: `SO ( sales order ) ` containing a `Coconut-scented candle ` is confirmed on July 11th. The
79
80
product has a customer lead time of 14 days, and the business uses a sales security lead time of
80
81
1 day. Based on the lead time inputs, Odoo suggests a delivery date in 15 days, on July 26th.
81
82
@@ -149,28 +150,80 @@ and set the :guilabel:`Shipping Policy` to:
149
150
delivery date is 5 days from today: April 7th. On the other hand, selecting :guilabel: `When all
150
151
products are ready ` configures the scheduled date to be 8 days from today: April 10th.
151
152
152
- .. _inventory/warehouses_storage/purchase-lt :
153
-
154
153
Purchase lead times
155
154
===================
156
155
157
- Automatically determining the dates on which to place orders from suppliers can help simplify the
158
- procurement process .
156
+ Automatically scheduling supplier orders streamlines procurement by showing users exactly when to
157
+ confirm a request for quotation (RFQ) and when to expect the goods .
159
158
160
- Odoo calculates the supplier shipment *receipt date *, and :abbr: `PO ( Purchase Order ) ` deadline,
161
- based on the required date the product is needed in the warehouse. By working backwards from the
162
- receipt date, vendor lead times and purchase security lead times are taken into account, in order to
163
- determine the :abbr: `PO ( Purchase Order ) ` deadline.
159
+ .. list-table :: Key dates on an RFQ / PO
160
+ :header-rows: 1
161
+ :stub-columns: 1
164
162
165
- This deadline is the date by which the order should be confirmed, in order to ensure timely arrival
166
- by the expected receipt date.
163
+ * - Field
164
+ - Description
165
+ * - Order Deadline
166
+ - Last calendar day to confirm the |RFQ | and convert it to a |PO |
167
+ * - Expected Arrival
168
+ - Arrival date of the products. Calculated by *Order Deadline * + *Vendor Lead Time *
167
169
168
- .. image :: lead_times/vendor-lead-times.png
169
- :alt: Visualization of PO deadline and receipt date used with vendor lead times.
170
+ In addition, Odoo has global security lead times, which are buffers that widen the
171
+ :ref: `just-in-time <inventory/warehouses_storage/just-in-time >` (JIT) forecast window. The security
172
+ lead times affect **only ** replenishment methods that use :doc: `pull rules
173
+ <../../shipping_receiving/daily_operations/use_routes>`—for example :doc: `reordering rules
174
+ <reordering_rules>` or :doc: `make to order (MTO) <mto >`. They do not change the interval between
175
+ *Order Deadline * and *Expected Arrival *.
170
176
171
177
.. seealso ::
172
178
:doc: `PO scheduling with reordering rules <reordering_rules >`
173
179
180
+ .. list-table :: Global security lead time buffers
181
+ :header-rows: 1
182
+ :stub-columns: 1
183
+
184
+ * - Buffer
185
+ - Purpose
186
+ - Impact on dates
187
+ * - :ref: `Purchase Security Lead Time <inventory/warehouses_storage/purchase-security-lt >`
188
+ - Extra calendar days to account for delays. Typically used to account for weekends or
189
+ holidays.
190
+ - None on the |RFQ |/|PO |; adds buffer days in the :ref: `JIT forecast window
191
+ <inventory/warehouses_storage/forecasted-date>`.
192
+ * - :ref: `Days to Purchase <inventory/warehouses_storage/days-to-purchase >`
193
+ - Days the vendor needs to review an |RFQ | after it is sent.
194
+ - None on the |RFQ |/|PO |; adds buffer days in the :ref: `JIT forecast window
195
+ <inventory/warehouses_storage/forecasted-date>`.
196
+
197
+ .. image :: lead_times/vendor-lead-times.png
198
+ :alt: Visualization of PO deadline and receipt date used with vendor lead times.
199
+
200
+ .. example ::
201
+ To tie all the purchase lead times together, consider this:
202
+
203
+ - Today: April 21
204
+ - :guilabel: `Vendor Lead Time `: 1 day
205
+ - :guilabel: `Purchase Security Lead Time `: 4 days
206
+ - :guilabel: `Days to Purchase `: 2 days
207
+
208
+ Days from today = 1 + 4 + 2 = 7
209
+
210
+ Forecasted date = April 28
211
+
212
+ .. figure :: lead_times/forecasted-date-purchase.png
213
+ :alt: Forecasted date calculation on the lead times pop-up.
214
+
215
+ Example of the :abbr: `JIT (just-in-time)` forecast window, which is April 21-28.
216
+
217
+ If an |RFQ | is created today, the following fields show:
218
+
219
+ - :guilabel: `Order Deadline `: April 23 (:math: `\text {Today} + 2 `)
220
+ - :guilabel: `Expected Arrival `: April 24 (:math: `\text {Order Deadline} + 1 `)
221
+
222
+ .. image :: lead_times/order-deadline.png
223
+ :alt: Order deadline displaying Apr 23 and Expected Arrival Apr 24.
224
+
225
+ .. _inventory/warehouses_storage/purchase-lt :
226
+
174
227
Vendor lead time
175
228
----------------
176
229
@@ -184,7 +237,11 @@ pricelist, click the :guilabel:`Add a line` button to add vendor details, such a
184
237
185
238
.. note ::
186
239
Multiple vendors and lead times can be added to the vendor pricelist. The default vendor and lead
187
- time selected will be the entry at the top of the list.
240
+ time selected is the entry at the top of the list.
241
+
242
+ .. tip ::
243
+ A |PO | is marked late if the *Expected Arrival * date has passed, and appears in the *Late * box on
244
+ the **Purchase ** app's dashboard.
188
245
189
246
.. example ::
190
247
On the vendor pricelist of the product form, the :guilabel: `Delivery Lead Time ` for the selected
@@ -193,46 +250,20 @@ pricelist, click the :guilabel:`Add a line` button to add vendor details, such a
193
250
.. image :: lead_times/set-vendor.png
194
251
:alt: Add delivery lead times to vendor pricelist on a product.
195
252
196
- By setting the vendor lead time, the expected arrival date of the item is automatically determined
197
- as the date of the :abbr: `PO ( Purchase Order ) ` confirmation, plus the vendor lead time. This ensures
198
- that warehouse employees are notified, if the products do **not ** arrive within the expected
199
- timeframe.
200
-
201
- .. example ::
202
- On a :abbr: `PO ( Purchase Order ) ` confirmed on July 11th, for a product configured with a 10-day
203
- vendor lead time, Odoo automatically sets the :guilabel: `Receipt Date ` to July 21st. The receipt
204
- date also appears as the :guilabel: `Scheduled Date ` on the warehouse receipt form, accessible
205
- from the :guilabel: `Receipt ` smart button, located on the :guilabel: `PO (Purchase Order) `.
206
-
207
- .. image :: lead_times/receipt-date.png
208
- :alt: Show expected *Receipt Date* of the product from the vendor.
209
-
210
- .. image :: lead_times/scheduled-date-receipt.png
211
- :alt: Show expected *Scheduled Date* of arrival of the product from the vendor.
212
-
213
253
.. _inventory/warehouses_storage/purchase-security-lt :
214
254
215
255
Purchase security lead time
216
256
---------------------------
217
257
218
- *Purchase security lead time * is set globally for the business in :menuselection: ` Inventory app -->
219
- Configuration --> Settings `.
258
+ *Purchase security lead time * is a global buffer to account for delays, applied to ** all ** vendors.
259
+ To set it, go to :menuselection: ` Inventory app --> Configuration --> Settings `.
220
260
221
- On the :guilabel: `Settings ` page, under the :guilabel: `Advanced Scheduling ` heading, tick the
222
- checkbox for :guilabel: ` Security Lead Time for Purchase ` .
261
+ Under :guilabel: `Advanced Scheduling `, tick the :guilabel: `Security Lead Time for Purchase `
262
+ checkbox.
223
263
224
264
Next, enter the desired number of calendar days. By configuring the security lead time, a buffer is
225
265
set to account for potential delays in supplier deliveries. Then, click :guilabel: `Save `.
226
266
227
- .. example ::
228
- Setting the :guilabel: `Security Lead Time for Purchase ` to `2.00 ` days, pushes the
229
- :guilabel: `Scheduled Date ` of receipt back by two days. In that case, if a product is initially
230
- scheduled to arrive on April 6th, with a two-day security lead time, the new scheduled date for
231
- the receipt would be April 8th.
232
-
233
- .. image :: lead_times/vendor-security.png
234
- :alt: Set security lead time for purchase from the Inventory > Configuration > Settings.
235
-
236
267
.. _inventory/warehouses_storage/days-to-purchase :
237
268
238
269
Days to purchase lead time
0 commit comments