Deutsch (Deutschland) 
Polski (PL) 
Independent IFS Cloud practice · Warehouse
Received stock that waits in inspection while orders wait for it
Goods received into quality inspection, or onto a blocked status, stay out of available inventory until someone releases them. Physically the part is on the shelf. Depending on your setup, it does not count toward what you can promise, so planning may reorder it and a customer order may wait for a part that already arrived. The receipt date is recorded in IFS Cloud, and the cost comes from nobody tracking how long the release takes.
Key takeaways
- Stock held in quality inspection is on hand but, depending on your setup, outside availability until someone releases it, and whether anything in your setup chases the release is worth checking.
- The quantity exists, so a minimum-stock rule that reads on-hand stays quiet. The cause is an unfinished inspection or release step.
- Nothing fails visibly while the hold stays open, so the first sign is a stock-out or a count that finds inventory that was there all along.
- The inspection status and its date can be read through OData (the exact projection is worth confirming in your environment), so ageing in QA can be listed before stock-take.
A failed pick, an empty location or a line that will not ship announces itself. Stock in quality inspection gives no such signal, because from the receiving side the job looks done: the goods came in and the receipt posted. The step that did not happen is the move from inspected to available. Until it completes, the stock is real to the shelf and invisible to the plan, and in that gap working capital sits idle and orders wait without cause.
1.How does received stock stay stuck in inspection?
When goods arrive against a purchase order for a part set up with an inspection step, the stock is received and put somewhere, but it is held on an inspection or blocked status until a person confirms it passed and releases it to available inventory. That release is a deliberate action, and a deliberate action is forgotten when the person who owns it is busy, away, or unclear that the task is theirs. Which projection carries the inspection status is worth confirming in your environment.
So the stock waits, with no failed inspection behind it, only an open step. The goods read as on hand to a physical count and, depending on your setup, as unavailable to planning. A first article awaiting sign-off, a lot pending a certificate, a routine check nobody got back to: each is a legitimate hold that outlives its reason.
2.What stock stranded in QA actually costs
The cost is capital you already spent sitting where it cannot earn, plus the decisions the rest of the system makes as if that stock did not exist.
- Idle working capital - money is committed to goods that cannot be sold or consumed while they wait for a release.
- Needless reordering - planning sees the part as unavailable and may raise another order for stock already on the shelf.
- Orders that wait - a customer or production order can be short of a part that physically arrived, because it never became available to allocate.
- Surprise at count - the stranded quantity surfaces at a cycle count or stock-take, long after it could have been useful.
A quality hold keeps a paid-for part on hand and outside availability, so an unread hold behaves like an empty shelf.
Illustrative only: a part held a few days past a routine check costs little, while the same hold left open for weeks on every receipt of a part ties up real availability and real cash. The threshold is the number of days you choose to allow.
3.Seeing the hold in IFS Cloud
On-hand quantity, its availability status, and the date it entered inspection are readable through OData projections without writing anything back. The exact projection and field names for the inspection or blocked status are worth confirming in your environment before a rule is built. Turning that into a watch list is a scheduled read of two things:
- Stock in inspection past a threshold - any quantity held on an inspection or blocked status for longer than a number of days you choose, ranked by value so the most capital surfaces first.
- Held stock a demand is waiting on - parts on hold where an order or plan needs the same part, the case where the shelf and the shortage disagree.
The status is already in the system. What is missing is a scheduled read that lists the holds that have outstayed their reason.
4.The manual check versus a systematic one
A quality lead clears the holds they can see. An open inspection makes no noise, and the one that ages longest is the one nobody remembers is open. A habitual check depends on the habit holding on the busy days, which are the days holds pile up.
| Manual QA follow-up | Systematic monitor | |
|---|---|---|
| Trigger | Someone notices a hold or hits a shortage | Every held quantity aged against a threshold each day |
| What surfaces | The holds people happen to remember | Every hold past its allowed days, ranked by value |
| Demand link | Hard to see which holds block an order | Held stock a live demand is waiting on is flagged |
| Continuity | Depends on who is checking that day | Runs the same regardless of workload |
| IFS footprint | None, but nothing tracks the ageing | Read-only; no object added to IFS Cloud |
Because it is a read-only monitoring pattern, it never writes back to IFS Cloud and 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 lists the held stock that has aged and leaves the inspection, the release, or the escalation with the person who owns quality.
5.Rolling it out without adding noise
- Start with value - rank held stock by capital tied up, so the first list is the money worth freeing, not every hold.
- Dry-run a full period - log what would have been flagged before a single alert reaches the quality team.
- Two views - holds aged past a threshold, and holds that block a live demand, because they need different urgency.
- No upgrade footprint - standard OData reads only, so nothing is installed inside IFS Cloud.
Related reading
6.Frequently asked questions
Does IFS Cloud already show stock held in quality inspection?
The status is visible when you open the part or location. Whether anything in your setup watches how long a hold has been open, or tells you when it has passed the number of days you allow, is worth checking; where nothing does, the first notice can be a lost order.
How is this different from stock below minimum?
Stock below minimum means the quantity on hand is too low, and the fix is replenishment. Stock in quality inspection means the quantity arrived but is held outside availability, and the fix is a release by the person who owns the inspection.
What data does IFS Cloud need to expose to flag it?
A rule needs on-hand quantity, its availability or inspection status, and the date it entered that status, read through OData projections. The exact projection and field names for the inspection status are worth confirming in your environment. Reading them on a schedule is enough to list stock held past a chosen number of days, ranked by value.
Does monitoring QA holds write anything back to IFS Cloud?
No. The pattern reads status and dates through standard OData and raises alerts outside IFS. Nothing is written back, so there is no upgrade footprint and no new object inside the client’s system.
7.About the author
Dariusz Myśliwiec has 18 years hands-on with IFS (Apps 7.5–10 and IFS Cloud). He is an IFS Certified Associate Consultant and PRINCE2® 7 certified. Based in Kraków, he delivers 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.
Turn received stock into available stock on time
Tell me where your receipts wait in inspection. On a 30-minute fit call we check whether a rule that reads held stock and its ageing 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 period before a single alert reaches the quality team.
