Skip to main contentSkip to footer

IFS Cloud Implementation Rescue: Diagnose, Decide, Recover

IFS Cloud implementation rescue for stalled projects: a diagnostic, a keep, repair or rebuild decision per area, and a dated recovery plan.

IFS Cloud implementation rescue · Independent IFS Cloud practice A stalled IFS Cloud project needs a diagnosis, a decision per area and dated gates The go-live…

Read more

IFS Cloud Reporting Tools: Quick Reports to Lobbies

IFS Cloud reporting tools in six layers: Quick Reports, Business Reporter, Lobbies, Power BI, Analysis Models and OData, and when to use each.

Independent IFS Cloud practice · Reporting From the weekly Excel export to a Lobby your team opens first Key takeaways IFS Cloud reporting tools fall into six…

Read more

Parts Not in Any Cycle Count Schedule in IFS Cloud

Parts with no counting class or schedule are never selected for a count, so their balance goes unverified until a pick fails or an audit asks.

Independent IFS Cloud practice · Inventory The part no cycle count ever reaches Cycle counting works on the parts it selects. Depending on how your counting…

Read more

Slow-Moving and Obsolete Inventory in IFS Cloud

Stock with no receipts or issues for weeks ties up cash in IFS Cloud. How to list slow-moving and obsolete inventory before the write-off review.

Independent IFS Cloud practice · Inventory Stock that stopped moving while its balance stayed positive A part that runs short stops a production line, and…

Read more

Inventory Lot Expiry and Shelf Life in IFS Cloud

IFS Cloud records lot expiry dates, but a stock balance may not warn you as one nears. How to list inventory nearing shelf-life before it is a write-off.

Independent IFS Cloud practice · Inventory The stock that expired on the shelf while the balance still looked fine A lot with a shelf-life or expiry date…

Read more

Serial-Tracked Part Missing a Serial Number in IFS

A serial-tracked part can sit in stock with no serial number recorded. The balance exists, but the traceability IFS Cloud promised is already broken.

Independent IFS Cloud practice · Inventory A serial-tracked part that holds stock with no serial number Serial tracking exists so you can answer one question…

Read more

Lot-Tracked Parts With No Lot Number in IFS Cloud

Lot-tracked stock in IFS Cloud carrying no batch number breaks traceability where a recall or audit needs it. Find it read-only before you need it.

Independent IFS Cloud practice · Inventory Stock you cannot trace back to a batch The part is set up for lot tracking, so every unit is supposed to carry a…

Read more

Parts Missing Planning Parameters in IFS Cloud

A part with no reorder point or safety stock in IFS Cloud cannot fire a below-minimum alert, and planning has no parameter to work from. How to list them.

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…

Read more

Reorder Points Set Once and Never Revisited in IFS Cloud

A reorder point set once and never reviewed drifts from real demand. It causes stockouts on one part and slow-moving stock on another. How to list them.

Independent IFS Cloud practice · Inventory A reorder point that stopped matching demand years ago still drives every order A planner sets a reorder point when…

Read more
Abstract illustration on a navy background with the article title: “Lot-Tracked Parts With No Lot Number in IFS Cloud”

Independent IFS Cloud practice · Inventory

Stock you cannot trace back to a batch

The part is set up for lot tracking, so every unit is supposed to carry a batch number that ties it back to when and how it was made or received. Some of it is on hand with no lot number at all. Depending on your setup, that stock can pick, ship, and count like any other in day-to-day handling. When a supplier reports a bad batch, or an auditor asks you to trace a shipment, the one field that answers the question is blank.

Key takeaways

  • A part set up for lot or batch tracking can still hold on-hand stock with no lot number attached, so the traceability the setting promises is missing for that quantity.
  • The gap does not show in day-to-day handling. It shows during a recall, a customer complaint, or a quality audit, when someone needs the batch history.
  • The goods are on hand and usable; the missing piece is the batch identity in the data. A recall scoped by batch number cannot match a unit whose lot field is blank.
  • Stock can land without a lot number through a manual adjustment, tracking switched on later for a part that already had stock, or a migration or interface load.
  • On-hand balances, the part’s tracking setting, and the lot field are recorded in IFS Cloud (worth confirming the exact projections in your environment), so a read-only monitor can list the lot-tracked parts that hold stock with no batch number.

1.Traceability is only real when every unit carries its batch

Turning on lot tracking for a part is a promise: every quantity on hand can be traced to a specific batch, and from that batch to a supplier receipt or a production order. That link answers two questions: where this unit came from, and where the rest of its batch went. A quantity on hand with no lot number cannot answer either.

A blank lot costs nothing until someone needs the batch. A supplier recalls a batch and you cannot say how much of it you still hold or shipped. A customer reports a defect and you cannot trace it back to a source. An auditor asks for the genealogy of a tracked part and the record has a hole in it.

