Deutsch (Deutschland) 
Polski (PL) 
Independent IFS Cloud practice · Inventory
A part with no threshold can run out without any alert firing
A replenishment alert works by comparing a stock level against a threshold: below minimum, under the reorder point, beneath safety stock. A part whose threshold was never set has nothing to compare against, so no alert can fire on it, and planning has no parameter to plan from (worth confirming in your setup how your planning run treats such a part). The part is not low. It does not appear in any threshold report, and it stays out of sight until someone goes to pick it and the shelf is empty.
Key takeaways
- A part with no reorder point, no min/max, and no safety stock cannot generate a below-minimum alert, because the alert needs a threshold and there is none.
- Planning calculates replenishment from planning parameters. A part without them has nothing to calculate from, and depending on your setup the gap may produce no message.
- Threshold monitoring watches every part that has a minimum. The parts with no minimum are the ones outside it.
- The gap enters with new part numbers, a data migration, or a planner leaving, so each of those events is a point to check.
- The parameters are readable through OData (the exact projections are worth confirming in your environment), so a read-only monitor can list every planned part with missing or zero settings before the stockout.
1.An alert can only fire on a threshold that exists
Threshold monitoring watches a number and warns you when that number crosses a line you drew. Draw the line at the reorder point and you get a reorder alert. Draw it at safety stock and you get a safety-stock warning. The mechanism depends on the line being there.
A part with no planning parameters has no line. On-hand can fall from a comfortable buffer to zero and every threshold report stays quiet, because there is nothing for the stock level to cross. A breach of a limit that was never defined cannot be detected, whatever the quality of the alerting.
A manual adjustment without a reason leaves a number that can be questioned. A missing parameter leaves no number at all, and with nothing on the screen to look at, the absence is harder to see.
2.How a part ends up with nothing set
A part ends up unplanned through three mechanisms, each at the edge of normal work.
| Origin | What happens | Why it survives |
|---|---|---|
| New part number | The part is created and used before planning parameters are filled in | It transacts normally, so it looks complete until it needs replenishing |
| Data migration | Master data is loaded without the reorder point, min/max, or safety stock that existed in the old system | The part exists and issues fine, so the missing settings are not obvious at go-live |
| Planner turnover | The person who curated the parameters leaves and the maintenance stops | Existing parts keep their old settings while new ones go unmaintained |
In each case the part transacts without a problem until the day it has to be reordered, and the gap surfaces as a stockout on a part that should have been planned. The same lack of maintenance can also leave a part with a reorder point that no longer matches demand, which ends as slow-moving stock that no rule retires.
3.Detecting the absence of a setting
Planning parameters per part and site are readable through OData projections without touching a record. Detection inverts a normal alert: instead of watching for a value that crossed a line, it watches for the line that is missing:
- Planned parts with no reorder point or min/max - items flagged for planning that carry no threshold at all, the parts on which no replenishment alert can fire.
- Parameters set to zero where zero makes no sense - a safety stock or reorder point of zero on a part with recurring demand has the same effect as no setting, and is harder to spot because a value is present.
- Newly created parts still transacting without settings - parts that have started moving but were never completed, caught in the window between first use and first reorder.
Because this is a read-only monitoring pattern, it runs beside the warehouse and writes nothing back to IFS. It adds no object inside the client system, so an R1 or R2 release leaves nothing of ours in your IFS to retest. Before each release I check that the standard projections it reads still match, as part of the subscription. It does not set the parameter, because choosing a reorder point is a planning decision. It hands a planner the list of parts that have no threshold, so the decision gets made before the stockout.
4.Rolling it out without noise
- Start with parts that have real demand - a missing parameter costs most on parts that move, so rank by recent issue history.
- Dry-run the full list first - see the size of the gap before anyone is asked to fix it, so the first day is not a long list of parts.
- Treat zero as a value to question - a zero threshold on a moving part is a decision worth confirming, and it does not complete the setup.
- Read-only by design - standard OData reads only, nothing written back to IFS and no new object installed in the client system.
Related reading
5.Frequently asked questions
Why does a part with no reorder point never raise an alert?
A replenishment alert compares the stock level against a threshold. If the reorder point, min/max, and safety stock are all absent, there is no threshold to compare against, so the condition that triggers an alert can never be met. The part stays quiet however low it falls.
Is a zero setting the same as a missing one?
For a part with recurring demand, a zero setting has the same effect as a missing one. A safety stock or reorder point of zero behaves like no threshold, because the stock level does not drop below zero. It is harder to notice than a blank field, because a value is present and the record looks complete.
How is this different from a below-minimum alert?
A below-minimum alert assumes a minimum exists and warns you when stock drops under it. A part with no minimum set cannot raise that alert at all. The first watches parts that have a threshold, and a missing-parameter check lists the parts that have none.
Should the monitor fill in the missing parameters automatically?
No. Choosing a reorder point or safety stock is a planning decision that depends on demand, lead time, and cost. The monitor reads parameters through OData and lists the parts that have none, then leaves the decision with a planner. Nothing is written back to IFS.
6.About the author
Dariusz Myśliwiec brings 18 years hands-on with IFS (Apps 7.5–10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Based in Kraków, delivering remotely across Europe and globally as an independent practice, so you talk to the consultant who builds it.
Selected clients: 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.
Find the parts with no threshold set
Tell me which sites carry your most important parts. On a 30-minute fit call we check whether a rule that reads planning parameters per part and site fits your data. The SCM Automation Pack runs three rules today (unconfirmed purchase orders, late deliveries, stock below minimum), so this would be an additional rule built to order, with a dry-run week so you see the size of the gap before anyone is asked to fix it.
