---
title: "IFS Cloud Lead Time: Purchase, Manufacturing and Expected"
date: 2026-10-28
description: "IFS Cloud lead time: how purchase, manufacturing and expected lead time are defined, where each is calculated and which one MRP reads."
author: "Dariusz Myśliwiec"
categories:
  - name: "How IFS Cloud ERP Transforms Business Operations Supply Chain AI and Legacy System Migration"
    url: "https://ifs-erp.consulting/ifs-cloud.md"
tags:
  - name: "IFS Cloud"
    url: "https://ifs-erp.consulting/tags/ifs-cloud.md"
  - name: "Purchasing"
    url: "https://ifs-erp.consulting/tags/purchasing.md"
  - name: "Planning"
    url: "https://ifs-erp.consulting/tags/planning.md"
  - name: "IFS Cloud Implementation"
    url: "https://ifs-erp.consulting/tags/ifs-cloud-implementation.md"
  - name: "Best Practices"
    url: "https://ifs-erp.consulting/tags/best-practices.md"
---

# IFS Cloud Lead Time: Purchase, Manufacturing and Expected

Independent IFS Cloud practice · Planning data design

 
## Know which lead time a function reads before you fill the fields

 **IFS Cloud lead time** lives in several fields, and each field has its own meaning. If purchase, manufacturing and expected lead time are filled without knowing which one a function reads, planned dates and promised dates rest on a value the team does not think it maintains. This article follows the 26R1 documentation on [lead time](https://docs.ifs.com/ifsclouddocs/26r1/MaintainInventory/AboutLeadTime.htm), on the [routing lead time calculation](https://docs.ifs.com/ifsclouddocs/26r1/MfgStandard/AboutManufLeadTimeCalculation.htm) and on [MRP](https://docs.ifs.com/ifsclouddocs/26r1/Planning/AboutMrp.htm), and the 25R2 page on [calculating purchase lead time](https://docs.ifs.com/ifsclouddocs/25r2/Procurement/ActivityCalculatePurchaseLeadtime.htm).

  **Key takeaways**

 
- The page distinguishes purchase lead time, manufacturing lead time and expected lead time, and it states that safety lead time is not a component of purchase lead time.
- Purchase lead time runs from the order until the part is available in inventory and has five components, including transport lead time.
- Manufacturing lead time is calculated in Manufacturing Standard or on the Routing page; the fixed and variable sums on the page hold for a routing alternate with no parallel or overlapping operations.
- Expected lead time assumes that not all component parts are in inventory. Its default is 0, and when it is empty the purchase or manufacturing lead time applies.
- MRP uses the primary supplier’s lead time for a purchased part and the valid routing for a manufactured part, and falls back to the Inventory Part value.
- The test table has four parts, each with an expected source of lead time and an owner.

  ## 1.Which lead times does IFS Cloud define for an inventory part?

 IFS Cloud defines purchase lead time, manufacturing lead time and expected lead time for an inventory part, and it treats safety lead time separately. The table gives what the page says about each.

 
| Lead time | What the page says | Where it comes from |
| --- | --- | --- |
| Purchase lead time | The time from when the part is ordered until it is available in inventory | Supplier and internal components; calculated in the Calculate Purchase Lead Time dialog |
| Manufacturing lead time | Calculated for a manufactured part | Manufacturing Standard/Calculation or the Routing page |
| Expected lead time | The time, in days, to receive the parts into inventory, assuming that not all component parts are in inventory | Entered on the inventory part; defaults to 0, and falls back to the purchase or manufacturing lead time when empty |
| Safety lead time | Not a component of purchase lead time | Used to offset supply generated by MRP, Master Scheduling and Next Level Demand, according to the page |

  ## 2.What is purchase lead time, and what does it include and exclude?

 Purchase lead time is the time from when the part is ordered until it is available in inventory. The page builds it from the primary supplier’s manufacturing lead time, the external transport lead time, the transport lead time, the internal transport lead time and the internal inspection lead time. It adds a note: safety lead time will not be considered as a component in purchase lead time.

 The components sit in different places and use different calendars. You can specify a supplier manufacturing lead time and an internal inspection lead time per combination of supplier and purchase part. Supplier manufacturing lead time is measured in supplier calendar days, or in calendar days if no supplier calendar is defined, and internal inspection lead time is measured in distribution calendar days. The external transport calendar is defined by the Ship Via Code, and internal transport lead time is measured in site distribution calendar days.

 Two further statements affect dates on orders. The total purchase lead time shown on the Inventory Part page is used for calculating dates when, for example, a purchase requisition is entered without a supplier. When a supplier is identified, the system sets dates from the lead times configured in the Supply Chain Matrix and on Supplier for Purchase Part. And on a purchase order, neither internal transport lead time nor external transport lead time is saved. The supplier side of this is covered in [IFS Cloud sourcing rules](https://ifs-erp.consulting/ifs-cloud/ifs-cloud-sourcing-rules-order-supply) and [multi-supplier ordering](https://ifs-erp.consulting/ifs-cloud/multi-supplier-ordering-supplier-split-ifs-cloud).

  ## 3.How is purchase lead time calculated?

 You can calculate the total lead time of a purchased part in the Calculate Purchase Lead Time dialog box, and the result is presented in the Acquisition tab of the Inventory Part page when using the Update option. The 25R2 page on the calculation gives a worked example: a supplier manufacturing lead time of 10, an external transport lead time of 2, a transport lead time of 0 and an internal transport lead time of 1, together with an internal inspection lead time of 1, give a total purchase lead time of 14 days.

 The page names four update options: Update, Update Also Expected, Do Not Update, where there is no update in the system and only a report is created, and Update Using Average Historical Lead Time. The last option does not use the standard set-up lead times. When it is used, the standard set-up lead times on Supply Chain Matrix and Supplier for Purchase Part are not applied, and the purchase lead time is calculated from the actual received and approved dates of the historical receipts.

 For the historical average, the page offers start date options and excludes outliers: values with a Z-score higher than 2.5 are excluded by default, and the threshold can be adjusted to 2 or 3. In the page’s example the average of 4.166 days is rounded up to the nearest full day, 5 days. Whether to use actual receipts or the standard lead times is a decision for purchasing, and the supplier behaviour behind such numbers is discussed in [supplier behaviour change signals](https://www.ifs-erp.com/en/blog/supplier-behaviour-change-signal-ifs-cloud).

  ## 4.What is manufacturing lead time, and where is it calculated?

 Manufacturing lead time can be calculated using the lead time calculations found in Manufacturing Standard/Calculation or in the Routing page. The routing page of the documentation separates a fixed part from a variable part, and the sums hold for a routing alternate having no parallel or overlapping operations: the fixed lead time is the sum of setup time, transport time and queue time for all operations, and the variable lead time is the sum of machine or labor time for all operations.

 The calculation depends on further inputs. The lot size is normally the standard lot size specified on the inventory part. The calculation can be based on machine time, labor time or the maximum of the two. For parallel operations only the operation that takes the longest to complete is considered when calculating the fixed and variable lead time.

 The page works one example without overlap: a fixed lead time of 7h, a variable lead time of 4h and a lot size of 5 pieces give 7h + (4h * 5 pcs) = 27h. A second example, with overlap between operations, uses a variable lead time of 2h and gives 7h + (2h * 5 pcs) = 17h. Routing lead time is used in several places, among them MRP and Master Scheduling. The planning side is covered in [dynamic structures in MRP](https://ifs-erp.consulting/ifs-cloud/dynamic-structures-mrp).

  ## 5.What is expected lead time, and when does it apply?

 Expected lead time is the time, in days, that it takes to receive the parts into inventory, assuming that not all component parts are in inventory. The default value of the Expected Lead Time field is 0 (zero). If no expected lead time is entered in the inventory part record, the expected lead time is the same as the purchase or the manufacturing lead time.

 The page explains why the field exists. The manufacturing lead time of the part can be incorrect because it assumes that all parts are available from inventory, so you should use the Expected Lead Time field to help ensure that a part can be delivered in time. Order promising is covered in [high-fidelity discrete order promising](https://ifs-erp.consulting/ifs-cloud/high-fidelity-discrete-order-promising) and, for capable-to-promise, in [CTP in IFS Cloud](https://www.ifs-erp.com/en/blog/ctp-in-ifs-cloud).

  ## 6.Which lead time does MRP use?

 For purchased parts MRP uses the lead time defined for the primary supplier, including supply chain matrix and inspection lead time. If no valid routing exists or no primary supplier for a purchased part, the lead time specified on the Inventory Part page is used. For a manufactured or remanufactured part, MRP calculates the lead time for a supply from the valid routing.

 The order of preference matters for data maintenance: the supplier’s data comes first for a purchased part, and the Inventory Part value is the fallback. Check for each purchased part which of the two MRP will read before deciding where to maintain the value. The reorder point side of planning is covered in [reorder point planning in IFS Cloud](https://ifs-erp.consulting/business-process-optimisation/reorder-point-planning-ipr-ifs-cloud).

  ## 7.Which decisions belong to planning and purchasing?

 Purchasing owns the supplier-side components and planning owns the manufacturing and expected values, and both own the review date. Purchasing maintains the supplier manufacturing lead time per supplier and purchase part, and the transport lead times. Planning maintains the routing and the expected lead time. Agree how often each value is reviewed, and who decides whether to replace standard lead times by the historical average.

  ## 8.How do you test lead time data before go-live?

 Test lead time data with one part per type and write down the expected planned date before the planning run. The table gives four parts that follow from the documentation.

 
| Part | Expected source of lead time | Owner |
| --- | --- | --- |
| Purchased part with a primary supplier | The primary supplier’s lead time with supply chain matrix and inspection lead time | Purchasing |
| Purchased part with no primary supplier | The lead time on the Inventory Part page | Planner |
| Requisition entered without a supplier | The total purchase lead time on the Inventory Part page | Buyer |
| Manufactured part with a valid routing | The routing lead time; expected lead time is checked separately against the promised date | Planner |

  ## 9.What does a lead time data checklist contain?

 Lead time data is ready for go-live when each of the checks below has a record behind it.

 
1. The five components of purchase lead time are maintained where the page places them, in the calendars it names.
2. Safety lead time is kept out of purchase lead time.
3. Primary suppliers are set, so that MRP reads the supplier data and not the part field.
4. Routings are valid for manufactured parts, and their standard lot size is set.
5. Expected lead time is set where components can be missing, and its default of 0 has been checked.
6. The update option used for calculating purchase lead time is decided.
7. The four test parts are recorded with expected dates.
8. Each value has an owner and a review date.

  ## 10.Frequently asked questions

 What is the difference between purchase lead time and expected lead time in IFS Cloud? Purchase lead time in IFS Cloud is the time from when a part is ordered until it is available in inventory, built from supplier and internal components. Expected lead time is the time, in days, to receive the parts into inventory assuming that not all component parts are in inventory. Its default is 0, and when it is empty the purchase or manufacturing lead time applies.

   Does purchase lead time include safety lead time? No. The IFS Cloud documentation states that safety lead time will not be considered as a component in purchase lead time. The page says it is used to offset the supply generated by MRP, Master Scheduling and Next Level Demand.

   Where is purchase lead time calculated and stored? Purchase lead time is calculated in the Calculate Purchase Lead Time dialog box in IFS Cloud. The result is presented in the Acquisition tab of the Inventory Part page when the Update option is used. With the Do Not Update option nothing is changed and only a report is created.

   Which lead time does MRP use for a purchased part? For a purchased part, MRP in IFS Cloud uses the lead time defined for the primary supplier, including supply chain matrix and inspection lead time. If no valid routing exists or there is no primary supplier for the purchased part, MRP uses the lead time specified on the Inventory Part page.

   Why can the routing-based manufacturing lead time be misleading? The routing-based manufacturing lead time in IFS Cloud assumes that all parts are available from inventory. When components can be missing, the documentation says to use the Expected Lead Time field to help ensure that a part can be delivered in time.

  ## 11.About the author

 **Dariusz Myśliwiec**: 18 years hands-on with IFS, including IFS Cloud. Based in Kraków, delivering remotely across Europe and globally through an independent practice. You talk to the consultant who does the work, not a sales layer.

 IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.

  ## Do your planned dates match what you promise?

 A review of lead time data against what planning and order promising read shows which field each function uses and where the values come from. Planning and purchasing take part.

 [Book a lead time data review](https://ifs-erp.consulting/contact) [Read about dynamic structures in MRP](https://ifs-erp.consulting/ifs-cloud/dynamic-structures-mrp)