Your WMS is lying to you.
If your system treats "inventory" as a generic bucket of SKUs rather than a collection of batch-specific entities with decaying value, your CFO is currently subsidizing waste. In the cosmetics and personal care segment, where margins are squeezed by high marketing spends and heavy packaging costs, an expired unit isn’t just a "loss"—it is an absolute write-off that eats 100% of the landed cost plus the overhead of storage.
The industry standard of FIFO (First-In, First-Out) is insufficient for beauty products with volatile expiration windows. A batch arriving today might have a 6-month window, while the pallet behind it—arrived last month—might have 18 months. If your pickers are pulling based on "arrival date" instead of "expiry date," you are effectively gambling with your net margins.
The Failure State: When Batch Logic Collapses
I once worked with a mid-market premium skincare brand operating across six regional DCs in India. They were scaling rapidly, moving from 50k to 250k units monthly. Their WMS was "aware" of the SKU, but the inventory sync between their ERP and the 3PL’s warehouse floor was disconnected from batch identifiers.
During a festive season spike, they had 4,000 units of a high-margin serum in a central hub. The system saw "available stock." It didn't see that the specific bin containing the oldest batch was actually slated for an expiry date just three weeks out. Because the picker’s handheld device only showed "Quantity: 10," they grabbed it.
The result? 400 customers received products that would expire during their transit or within days of delivery. The "Return to Origin" (RTO) costs were manageable, but the brand damage and the subsequent cost of incinerating "near-expiry" stock—which couldn't be sold as "sale" items due to strict brand guidelines—gutted their quarterly margin by 4.2%. They weren't just losing product; they were paying for waste that could have been liquidated months prior if the system had flagged the expiry window at the T-180 day mark.
The FEFO Implementation Matrix
To solve this, you don't need "smarter" people on the floor; you need a more primitive, rigid logic gate in your warehouse management system.
1. The Data Signal: GS1-Compliant Batch Tracking Every incoming pallet must be scanned with a unique Batch ID linked to an Expiry Date and a Manufacturing Date. If the WMS doesn't prompt the put-away operator for both, the system should reject the bin entry. You cannot manage what you cannot see at the SKU+Batch level.
2. The Logic Layer: Priority Scoring Instead of a simple queue, implement an "Expiry Proximity Score."
- Zone A (Safe) : >180 days to expiry. Standard fulfillment logic applies.
- Zone B (Warning) : 90–180 days. System flags these for "Flash Sale" logic or specific "Bundle" promotion hooks in the e-commerce front-end.
- Zone C (Critical) : <90 days. The system must automatically pull these from general stock and move them into a "Liquidation" bucket where they are only available to B2B bulk buyers or discounted outlet channels.
3. Automation & Exceptions: The sync cycle between the ERP and WMS should run every 15 minutes, not once a day. When an item hits the 120-day "Yellow Zone," an automated API call must trigger to your marketing automation tool to push these SKUs into "Limited Time Offer" banners.
The Bottom Line for the CFO
Stop viewing "wastage" as a cost of doing business in cosmetics. It is a failure of data architecture. If your WMS doesn't force a pick-path based on `min(expiry_date)`, you are essentially running a lottery where the house loses every time a customer receives a product with 30 days of life left.
Move to FEFO. Lock down batch-level visibility. If the picker has to think about which box to grab, your system has already failed you.