Understand Inventory Status and Occurrence Date in Proposed Orders

Created by Shyam Sayana, Modified on Tue, 14 Oct at 1:00 PM by Shyam Sayana

Purpose

The Inventory Status and Occurrence Date provide planners with real-time visibility into inventory health during replenishment planning. These indicators help identify when a Low Stock or Stock-Out situation will occur within the lead time horizon, enabling planners to take proactive actions before supply shortages impact operations.


TABLE OF CONTENTS


Overview

The replenishment solver engine evaluates inventory availability for every proposed order line during order generation.


It calculates:

  • The Inventory Status — representing the health of the item’s supply during the lead time window.

  • The Occurrence Date — indicating when a Low Stock or Stock-Out situation will begin.

These details are captured in two separate columns in the proposed orders screen.


Lead Time Horizon Evaluation

During each solver run, the application evaluates inventory status across the entire lead time period (e.g., 7, 14, 30, or 90 days).


The solver considers:

  • On-hand inventory

  • In-transit quantities (with receipt dates within the lead time)

  • Forecasted demand during the lead time

  • Safety stock or minimum stock thresholds


The solver excludes future Suggested Order Quantities (SOQs) when computing these values.
Each proposed order generation recalculates these fields to ensure data accuracy.


Inventory Status Definitions


StatusDefinition
On TargetDefinition: Total supply (on-hand + in-transit within lead time) is greater than or equal to total demand and satisfies the safety stock threshold.

InterpretationInventory position is healthy; no immediate action required.
Low StockDefinitionTotal supply during lead time is less than safety stock but greater than zero. The Occurrence Date marks when inventory first drops below safety stock.

 InterpretationInventory expected to fall below safety stock soon; planner may monitor or trigger an order.
Stock-OutDefinitionTotal supply during the lead time is insufficient to meet demand (zero or negative balance). The Occurrence Date marks when the inventory is fully depleted.

InterpretationInventory will run out during the lead time; immediate replenishment is required.
OverstockDefinitionTotal supply during the lead time significantly exceeds demand or maximum stock limits. No proposed orders are created in this case, and the occurrence date remains blank.

InterpretationSupply exceeds expected demand; solver ignores these cases for order generation. 


Note: The solver generates proposed orders only for Low Stock and Stock-Out scenarios.  In a few cases, if might generate orders even when the Inventory status is On Target by considering future requriements.


Occurrence Date Logic

The Occurrence Date identifies when a potential shortage begins within the lead time horizon.


Status TypeLogic
Low StockEarliest date when total supply (on-hand + in-transit) drops below safety stock.
Stock-OutThe Earliest date when the total supply becomes zero or insufficient to meet immediate demand.
On Target / OverstockThe Occurrence Date field remains blank or shows “N/A”.


The date format for Occurrence Date is based on the attribute configuration defined in the Admin App.


User Interface

  • The Proposed Orders screen includes two additional columns:

    • Inventory Status – Displays the calculated status.

    • Occurrence Date – Displays the date when the shortage begins.

  • For Low Stock and Stock-Out, both fields are populated automatically during solver execution.

  • For On Target and Overstock, the occurrence date remains blank or N/A.


Example : Scenrarios

Let's assume the replenishment engine was run on Oct 1, 2025

Example 1: Stockout scenario at the end of the lead time

 

ParameterValue
Lead Time60 days (≈ 9 weeks)
On-Hand Inventory5,100 units
In-Transit Supply (within LT)2,000 units
Total Supply7,100 units
Weekly Demand800 units
Safety Stock500 units
Order policyDue Order

 

Let's assume that the replenishment engine was run on Oct 1, 2025, where the current period is Sep 29, 2025, to Oct 06, 2025

 

WeekStart dateEnd DateStarting SupplyDemandEnding SupplyRemarksInventory StatusOccurrence date
Week 109/2910/067,1008006,300Sufficient supplyOn Target
Week 210/0710/146,3008005,500Sufficient supplyOn Target
Week 310/1510/225,5008004,700Sufficient supplyOn Target
Week 410/2310/304,7008003,900Sufficient supplyOn Target
Week 510/3111/073,9008003,100Sufficient supplyOn Target
Week 611/0811/153,1008002,300Sufficient supplyOn Target
Week 711/1611/232,3008001,500Sufficient supplyOn Target
Week 811/2412/011,500800700Barely above safety stock (500)On Target
Week 912/0212/09700800-100A supply shortage occurredStockoutDec 02, 25


Inventory Status: Stockout
Occurrence Date: 02 Dec 2025
Explanation: The supply of 7,100 units fulfilled demand until Week 8; however, in Week 9, a shortage of 100 units occurred, resulting in a stockout exception.


