An expiry report should tell you what can still be sold
For Inventory managers and supply-chain heads · Compare approaches
TL;DR — what you’ll learn
- Calculate exposed quantity after assigning eligible demand to each lot once.
- Keep confirmed orders separate from forecast coverage so uncertainty remains visible.
- Rank the work by the last useful action date and commercial exposure.
- Give every intervention an owner, an approval path and a check on its actual outcome.
A warehouse manager receives a spreadsheet of thirty lots expiring this month. Several already have confirmed orders. One large lot expires next month but has no customer likely to accept it. The report looks urgent without separating the work that is already covered from the stock that needs attention.
What should a food expiry risk report include beyond expiry dates?
Compare each lot's remaining quantity with demand that can actually use it before the selling window closes. Show the unmatched balance, its owner and the next decision. Days to expiry alone cannot establish commercial exposure.
- 01List eligible stockLot, quantity and usable window
- 02Allocate feasible demandAvoid counting demand twice
- 03Review exposed quantityOwner and available optionsIs the proposed action supported?YesRecord the actionNoKeep the quantity exposed and obtain the missing demand or disposition evidence.
- 04Record the actionTrack the remaining exposure
Illustrative information flow. The article explains the evidence, exceptions and responsible decisions. Diagram: NextEdge Labs.
Allocate demand once
Suppose a released lot contains 600 cases. Confirmed eligible orders require 220, and an additional 150 cases of forecast demand may fit its selling window. The illustrative exposure is 380 cases against confirmed orders alone, or 230 if the forecast materialises. Show both views. A forecast is not a reservation, and presenting only the optimistic number hides the uncertainty.
If two lots serve the same demand, allocate that demand in the report's agreed order before calculating the remainder. Subtracting the same 150 cases from every lot creates reassuring totals that cannot all be achieved.
Expiry is only one boundary
Include customer remaining-life requirements, transit time, release status and any business-approved dispatch cutoff. Microsoft's shelf-life documentation is a useful reference for customer-specific sellable days. Product safety and handling decisions remain with the appropriate quality owner; the dashboard must not extend an expiry date to make a sales opportunity fit.
| Field | Decision it supports |
|---|---|
| Unmatched cases by lot | How much stock needs another route to demand? |
| Latest eligible dispatch date | When must the team act? |
| Confirmed and forecast coverage | How certain is the proposed consumption? |
| Action owner and review date | Who is resolving the remaining exposure? |
Source: Microsoft Learn · Sellable-day requirements. Reference details
A lot can be urgent before it is near expiry
Imagine two illustrative lots worth ₹60,000 each. The first has five days left and a confirmed order that accepts it tomorrow. The second has twenty days left, but its usual customer requires eighteen days on receipt and transport takes two days. The second lot's normal commercial route is closing now. Sorting by expiry alone would put it below the lot that already has a solution.
Build the working list around the latest feasible action date. Label that date as a planning calculation and show its assumptions. A new transport commitment or customer requirement may change it. Where no approved requirement exists, display the missing input rather than silently inventing a standard number of days.
Account for the cost of the proposed rescue
A transfer may save the stock but incur extra freight, handling and a discount. A transparent comparison shows the expected contribution from the alternative route alongside those incremental costs. It also records whether the demand is firm. Avoid presenting the full sales value of moved stock as money saved; the transfer may merely move the exposure to a different warehouse.
For example, moving 100 cases to an outlet is not a resolved outcome until there is a credible consumption plan. Keep the lot on the exposure view with its new location and expected use. If a planner cancels a later replenishment because of the transfer, link that action too. Otherwise the receiving outlet may be overstocked again when its regular delivery arrives.
Close the loop after the alert
Use a small set of outcome codes that reflect real events: sold through an eligible order, consumed in an approved production run, transferred with demand attached, written off, or still unresolved. Preserve the original exposed quantity and the final disposition. This lets the team learn whether it had enough lead time and whether the chosen action worked.
Review repeated causes separately from individual lots. An oversized purchase minimum, optimistic launch forecast or habitual overproduction requires a policy change. A daily report can reveal those patterns; it cannot resolve them by repeatedly asking a salesperson to find another buyer. At a weekly review, choose one recurring cause to investigate and record the changed purchasing or planning rule.
Turn the report into a short working list
Sales may propose a different customer, planning may reduce the next run, and procurement may defer an incoming order. Record those proposals separately from approved actions. A discount, transfer or production change needs its normal commercial approval, even when the alert was generated automatically.
AI can rank plausible interventions or summarise unresolved cases, but begin with transparent allocation rules and an explicit unknown category for incomplete data. Review whether the report identified stock early enough to change an outcome. Counting alerts or colouring more rows red says little about its usefulness.
Summary
A useful expiry report is a working account of unmatched stock. It shows what can still be sold, when the opportunity closes and who is changing the situation. Its value comes from earlier decisions and honest demand allocation, rather than the number of warning rows it produces.
What to do next
- Rebuild the report for one product family using lots, free quantities and customer receipt requirements.
- Separate certain demand from possible demand and review the exposed balance with planning and sales.
- Record the outcome of each action so the next review can distinguish resolved exposure from expired stock.
Compare this workflow with your current setup
Share the step that takes the most manual work, the systems involved and the exceptions your team handles. That gives us a concrete starting point for comparing approaches.
Sources and further reading
Sources checked 15 October 2026. The worked examples and software evaluation suggestions are NextEdge Labs’ editorial analysis.
- Shelf life planningMicrosoft Learn · Dynamics 365 Supply Chain Management documentation, accessed October 2026
Product documentation explaining shelf life and customer sellable-day requirements. A software example, not a food safety specification.
Visual credits
AI-generated illustration created for NextEdge Labs; it does not depict a client facility. Workflow diagram by NextEdge Labs. Icons from Lucide (ISC licence).
