UC-499
Improve Terminal Stock and Markdown to keep the right items available
Fills the Stores page in TFS LENS: which stock records are wrong, and which counts fix them.
TBDBuild Duration
XXXXIndicative ROI
XXXXBuild Cost
XXXXValue
The Challenge
The opportunity is to eliminate Selling a bottle that is not in the building, a Christmas gift that becomes a refund, and a count that finds nothing. The proposed workflow is source-linked, but the current operating baseline and financial value remain illustrative until validated with the client.
How It Works
- One engine scores every store and line record for the probability it is wrong, reading receipt patterns, count history, sales velocity, transfer lag and store tenure.
- It holds availability back before the site or the app can sell it.
- Then it tells each store which counts are most likely to find a discrepancy today, instead of counting everything and finding nothing.
What It Removes
- Selling a bottle that is not in the building
- A Christmas gift that becomes a refund
- A count that finds nothing
Input Data RequirementsInventory balances, demand history, purchase orders, lead times, usage, locations and service levels
Output FormatDashboard showing which stock records are wrong, and which counts fix them.
“If the site says it is in my store, it is in my store.”