Expiry dates and lot markings: practical rules for handling shelf-life products on the unit
Expiry dates and lot markings: practical rules for handling shelf-life products on the unit
A batch arrives with expiry dates printed in three different formats across the same SKU. Two units show lot codes that don't match the supplier's manifest. One carton has expiry dates that are partially obscured. If receiving accepts these units without flagging the inconsistencies, the inventory becomes a liability that compounds with every pick. Shelf-life handling isn't about following a calendar — it's about creating proof that the right unit left at the right time for the right reason.
When products carry expiry dates or lot markings, the fulfillment operation shifts from "move inventory" to "manage time-sensitive assets." The difference shows up in how units are received, where they're placed, which gets picked first, and what documentation travels with each order. The rules aren't complex, but they must be consistent: what gets captured at receiving, how rotation happens during storage, and what proof prevents disputes when something goes wrong.
Why Shelf-Life Handling Fails Without Unit-Level Rules
The clearest sign that shelf-life protocols are breaking down: orders going out with mixed expiry dates from the same SKU, or worse, products that expire before the customer receives them. This happens when the operation treats shelf-life as a sorting problem rather than a capture-and-proof system.
Most failures trace to three missing controls. First, inconsistent lot capture at receiving means the system doesn't know what actually arrived or when it expires. A shipment shows different date formats, partial markings, or lot codes that don't reconcile with the paperwork, but receiving accepts the units anyway to maintain throughput. Second, unclear rotation rules leave pickers guessing which units to select, leading to random selection that ignores expiry logic. Third, no proof system means when a customer receives expired product or questions the remaining shelf-life, there's no trail showing which specific unit was picked and why.
The operational impact becomes visible during peak periods when speed pressure overrides verification. Pickers grab the nearest unit instead of following rotation logic. Exception handling defaults to "process it anyway" rather than clarifying which rule applies. Customer complaints about shelf-life arrive without a way to trace the specific unit or validate whether the pick was correct. Each incident requires investigation time that the operation doesn't have, and each unclear case sets a precedent that weakens the entire protocol.
FIFO vs FEFO: When to Use Which Rotation Logic
First In, First Out (FIFO) moves inventory based on arrival sequence, regardless of expiry dates. First Expired, First Out (FEFO) prioritizes units by expiry date, regardless of when they arrived. The choice depends on the product type, regulatory requirements, and how much expiry variation exists within the same SKU.
FIFO works for products with consistent shelf-life where arrival date closely correlates with expiry date. When a SKU arrives in regular batches with predictable expiry patterns, and the business can accept some expiry variation in outbound orders, FIFO provides simpler picking logic. The system tracks arrival date and picks the oldest received inventory first. This approach handles volume efficiently and reduces picker decision-making during busy periods.
FEFO becomes necessary when expiry dates vary significantly within the same SKU, when regulatory requirements mandate shortest-expiry-first rotation, or when customers specifically request maximum remaining shelf-life. Food products, cosmetics, pharmaceuticals, and anything with regulatory oversight typically require FEFO. The system must capture actual expiry dates at unit level and direct pickers to the shortest-dated inventory first.
A beverage distributor receives energy drinks with expiry dates ranging from eight months to fourteen months on the same delivery. Under FIFO logic, a unit that arrived first but expires last could sit in inventory while shorter-dated units from later deliveries get picked first. Under FEFO logic, the shortest-dated units move first regardless of arrival sequence, maximizing the shelf-life that reaches customers.
The critical decision point: if your product's regulatory classification requires expiry-based rotation, FEFO isn't optional. If customer expectations include maximum shelf-life (common in food retail), FEFO prevents returns and complaints. If neither applies and arrival patterns correlate with expiry, FIFO simplifies operations without meaningful risk.
Lot and Expiry Capture at Receiving
Effective shelf-life handling starts with systematic capture during receiving. Every unit must be verified for lot code and expiry date before entering inventory, with discrepancies flagged immediately rather than processed as exceptions later.
The receiving protocol begins with manifest comparison: what lot codes and expiry dates were expected versus what markings appear on actual units. Units with missing, illegible, or non-conforming markings get segregated for clarification before acceptance. This prevents contaminating clean inventory with units that can't be tracked or rotated properly.
Lot code capture requires consistent formatting in the inventory system. Whether the supplier uses alphanumeric codes, date-based systems, or proprietary formats, the system must store the exact marking as printed on the unit. Standardization attempts that translate supplier codes into internal formats often introduce errors during busy receiving periods. The safest approach: capture lot codes exactly as marked, then map to supplier documentation during reconciliation.
Expiry date capture follows the same exact-match principle. Suppliers print dates in various formats — MM/DD/YYYY, DD/MM/YYYY, Julian dates, or text descriptions like "Best By MAR 2025." The system stores the format as printed, then converts to a common expiry date for rotation logic. Attempting format conversion during receiving creates transcription errors when volume pressures mount.
A vitamin supplement arrives with lot codes printed in small text on bottle shoulders and expiry dates embossed on bottle caps. The manifest shows lot "VT2024-089" but units show "VT089" and "VT24089" variations. Receiving that accepts all variations without clarification creates inventory that can't be reliably rotated. Proper protocol segregates the units, contacts the supplier for clarification, and only accepts units with confirmed lot-to-manifest mapping.
Pick Rules and Rotation Enforcement
Once lot and expiry data exists in the system, pick rules translate rotation logic into specific unit selection during order fulfillment. The rules must be clear enough that pickers can execute consistently under volume pressure without requiring case-by-case judgment calls.
For FEFO rotation, the pick rule prioritizes shortest expiry date within the requested SKU. The system sorts available units by expiry date and directs the picker to the location containing the shortest-dated inventory. When multiple units share the same expiry date, secondary criteria (lot code, location preference, or arrival sequence) determine the specific unit selected.
Location assignment becomes critical for effective rotation. Units with shorter expiry dates must be accessible for picking before longer-dated units. This often means shorter-dated inventory goes to primary pick locations while longer-dated stock stays in reserve until needed. Physical placement supports system logic rather than working against it.
Partial lot handling requires specific rules for mixed-expiry picks. When an order requires multiple units of the same SKU, should all units carry the same expiry date, or is mixing acceptable? Food retail customers typically expect consistent expiry dates within the same order. Industrial users may accept mixed expiry dates if all units exceed minimum shelf-life requirements. The rule must be defined per SKU or customer requirement, not left to picker judgment.
A cosmetics company ships anti-aging serums with 36-month shelf-life to beauty retailers. Orders for 12 units must carry the same expiry date to prevent customer complaints about inconsistent product freshness. The pick rule requires all units in a single order to come from the same expiry date lot, even if it means leaving some shorter-dated inventory for single-unit orders that can absorb the variation.
Exception Handling and Partial Lots
Real-world inventory creates scenarios where standard rotation rules don't apply cleanly. Effective shelf-life handling requires defined responses to common exceptions rather than ad-hoc decisions that create inconsistent practices.
Insufficient inventory in the preferred expiry date creates the most frequent exception. When FEFO logic calls for shortest-dated units but insufficient quantity exists to fill the order, the system must decide whether to split the order across multiple expiry dates or move to the next-shortest expiry date for the full quantity. The decision depends on customer requirements and business logic defined in advance.
Damaged units within a lot require segregation without affecting the rotation logic for remaining good units. A case arrives with two damaged units in a lot of twenty. The damaged units get removed to damage/investigation status, but the remaining eighteen units maintain their expiry date and lot code for normal rotation. The system must track partial lot quantities without losing the shelf-life data for sellable units.
Expiry date conflicts within the same lot code indicate supplier or marking errors that need resolution before the inventory can be rotated safely. When units carrying identical lot codes show different expiry dates, the inventory gets quarantined until the supplier clarifies which expiry date is correct. Processing the units as separate lots risks creating phantom inventory that doesn't match supplier records.
A food supplement distributor receives whey protein with lot code "WP240815" where most units show expiry "08/2025" but three units show "11/2025." Rather than creating two sub-lots or defaulting to the shorter date, proper exception handling quarantines all units pending supplier confirmation. Processing the mixed-date lot without clarification creates audit problems and potential regulatory compliance issues.
Cold Chain Integration with Shelf-Life Controls
Products requiring temperature control add complexity to shelf-life handling, but the principles remain consistent: capture, rotate, and prove. Cold chain products typically carry both temperature and time constraints that must be managed together.
Temperature monitoring during receiving includes verifying that arriving product maintained proper temperature during transit and confirming that internal storage can maintain required conditions. Cold chain products often carry shorter effective shelf-life due to temperature exposure, making accurate lot and expiry capture even more critical. Time spent at incorrect temperatures effectively reduces remaining shelf-life, even if the printed expiry date remains unchanged.
Storage logic for cold chain products follows the same FIFO or FEFO rotation rules but requires physical organization that maintains temperature while enabling proper rotation. Shorter-expiry product must remain accessible for picking without compromising temperature control. This often means organized cold storage with clear date marking and physical separation by expiry period.
Pick rules for cold chain products incorporate both expiry date and temperature exposure time. Products that leave temperature-controlled storage must reach the customer within specified time windows, effectively adding a second countdown timer to the standard expiry date logic. The system must track both the product's printed expiry date and the time-to-customer calculation based on shipping method and destination.
A pharmaceutical distributor handles insulin products requiring refrigerated storage with 28-day expiry after leaving refrigeration. The pick rules consider both the printed expiry date and the shipping time to destination. An order shipping two-day ground to a clinic gets different lot selection than an overnight shipment to the same location, because the ground shipment consumes more of the 28-day post-refrigeration window.
Proof Systems and Documentation
Effective shelf-life handling requires documentation that proves the right unit left for the right customer based on the correct rotation logic. This proof prevents disputes and enables rapid investigation when questions arise about expiry dates or product quality.
Pick documentation must capture which specific unit or lot was selected for each order, along with the expiry date and remaining shelf-life at time of shipment. When customers receive products with shorter shelf-life than expected, this documentation shows whether the pick followed established rotation rules or represents a process failure that needs correction.
Lot traceability becomes critical during recalls or quality investigations. When a supplier issues a recall for specific lot codes, the system must identify which customers received units from affected lots and when those shipments occurred. Forward traceability (lot to customer) and backward traceability (customer complaint to specific lot) both depend on accurate lot capture and pick documentation.
Customer communication about shelf-life should include remaining shelf-life information when it materially impacts product use. Beauty products, food items, and anything with regulatory requirements benefit from shelf-life disclosure that manages customer expectations and reduces returns. The communication draws from the same data captured during receiving and picking.
A nutritional supplement company receives a customer complaint about product expiring "too soon" after delivery. The pick documentation shows the unit came from lot "NS240901" with 18-month shelf-life, picked and shipped with 14 months remaining — well within normal parameters. Without this documentation, the complaint requires investigation time and potentially unwarranted returns processing. With proof, the response becomes a simple verification that rotation rules were followed correctly.
Governance Loop: Checks, Counts, and Incident Review
Shelf-life handling requires ongoing verification that rules are being followed consistently and that exceptions get resolved rather than accumulated. The governance loop includes regular inventory checks, cycle counting focused on expiry dates, and systematic review of shelf-life incidents.
Expiry date audits involve selecting random SKUs with shelf-life requirements and verifying that physical inventory matches system records for lot codes, expiry dates, and rotation sequence. These audits catch data entry errors, location mistakes, and process deviations before they impact customer orders. The frequency depends on product risk and regulatory requirements, but monthly audits provide adequate oversight for most operations.
Cycle counting for shelf-life products includes both quantity verification and expiry date accuracy. Standard cycle counting verifies "how many" units exist; shelf-life cycle counting adds "which lots and expiry dates" to ensure system data matches physical reality. Discrepancies in expiry dates often indicate receiving errors, system data corruption, or picker errors that need correction.
Incident review examines customer complaints, returns, and internal exceptions related to shelf-life to identify patterns that indicate process weaknesses. A cluster of complaints about short shelf-life from the same SKU might indicate supplier marking problems, receiving errors, or rotation rule failures. Systematic review prevents isolated incidents from becoming recurring problems.
The review process includes both operational metrics (rotation compliance, expiry accuracy, exception frequency) and customer impact metrics (shelf-life complaints, returns, satisfaction). The goal isn't perfect execution — it's consistent improvement and rapid detection of process drift before it affects customer experience.
FAQ
How do I handle products with multiple date markings like "manufactured," "best by," and "use by"? Capture all date markings during receiving but establish which date drives rotation logic. Regulatory requirements usually specify which date matters for rotation. When in doubt, use the most conservative (shortest) date for rotation to minimize risk. Document the decision in your shelf-life handling procedures.
What happens when the system shows available inventory but all units are too close to expiry? Define minimum shelf-life thresholds for different customer types and shipping methods. When remaining shelf-life falls below the threshold, flag the inventory as "short-dated" for special handling. Options include discount sales, donation programs, or disposal depending on product type and regulatory requirements.
Should I batch orders by expiry date to use up shorter-dated inventory faster? Only if it doesn't compromise service levels or create artificial constraints on order fulfillment. Natural FEFO rotation typically handles shorter-dated inventory without forced batching. Consider special promotions or channels for short-dated products rather than restricting normal order processing.
How do I handle customer requests for maximum shelf-life when shorter-dated inventory exists? Establish customer-specific rules in your pick logic. Premium customers or special requests can override standard FEFO to select longer-dated inventory, but document the exception and understand that it may leave shorter-dated inventory for other customers or disposal.
What proof do I need for regulatory compliance with shelf-life requirements? Maintain receiving records showing lot and expiry capture, pick records showing rotation compliance, and shipping records connecting specific lots to customer destinations. The exact requirements vary by product category and jurisdiction, so verify with your regulatory compliance team or industry guidelines.
How often should I audit expiry date accuracy in inventory? Monthly audits work for most operations, with quarterly deep audits for high-risk products. Focus audits on SKUs with frequent shelf-life complaints, complex lot structures, or regulatory requirements. The audit frequency should match your risk tolerance and regulatory obligations.