The part looks controlled because the tracking setting is on and the quantities that carry lot numbers are complete. The untracked quantity sits in the same balance as everything else. Whether a pick or a count objects to a missing lot depends on your setup; where nothing does, the gap stays until a recall or an audit asks for the batch.

2.How tracked stock ends up with no batch number

A lot number goes missing where stock enters or changes outside the standard receiving path. Three routes are worth checking in your setup.

Origin What happens Why it survives
Manual adjustment or count-inStock is added by an adjustment or a count correction without a lot number enteredThe balance is right, so the total looks correct and the blank lot is not noticed
Tracking turned on laterLot tracking is enabled on a part that already had stock, and the existing quantity has no batch behind itThe change looks like a setup improvement, and the legacy stock keeps moving as before
Migration or interfaceOpening balances or an integration load stock without carrying a lot number into IFSThe load reconciles on quantity, and lot completeness is not part of the check

In each case the quantity is real and usable. Where your setup does not stop it, it can be picked, shipped, or blended with tracked stock before anyone needs the batch, and each of those moves makes the hole harder to close.

3.Detecting the tracked stock with no batch

On-hand balances, the lot-tracking setting of a part, and the lot number on each quantity are recorded in IFS Cloud and can be read through OData projections without touching a record (the exact projections are worth confirming in your environment). Detection runs on a schedule, with the first scan after the rule is switched on, and compares what the part promises against what its stock carries:

  1. Lot-tracked parts with on-hand stock and no lot number - the part is set for batch tracking, yet a quantity on hand has the lot field empty.
  2. Blank-lot stock that is available to pick - the untracked quantity is in a pickable location and can ship with the gap still in it.
  3. Parts where blank-lot stock is a share of the balance - ranked so a part with a large untracked share is treated ahead of one with a single stray unit.

Because this is a read-only monitoring pattern, it runs beside the warehouse and writes nothing back to IFS. It does not assign a lot, adjust a balance, or block a pick, and it should not: attaching a batch to existing stock is a controlled correction with quality consequences. It adds no object inside the client system, so a release update 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. The warehouse and quality team get the list of tracked parts holding stock with no batch, so the traceability the setting promises can be restored before a recall or an audit asks for it.

4.Rolling it out without noise

  • Rank by untracked share - weight each part by how much of its balance has no lot number, so a part with a large untracked share outranks one stray unit.
  • Lead with pickable stock - blank-lot quantity in a shippable location can leave before it is fixed, so list it first.
  • Start where traceability is regulated - focus first on parts where a recall or audit is a real risk, such as food, pharmaceuticals, or medical devices.
  • Dry-run first - in the first week the rule only logs what it would have listed, and nothing reaches the warehouse team.
  • Read-only by design - standard OData reads only, no lot assigned or balance changed back in IFS and no new object installed in the client system.

See the SCM Automation Pack Book a 30-minute fit call

5.Frequently asked questions

If the quantity is correct, why does a missing lot matter?

A tracked part promises two things: the right quantity and the ability to trace each unit to a batch. A recall, a complaint, or an audit relies on the second. Stock with a correct quantity and no lot number looks right on the balance, and it cannot supply its batch history when someone asks for it.

Can stock with no lot number be traced in a recall?

A recall is scoped by batch number, so a unit whose lot field is blank has no batch to match against. The quantity can only be traced through other records, such as the receipt or the adjustment that created it, and assigning the right batch afterwards is a decision for the warehouse and quality team.

Should the monitor assign a lot number to fix it?

No. Attaching a batch to stock that has none is a decision about what that batch really is, with consequences for quality and traceability, so it belongs to a person. The monitor reads the tracking setting and the lot field through OData and lists the stock that is missing a batch, then leaves the correction to the warehouse and quality team. Nothing is written back to IFS.

Will the monitor list parts that are not lot tracked?

No. A part without lot tracking is not expected to have a lot number, so it is not an exception. The monitor only looks at parts whose own setting says they carry a batch, then lists the on-hand stock where that batch is missing. A human still decides whether each listed quantity is a real gap, because the monitor cannot know which batch the stock belongs to.

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 tracked stock that lost its batch

Tell me which of your parts are lot or batch tracked and how stock is received and adjusted. On a 30-minute fit call we check whether a rule that lists tracked parts holding stock with no batch number 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 before anything reaches your warehouse team.

Book a 30-minute fit call

ROI Calculator

Calculate your return on investment

Input Values

€
€
€

Results

Annual Savings
€ 0
Payback Period
0 months
ROI
0%
Monthly Savings
€ 0

Get Detailed Report

Enter your details to receive a detailed ROI report.