IFS Cloud inventory · Planning and replenishment
Stop chasing shortages: let IFS Cloud plan stock from parameters someone owns
Reactive inventory management in IFS Cloud ends when every stocked part has a planning method, a calculated safety stock and order point, an order proposal that turns them into supply, and a named person who works the exceptions every day.
Key takeaways
- Reactive inventory management means a person notices a shortage and creates the supply by hand. Planned inventory management means a parameter on the inventory part triggers the supply before the shortage.
- The planning method decides who plans the part: MRP for methods such as A (Lot for Lot) and D (Fixed Lot Size), the order proposal for B (Order Point Planning) and C (replenishment level).
- Calculate Planning Data derives safety stock, order point and lot size from part data with the Wilson formula, but only when at least one automatic update function is enabled.
- Perform Order Proposal creates a purchase requisition or a purchase order for parts on method B or C, depending on the supply type on the inventory part.
- Planning reduces exceptions but does not remove them. Stock below minimum, unconfirmed orders and late deliveries still need an owner and a daily routine.
Reactive inventory management is replenishment triggered by a person who notices that stock is short, instead of by a parameter that the system checks on every planning run. In IFS Cloud the move to planned inventory management uses standard functions: a planning method on each inventory part, safety stock and order point calculated from demand and lead time, and an order proposal that creates the supply. The cost of staying reactive shows up twice: as expedited purchases on the parts that run out and as dead stock on the parts that were over-ordered to be safe. The second problem is covered in The Pallet in the Corner. This article is about the first.
1.What reactive inventory management looks like in IFS Cloud
An IFS Cloud site is managing inventory reactively when the planning data on its inventory parts no longer drives the purchases that are actually placed. The signs are visible in the system without an interview.
- Manual requisitions after a shortage. Buyers create purchase requisitions by hand for parts that should have been proposed by planning, and the due date is already inside the supplier lead time when the requisition is created.
- Order points entered once. The order point and safety stock were typed in at go-live and never recalculated, so they describe demand and lead times from years ago. The drift is described in Reorder Points Set Once and Never Revisited in IFS Cloud.
- Parts with no planning data at all. A stocked part with a zero order point and zero safety stock cannot trigger a proposal, so the first signal is an empty bin. See Parts Missing Planning Parameters in IFS Cloud.
- A spreadsheet next to the system. The real reorder logic lives in a planner's file, and IFS Cloud only records the orders that come out of it.
Each sign points to a different fix. Manual requisitions point to the planning method, stale values point to the calculation, and missing values point to master data.
2.Which planning method should a part use?
The planning method on the inventory part decides whether MRP plans the part or whether the order point logic does, so it is the first decision in moving from reactive to planned replenishment. IFS provides the planning method codes, and the full list is in Planning Methods on docs.ifs.com. The four below are the ones a purchasing and distribution site chooses between first.
| Method | How the quantity is set | Planned by | Fits |
|---|---|---|---|
| A, Lot for Lot | Order quantity equals the actual demand of the period | MRP | Expensive parts that are not often needed, or complex structures; IFS advises against method A for raw materials and components that are needed in many parts |
| B, Order Point Planning | Order point and order quantity are specified on the inventory part | Order proposal, not MRP | Consumables, spare parts and purchased items with steady independent consumption |
| C, replenishment level | Order quantity is the order proposal quantity minus the quantity on hand | Order proposal, not MRP | Parts where storage space caps the quantity you can hold |
| D, Fixed Lot Size | Order quantity is fixed by the minimum and multiple lot sizes | MRP | Parts bought in packs, pallets or supplier minimums |
Method C appears as Replenishment Level on the planning methods page and as Refill Level on the order proposal page; it is the same code. Methods B and C are not affected by MRP, so a part with demand from production structures that is set to B is replenished from its order point alone, and the dependent demand that MRP would have netted does not create supply for it. The method is therefore chosen per part, not once for the whole site.
3.Safety stock and order point: calculate them, then keep them current
In IFS Cloud, safety stock is the stock held to cover variation in demand, and the order point is the stock level that triggers a replenishment proposal. Both definitions come from Inventory Planning and Replenishment, which also places each part in a frequency class (Fast, Medium, Slow or Very Slow Movers) and a lifecycle stage. IPR plans parts that have planning method B.
The calculation itself is done by Calculate Planning Data. It updates safety stock, order point and lot size from part data, and the lot size follows the Wilson formula, which is the economic order quantity that balances ordering cost against carrying cost. Two settings decide whether the result is usable.
- Service rate. The safety factor in the safety stock calculation is taken from the service rate connected to the inventory part, and service rate is controlled by commodity group 2. A part without the right commodity group gets the wrong buffer.
- Automatic update functions. At least one automatic update function (safety stock, order point or lot size) has to be enabled for the job to update the part.
Inventory Planning and Replenishment adds one rule that matters when values are entered by hand: a value defined on a lower level in its hierarchy always overrides a value defined on a higher level. A value maintained on a lower level is useful for a critical part and harmful when nobody remembers it was set, so record who set it and why.
Schedule the calculation as a recurring job rather than a one-off clean-up. A safety stock calculated once at go-live becomes the stale order point from section 1 within a few planning cycles of changed demand.
4.How the order proposal turns parameters into supply
Perform Order Proposal is the IFS Cloud activity that creates supply for parts on planning method B or C, and the supply type on the inventory part decides whether it creates a purchase requisition or a purchase order. The prerequisites are listed in Perform Order Proposal: the part uses method B or C, which you check on the Inventory Part Planning Data page, and it exists in standard inventory.
The calculation starts from the current quantity and the projected value shown on the Inventory Part Availability Planning page, and a proposal is created when the projected quantity on hand falls below the order point, as described in Order Proposals. The proposal can be run directly or scheduled as a background job. A rollout that works part group by part group looks like this:
- Pick one part group. Start with purchased parts that have steady consumption and a reliable supplier, where order point planning is easiest to check.
- Set the method and commodity group 2. Planning method B or C on each part, and the commodity group that carries the service rate you agreed with the business.
- Run Calculate Planning Data with automatic update. Compare the new safety stock and order point with the old values and with the buyer's experience before accepting them.
- Run the order proposal with requisitions as output. Buyers review proposed requisitions for a few cycles before the supply type is changed to create purchase orders directly.
- Schedule both jobs. The calculation and the proposal run on a fixed rhythm, and manual requisitions for planned parts are treated as an exception to explain.
Distribution orders replace purchase orders when the primary supplier is another site set up for multi-site planning, so a multi-site group should test that path before switching supply types.
5.Planned inventory still needs exception follow-up
Order point planning in IFS Cloud assumes that the supplier confirms the order and delivers on the confirmed date, so every planned part still depends on someone following up the orders that do not behave. A proposal that became a purchase order nobody confirmed, or a delivery date that passed without a receipt, pushes the part below its safety stock while the planning data looks correct.
The follow-up has three questions: which parts are below their minimum stock today, which released purchase orders have no supplier confirmation, and which deliveries are overdue with no receipt. Each needs a named owner and a daily routine, and each list has to stay short enough to be worked, which is the point of The Fastest Way to Get an Alert Ignored. The order states behind the second and third question are covered in Purchase Order Exception States You Cannot Ignore.
If you want to know how large that list is on your own data before changing any planning parameter, the SCM Exception Scan reads your IFS Cloud data and reports exactly these three exceptions: unconfirmed purchase orders in status Released, overdue deliveries without a receipt, and stock below minimum. You get the result in five working days, and nothing is installed in IFS. The opposite signal, stock that sits too long, is measured by the Smart Stock Aging report and explained in Slow-Moving and Obsolete Inventory in IFS Cloud.
6.Frequently asked questions
What is reactive inventory management in IFS Cloud?
Reactive inventory management in IFS Cloud is replenishment created by hand after someone notices a shortage, instead of by planning data on the inventory part. Typical signs are manual purchase requisitions for stocked parts, order points that were never recalculated after go-live, and parts with no safety stock or order point at all.
Which IFS Cloud planning methods use an order point?
In IFS Cloud only inventory parts with planning method B (Order Point Planning) or C (replenishment level, called Refill Level on the order proposal page) use the order point. Parts on these two methods are not planned by MRP; their supply is created by the Perform Order Proposal activity.
How does IFS Cloud calculate safety stock and order point?
IFS Cloud calculates safety stock, order point and lot size in the Calculate Planning Data job, using part data and the Wilson formula for the lot size. The safety factor comes from the service rate connected to the inventory part through commodity group 2, and the job writes values to the part only when at least one automatic update function is enabled.
Does the IFS Cloud order proposal create purchase orders or requisitions?
The IFS Cloud order proposal creates either a purchase requisition or a purchase order, and the supply type on the inventory part decides which. When the primary supplier is another site set up for multi-site planning, a distribution order is created instead of a purchase order. The proposal can run directly or as a scheduled background job.
Do planned parts in IFS Cloud still need exception monitoring?
Planned parts in IFS Cloud still need exception monitoring, because order point planning assumes that suppliers confirm orders and deliver on time. Stock below minimum, released purchase orders without supplier confirmation and overdue deliveries without a receipt each need a named owner and a daily review, even when every planning parameter is correct.
7.About the author
Dariusz Myśliwiec: 18 years hands-on with IFS (Apps 7.5 to 10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Independent practice based in Kraków, delivered remotely across Europe and globally. You talk to the consultant who does the work, not a sales layer.
I set up inventory planning and purchasing in IFS Cloud and build read-only monitoring for the exceptions that planning leaves behind. For the wider question of which inventory logic belongs in standard and which does not, see Clean Core in IFS Cloud: Purchasing & Inventory.
Selected clients from my IFS work: Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
How many of your parts are below minimum today?
The SCM Exception Scan answers that from your own IFS Cloud data, together with unconfirmed purchase orders in Released and overdue deliveries without a receipt. Five working days, nothing installed in IFS.

Deutsch (Deutschland)
Polski (PL)