3PL Lot Tracking Software: FEFO, Expiry Dates and Recall Proof

In 2026, more ecommerce 3PLs are being asked to handle products that are not just counted by SKU, but controlled by lot number, batch, serial number, best-before date or expiry date. Supplements, cosmetics, food, pet care, medical accessories and regulated consumer goods all create the same operational question: can the fulfillment center prove which physical batch was received, stored, picked, shipped, quarantined or recalled?

The gap is rarely that a warehouse cannot scan barcodes. The gap is that many 3PL workflows still treat stock as one flat quantity. That is enough for generic apparel or accessories. It breaks when one client needs first-expired, first-out picking, another requires minimum shelf life by channel, and a third asks for a lot-specific shipment report within minutes of a supplier issue. This is where 3PL lot tracking software becomes a margin and trust system, not an optional inventory feature.

Why lot tracking is becoming a 3PL sales requirement

Search results and competitor pages around FEFO, lot control and expiry-date tracking mostly explain definitions: what a lot number is, why expiration dates matter, and how a WMS can guide pickers. That is useful, but fulfillment centers need a more practical lens. The buying question from a brand is not only “can you track lots?” It is: “Can you stop expired units from shipping, prove which customers received a batch, and show me aging stock before it becomes a write-off?”

That demand is growing because ecommerce categories are getting more operationally sensitive. Supplements and beauty brands sell through Shopify, Amazon, bol.com and retail partners at the same time. Food and beverage sellers need minimum shelf-life rules. Regulated goods need traceability. A client may sell the same SKU across a D2C webshop, marketplace listing and B2B wholesale order, while the warehouse must decide which physical lot is safe to allocate.

For a fulfillment center, the commercial upside is clear: lot-aware workflows let you serve categories with higher switching costs and stronger operational needs. The downside is also clear: if lot tracking lives in spreadsheets, one late update can create expired shipments, rejected marketplace inventory, refund disputes or a recall scramble.

The five data points every lot-aware warehouse needs

A practical lot tracking workflow starts at receiving. If the dock team books a pallet into generic available stock and adds lot details later, the control has already failed. The WMS should force the right data before units are sellable. That does not mean the process has to be slow; it means barcode scanning and required fields must match the risk profile of the client.

1. 1
   Capture lot data at receiving

   Require lot number, expiry date, supplier batch and received quantity before stock becomes available.
2. 2
   Store stock by client, SKU and lot

   Do not merge dated stock into one generic SKU balance; keep owner, location and lot separate.
3. 3
   Apply FEFO and shelf-life rules

   Route picks by earliest usable expiry and block lots that fail client or marketplace thresholds.
4. 4
   Expose lot status in the client portal

   Give clients live views of available, aging, quarantined and expired stock before tickets start.
5. 5
   Keep a lot-to-order audit trail

   Every outbound order should carry the lot evidence needed for recalls, disputes and customer service.

The minimum record is simple: client owner, SKU, lot number, expiry date and quantity. Stronger workflows add supplier batch, manufacturing date, country of origin, inbound delivery reference, condition status and evidence photos. For high-risk clients, the warehouse also needs rules for minimum remaining shelf life by channel. Amazon, retail, B2B and D2C may not accept the same “good until” threshold.

FEFO only works when allocation is lot-aware

Many warehouses say they follow FEFO, but the software often only recommends a location or sorts stock by receipt date. True FEFO requires the order allocation engine to understand expiry dates at lot level. If a picker can override the suggested lot without a reason code, or if marketplaces receive an available-to-sell number that includes soon-to-expire stock, the process is not controlled.

ChannelDock’s role in this operational stack is to connect fulfillment execution with the ecommerce channels around it. A 3PL can use ChannelDock fulfillment center features to manage clients, orders and warehouse collaboration, while marketplace and webshop integrations keep sellable stock aligned outside the warehouse. For teams already improving scan discipline, the pick and pack workflow is the natural next layer: lot-aware stock data should travel all the way into the pick decision, not stop at the inventory screen.

What competitor content misses: client proof

Most 3PL lot tracking pages focus on internal control: track expiry dates, reduce waste, support FEFO and improve recall readiness. The missing piece is client proof. A fulfillment center can do the work correctly and still lose trust if the client cannot see the evidence. Modern 3PL software should turn every lot event into a client-facing record: received, quarantined, released, allocated, picked, shipped, returned or disposed.

The strongest 3PL lot tracking workflow is not the one with the most fields. It is the one that can answer a client’s recall, expiry or dispute question without opening a warehouse group chat.

This matters most during exceptions. If a supplier reports a contaminated batch, the 3PL should not search dispatch notes manually. It should export remaining stock by location, shipped orders by lot, affected clients, outbound dates and current quarantine actions. If a client challenges storage charges for aging stock, the portal should show when the lot arrived, when alerts were sent and why the stock was blocked from normal allocation.

How to design expiry alerts without creating alert fatigue

Aging-stock alerts work only when they are tied to decisions. A 90-day warning is useful if the client can run a promotion, shift demand to a marketplace, or approve liquidation. A 30-day warning is too late if the product requires 60 days of remaining shelf life to ship. The right model is not one global expiry rule; it is a rule table per client, SKU group and sales channel.

The operational trick is to connect those statuses to inventory sync. If a lot is blocked for Amazon but still acceptable for D2C orders, the 3PL should not simply remove all units from availability. If a lot is quarantined after a quality issue, it must be excluded from every channel immediately. This is where warehouse software, inventory sync and marketplace integrations need to behave as one system.

A practical 90-day implementation plan

Fulfillment centers do not need to rebuild every workflow in one go. The fastest path is to start with the clients whose categories create the most expiry, compliance or recall risk. Then standardise the lot data model and roll it across receiving, storage, picking, returns and reporting.

• Days 1-15: Identify clients with dated, batch-controlled or regulated goods. Document their minimum shelf-life rules and current manual workarounds.
• Days 16-30: Make lot number and expiry date mandatory at receiving for those clients. Train dock teams on exception codes for missing or unreadable data.
• Days 31-45: Configure FEFO pick rules, blocked-stock statuses and quarantine workflows. Test whether pickers can accidentally bypass expiry logic.
• Days 46-60: Connect lot status to sellable inventory sync so marketplaces and webshops do not receive unsafe availability.
• Days 61-90: Publish client-facing aging reports, lot-to-order exports and recall runbooks. Review disputes and expired-stock write-offs monthly.

What to measure after go-live

The quality of a lot tracking rollout is visible in a small set of metrics. Track them per client, not only at warehouse level, because one high-risk category can hide inside an otherwise healthy operation.

• Lot capture completeness: percentage of inbound units with valid lot and expiry data before becoming sellable.
• FEFO compliance: percentage of picks that used the correct earliest eligible lot.
• Blocked-stock accuracy: units excluded from channel availability because they failed shelf-life rules.
• Recall response time: minutes needed to identify remaining stock and shipped orders for a specific lot.
• Expired-on-shelf value: stock value lost because alerts or allocation rules failed to move units in time.

FAQ

Conclusion

3PL lot tracking software is no longer a niche feature for food warehouses. It is becoming part of the trust contract between fulfillment centers and ecommerce brands. The warehouse must know which lot is where, when it expires, whether it can be sold, which orders used it and what evidence the client can see.

The fulfillment centers that win this category will not be the ones that simply add a lot-number field. They will be the ones that connect receiving scans, FEFO allocation, marketplace availability, client portals and recall reports into one operational flow. That is the difference between storing products with expiry dates and running a fulfillment operation that can prove control.