Example 2: Stockout scenario - Supply doesn't meet the demand during the lead time.

 

ParameterValue
Lead Time60 days (≈ 9 weeks)
On-Hand Inventory5,000 units
In-Transit Supply (within LT)0 units
Total Supply7,100 units
Weekly Demand800 units/Week (Weeks 1–4), then 1,000 units/week (Weeks 5–9
Safety Stock600 units
Order policyDue order


Computation

 

WeekStart dateEnd DateStarting SupplyWeek DemandEnding SupplyRemarksInventory StatusOccurrence date
Week 109/2910/065,0008004,200Sufficient supplyOn Target
Week 210/0710/144,2008003,400Sufficient supplyOn Target
Week 310/1510/223,4008002,600Sufficient supplyOn Target
Week 410/2310/302,6008001,800Sufficient supplyOn Target
Week 510/3111/071,8001000800Barely above safety stock (600)On Target
Week 611/0811/158001000-200StockoutStock outNov 08, 2025
Week 711/1611/23-2001000-1,200StockoutStock out
Week 811/2412/01-1,2001000-2,200StockoutStock out
Week 912/0212/09-2,2001000-3,200StockoutStock out


Note: Negative supply is just for representation to demonstrate that there is 0 or negative supply. Hence considered it as Stockout scenario



Inventory Status: Stockout

Occurrence Date: Nov 08, 2025 (Start of Week 6)
Explanation: Supply remains healthy until week 5. As there is no new supply, the remaining supply has fallen below 0, causing a stockout situation.

Recommendation by replenishment engine: The engine creates a proposed order with Order Date = Oct 1, 2025.


Example 3: Low Stock scenario - Supply meets demand. However, supply is below the Min-Max Minimum inventory.


ParameterValue
Lead Time21 days (≈ 3 weeks) 
On-Hand Inventory3,000 units
In-Transit Supply0 units
Weekly Demand700 units
Min-Max Minimum Inventory 500 units
PolicyMin-Max Inventory


Computation


WeekStart dateEnd DateStarting SupplyDemandEnding SupplyRemarksInventory StatusOccurrence date
Week 109/2910/063,0007002,300Sufficient supplyOn Target
Week 210/0710/142,3007001,600Sufficient supplyOn Target
Week 310/1510/221,600700900Supply barely above safety sock (500 units)On Target
Week 410/2310/30900700200Supply falls below safety stockLow StockOct 23, 2025



Inventory Status: Low Stock
Occurrence Date: Oct 23, 2025 (Start of Week 4)
Explanation: By week 4, the ending supply falls below the Min-Max Minimum inventory (i.e., 500 Units). The solver flags this as a Low Stock status and creates a Proposed order with an order date of Oct 07, 2025, with a Need by date as Oct 23, 2025, with SOQ = Min-Max Maximum inventory.


Example 4: Sufficient supply to meet demand during lead time.



ParameterValue
Lead Time14 days (≈  2 weeks)
On-Hand Inventory3,000 units
In-Transit Supply0 units
Weekly Demand700 units
Min-Max Minimum Inventory 500 units
PolicyMin-Max Inventory


Computation


WeekStart dateEnd DateStarting SupplyDemandEnding SupplyRemarksInventory StatusOccurrence date
Week 109/2910/063,0007002,300Sufficient supplyOn Target
Week 210/0710/142,3007001,600Sufficient supplyOn Target
Week 310/1510/221,600700900Supply barely above safety sock (500 units)On Target
Week 410/2310/30900700200Supply falls below safety stockLow Stock


Inventory Status: On Target
Occurrence Date: NA
Explanation: By week 4, the ending supply falls below the Min-Max Minimum inventory (i.e., 500 Units).

  • However, the lead time is 14 days (≈  2 weeks). 
  • This means there is sufficient inventory to meet the demand and Safety stock requirements till Week 3.
  • However, the replenishment engine creates a proposed order for Week 4 (beyond lead time), as there is potential for a low stock scenario. This applies to both Due Order and Min-Max Policy.

Key Rules and Notes

  1. Lead Time Boundaries:
    • Only in-transit receipts arriving within the lead time window are included in the computation.
      Future receipts beyond lead time are ignored.
  2. Future SOQs:
    • Suggested orders are excluded from both inventory status and occurrence date logic.
  3. Status Triggers:
    • Only Low Stock and Stock-Out statuses trigger new proposed orders.
  4. Automatic Recalculation:
    • The solver recalculates inventory status and occurrence date each time proposed orders are generated to ensure accurate results.

Business Impact

  • Identify potential stock issues earlier.

  • Prioritize replenishment efforts by urgency.

  • Avoid unnecessary order duplications or overstocking.

  • Increase the overall responsiveness of the replenishment process.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article