How a date gets set: the three modes
An item’s shelf-life policy has one mode.NotManaged is the default — no expiry is tracked, and choosing it removes any existing policy. The other three modes each decide how the expiration date is computed:
When the clock starts
For Fixed Duration, the start event depends on how the item is sourced:- Made items start at a job operation finishing (or starting) — optionally gated to a specific trigger process (say, Pasteurise or Packaging), with Before or After timing. Sub-assemblies stamp their own batches from their own operations.
- Bought items start from the receipt’s posting date, not “today”, plus the configured days.
AllInputs
(the default) or ManagedInputsOnly.
Policy fields
The policy lives on the item’s pick method:What happens to expired stock
A company-wide expired-entity policy governs every material issue and stock transfer:
Picking is -aware: available tracked entities are offered earliest-expiry-first, so the oldest stock
leaves first by default. A near-expiry warning highlights batches approaching their date in the tracked-entity
lists; set its lead time (in days) in company settings. Leaving it blank turns the warning badges off.