A pallet can be physically present, correctly counted and still be unavailable to sell. If its remaining shelf life is too short for a customer, route or production plan, it is not useful stock. That is why operations teams ask: can WMS manage expiry dates? The answer is yes, provided expiry control is configured as a live warehouse process rather than a date held in a spreadsheet.
For manufacturers, wholesalers, distributors and retailers handling food, drink, cosmetics, chemicals, healthcare products or date-sensitive components, expiry management protects more than stock value. It supports product quality, customer compliance, recall readiness and the confidence that the right inventory is being dispatched first.
Can your WMS Manage Expiry Dates Reliably?
A capable warehouse management system can record expiry dates at receipt, associate them with a batch or lot, apply stock rotation rules during allocation and picking, and prevent unsuitable stock from being shipped. It can also provide alerts and reports so teams can act before inventory becomes a write-off.
The key distinction is between storing a date and controlling a workflow. Basic stock systems may allow an expiry date to be entered against an item. A warehouse-led WMS uses that information to direct decisions on the floor: which pallet is put away, which location is picked, which customer order can be fulfilled and which stock must be quarantined or reviewed.
The result is a clearer answer to a question that regularly causes friction between warehouse, customer service and finance teams: what stock do we have that is genuinely available to sell?
What Expiry Date Control Looks Like in Practice
Expiry management begins at goods-in. When a receipt is scanned, the operator captures or confirms the product, batch or lot number, quantity and expiry date. Depending on the product and supplier process, that data may be received electronically from the ERP or captured from a barcode on the case, pallet label or supplier documentation.
The WMS then creates inventory with its own identity. Two pallets of the same SKU are not treated as interchangeable if they have different batch numbers or expiry dates. This matters when one delivery expires in four months and another in fourteen months. A simple on-hand quantity masks that difference; a WMS makes it visible.
At putaway, the system can apply rules designed around the operation. It may consolidate like batches, keep lots separated, direct stock to temperature-controlled areas or restrict a particular batch to a defined zone. Location-level visibility means a supervisor can see not only the quantity and expiry status, but where the inventory sits and whether it is already allocated.
FEFO is usually the right rule, but not always
For most date-controlled products, FEFO – first expired, first out – is more appropriate than FIFO – first in, first out. FIFO assumes the earliest receipt should leave first. FEFO selects stock with the earliest acceptable expiry, regardless of when it arrived.
That difference becomes significant when suppliers deliver stock with varying shelf life. A newer receipt may need to ship before older stock if its expiry date is sooner. By following FEFO, the warehouse protects saleable life and reduces the risk of overlooked inventory becoming obsolete in a back location.
However, FEFO should not be applied blindly. Some customers require a minimum remaining shelf life, such as 90, 180 or 365 days. Some products are subject to customer-specific technical agreements. Others may need to be held until quality checks are completed. The WMS rules must reflect those operational realities, rather than forcing one generic rotation method across every item.
Set Shelf-Life Rules at the Right Level
The most effective expiry configuration is specific enough to control risk without creating unnecessary exceptions. Businesses can define minimum shelf-life requirements by SKU, product family, customer, order type or destination. A domestic retail order and an export order, for example, may have very different acceptable shelf-life thresholds because of transport time and the customer’s receiving policy.
When an order is released, the WMS checks whether a batch meets the rule before allocating it. If it does not, the system can exclude it from normal pick selection. This prevents a picker from doing the logical thing on the floor – taking the nearest pallet – when that pallet will later be rejected by the customer.
This is where warehouse and transport planning need to work together. A product might technically meet its minimum shelf-life rule when picked, but not when it reaches the delivery point after consolidation, loading and a multi-drop lorry route. Operations should agree whether shelf-life validation is based on despatch date, expected delivery date or another defined control point.
Use WMS Expiry Alerts Before Stock Becomes a Problem
Expiry control should not only intervene at the point of pick. By then, the best opportunity to recover value may have passed. Exception reporting allows warehouse and commercial teams to see stock approaching its expiry window and decide what to do next.
A useful approach is to work with alert bands, such as stock expiring within 30, 60 or 90 days. The correct windows depend on the product’s normal sales cycle, lead times and contractual shelf-life requirements. A short-life chilled product may need daily attention, while industrial materials may need a much longer planning horizon.
Alerts create options. The business may prioritise stock in a promotion, transfer it to a customer with a suitable requirement, use it in production, return it to the supplier where agreed, or move it into a controlled hold status. If no action is appropriate, the WMS can block the stock from allocation so it is not accidentally despatched.
That discipline also improves financial visibility. Rather than discovering obsolete inventory during a periodic stocktake, finance and operations can quantify exposure while there is still time to reduce it.
Traceability Depends on Accurate Data Capture
A WMS is only as reliable as the data entering it. Expiry control fails when operators key dates manually without validation, labels are unreadable, batches are mixed on a pallet, or stock is moved without scanning. These are process design issues, not simply software issues.
Barcode scanning on receipt and during internal movements reduces the reliance on memory and paperwork. Where suppliers provide GS1 barcodes containing batch and date information, the process can be faster and more consistent. Where they do not, a well-designed receiving screen should require the critical fields and apply sensible checks, such as rejecting an invalid date format or a date that falls outside the agreed product shelf life.
Physical labelling matters too. Warehouse teams need to distinguish batches quickly at the point of putaway, replenishment, picking and loading. If a picker has to stop and read a faint supplier label on a mixed pallet, the process is vulnerable. Clear internal pallet labels, consistent scan points and defined handling rules make the system practical under real operating pressure.
Batch Holds, Recalls and Quality Exceptions
Expiry control naturally sits alongside batch traceability. If a supplier reports a quality issue, the warehouse should be able to identify every location holding the affected batch, its current status, related receipts and any orders already despatched. This supports a controlled response rather than a broad and costly search through paper records.
A WMS can place a batch on hold immediately, preventing it from being allocated or picked while the issue is investigated. The same process is valuable for damaged goods, temperature excursions, failed inspection or customer returns awaiting assessment.
There is a trade-off here. Tighter controls reduce the chance of an incorrect despatch, but overly broad holds can restrict available stock and disrupt service. Clear authority levels, reason codes and review processes help ensure that holds are applied deliberately and released only when the evidence supports it.
Integration Stops Dates Being Re-Keyed
Expiry information has value beyond the warehouse. ERP, quality, customer service and purchasing teams may all need a trusted view of batch status and remaining shelf life. Integration avoids the familiar problem of one system showing stock as available while another team has manually marked it as unsuitable.
For businesses running platforms such as Sage Intacct, SAP Business One, Microsoft Dynamics or Acumatica, the integration design should establish which system owns product master data, batch details, order demand and stock status. The WMS should receive the information needed to execute warehouse controls in real time, then return confirmed receipts, movements, allocations and despatches without rekeying.
This does not mean every date rule must be configured in every system. Usually, the WMS should own the operational selection and scan-led execution, while the connected business systems retain the information they need for planning, finance and customer service. The priority is one agreed inventory truth, not duplicated logic.
Questions to Ask Before Configuring Expiry Management
Before selecting or configuring a WMS, map the decisions your team currently makes about date-controlled stock. Ask whether dates are captured by batch, case or pallet; whether partial pallets can contain mixed batches; what minimum shelf life each customer expects; and who is authorised to release held stock.
Also examine exception handling. What happens when a supplier sends stock with less remaining life than agreed? Can a picker override FEFO, and if so, is the reason recorded? How are returns assessed before they re-enter available inventory? The answers shape the configuration, training and reporting required.
A system demonstration should show these scenarios from receipt through to despatch, not just a stock screen containing an expiry-date field. The practical test is whether the software makes the compliant action the easiest action for the person holding the scanner.
Smarter Warehouse approaches expiry management as part of the wider warehouse operating model: receiving discipline, batch visibility, allocation rules, mobile execution and integration all need to work together. When those foundations are in place, expiry dates stop being a retrospective reporting problem and become a controllable part of daily fulfilment.