Lot tracking ecommerce WMS dashboard with batch numbers, expiry dates and FEFO pick rules

Lot Tracking Ecommerce WMS: FEFO, Expiry Dates and Recalls

In October 2026, lot tracking stopped being a niche warehouse feature for food manufacturers. It became a practical requirement for ecommerce sellers that sell supplements, cosmetics, pet food, perishables, cleaning products, medical-adjacent goods or any SKU where an expiry date, batch number or recall trail can decide whether stock is sellable.

The search results show the shift clearly. Shopify merchants are asking how to track batch and expiry dates after Stocky, Amazon sellers are asking where to see expiry dates and batch IDs, Picqer has added FEFO selection, Pickware documents remaining shelf-life handling, and fulfillment providers now sell lot tracking as a paid receiving control. The gap is not awareness. The gap is execution: many online sellers still keep expiry data in a spreadsheet that never reaches the picker, packer, marketplace order or customer-service team.

Operational trigger
1lot per receipt
Treat each batch and expiry-date combination as its own warehouse record, not as a note on the SKU.
Why lot tracking moved from enterprise WMS to ecommerce WMS

For a long time, small ecommerce warehouses treated lot tracking as something for pharmaceutical distributors or food manufacturers. That is no longer accurate. Direct-to-consumer brands now sell shelf-life products across Shopify, WooCommerce, Amazon, bol.com, TikTok Shop, wholesale portals and retail partners. A single SKU can sit in an own warehouse, a 3PL, FBA and marketplace-prep stock at the same time.

That makes a SKU-level stock number too blunt. It can tell the seller that 1,200 units are on hand, but not whether 300 units expire in 45 days, whether a wholesale buyer requires 180 days of remaining shelf life, or whether one supplier lot should be quarantined after a quality issue. A proper inventory control workflow needs the lot as a first-class object.

FEFO
Pick rule
Earliest eligible expiry ships first.
Lot + order
Recall trail
Know which customers received a batch.
Shelf-life gate
Channel rule
Block orders that need longer remaining life.
The ranking content misses the multi-channel failure mode

Most competitor articles explain FEFO, FIFO and batch tracking correctly, but they often stop at the warehouse door. They say to label batches, store expiry dates and pick the oldest expiry first. That is useful, but incomplete for online sellers. The operational risk appears when the same stock promise is published to several channels and each channel has a different tolerance for expiry, returns and customer communication.

An Amazon FBA inbound workflow, a Shopify D2C order, a bol.com order and a wholesale replenishment order can all touch the same item master while needing different handling. Amazon sellers in Seller Central forums ask how expiry dates and batch IDs are handled because marketplace systems often hide or transform the warehouse reality. Shopify merchants ask which apps can track lot codes because the native order view is not designed as a recall ledger. That is the real WMS problem: lot data must stay connected while orders move across channels.

The common FEFO mistake

FIFO is not a safe shortcut when later receipts can expire earlier than older stock. If a January receipt expires in August and a February receipt expires in July, a pure FIFO rule sends the wrong batch.

The minimum viable lot record

A WMS does not need a complicated data model to start. It needs a strict one. Every sellable lot should carry five fields: SKU, lot or batch number, expiry date or best-before date, received quantity and current location. For regulated categories, add supplier, production date, certificate or document reference and quality status. For marketplace sellers, add channel eligibility: which lots may ship to which sales channel based on remaining shelf life.

The most important rule is that a lot cannot be created after the fact. If a receiving operator scans only the SKU and quantity, the warehouse has already lost traceability. The correct place to enforce lot capture is inbound receiving. A missing lot number should send the units to quarantine until the supplier label, purchase order or packing list is reconciled.

  1. 1
    Capture lot data at receiving
    Require lot number, expiry date, supplier batch and received quantity before stock becomes sellable. Missing data should create quarantine stock, not available stock.
  2. 2
    Store stock by lot and location
    The WMS must know that SKU X has lot A in bin 01-02 and lot B in bin 03-04. A single SKU total is not enough.
  3. 3
    Apply FEFO with eligibility rules
    Pick the earliest expiry only if it still meets the marketplace, wholesale or customer shelf-life requirement.
  4. 4
    Scan the lot at packing
    The final scan should confirm that the unit in the box is the same lot that the WMS allocated.
  5. 5
    Write the lot to the order history
    Recall management depends on order-level evidence: order number, customer, SKU, lot, expiry date, ship date and carrier.
How FEFO should work in an ecommerce warehouse

FEFO means first expired, first out. The phrase sounds simple, but the warehouse rule is not simply “pick the nearest expiry.” The correct rule is “pick the earliest expiry that is eligible for this order.” Eligibility is where ecommerce sellers need more discipline than generic warehouse guides usually describe.

Imagine a skincare SKU with three lots. Lot A expires in 70 days, lot B in 120 days and lot C in 300 days. A clearance D2C order may safely use lot A. A subscription customer should probably receive lot B or C. A wholesale buyer that requires 180 days of remaining shelf life must not receive lot A or B. A marketplace prep shipment may have its own category threshold. A WMS should enforce those rules before the picker reaches the bin.

Spreadsheet lot tracking
  • Expiry dates live outside the pick path.
  • Pickers choose the front box or oldest receipt.
  • Customer service cannot instantly find affected orders.
  • Marketplace buffers are checked after a problem appears.
Cheap to start, expensive during exceptions.
WMS-controlled lot trackingRecommended
  • Receipt scans create lot-level stock records.
  • FEFO directs pickers to the right eligible batch.
  • Packing scans attach the lot to the order.
  • Recall, quarantine and channel rules use the same data.
Best fit for scaling online sellers.
Where ChannelDock fits in the workflow

ChannelDock's role is to connect the warehouse workflow with the selling channels around it. A seller does not only need scan-based warehouse control. The same control must feed inventory availability, marketplace order handling, returns and carrier handoff. That is why lot tracking should sit next to marketplace and webshop integrations, not in an isolated warehouse spreadsheet.

For online sellers using a first WMS, the rollout should be practical. Start with the SKUs where expiry, recall or supplier batch risk is real. Define lot capture at inbound, FEFO allocation in the pick flow, scan-to-confirm at packing and lot evidence in the order record. Then expand to more categories once the warehouse team trusts the process.

Think beyond one channel

Lot tracking is not only for FBA. D2C webshops, bol.com, Amazon FBM, TikTok Shop, wholesale buyers and 3PL overflow stock all need the same evidence when a product is short-dated, blocked or recalled.

The five controls to audit before choosing a WMS

When comparing ecommerce WMS software, do not ask only whether the system “supports lot tracking.” That answer is often yes, but too shallow. Ask where the lot is captured, whether the lot survives transfers, whether FEFO can include minimum shelf-life rules, whether the packer confirms the allocated lot, and whether customer service can search by lot after shipment.

Also check how returns work. A returned item from lot A should not blindly re-enter sellable stock. It may need inspection, quarantine, disposal or supplier evidence. If returns are handled outside the lot workflow, the warehouse can contaminate an otherwise clean recall trail.

  • Receiving: lot number and expiry date are mandatory before sellable stock is created.
  • Storage: each lot has a location-level quantity, not only a SKU-level total.
  • Picking: FEFO respects order eligibility, channel rules and blocked stock.
  • Packing: a final scan confirms the actual lot placed in the parcel.
  • After shipment: order history can answer which customers received a specific lot.
What to measure after go-live

The right metrics are operational, not decorative. Track the percentage of receipts with complete lot data, short-dated stock value, expired-stock write-offs, FEFO override rate, lot-related pick exceptions, recall search time and customer complaints related to expiry. These numbers tell you whether lot tracking is reducing risk or simply adding scan steps.

One useful test is a mock recall. Pick one lot code and ask the warehouse and support team to identify remaining stock, blocked locations, shipped orders, affected customers and open returns. If the answer requires three exports and a spreadsheet join, the process is not yet controlled.

What this means for online sellers
  • If the product expires, the expiry date must travel from receiving to picking, packing, marketplace sync and customer support.
  • FEFO only works when lot data is captured before stock becomes sellable, not after a customer complaint.
  • Minimum remaining shelf-life rules matter as much as the expiry date itself for Amazon, wholesale and subscription orders.
  • The best WMS setup treats missing lot data as an exception queue, not as a manual note that someone will fix later.
FAQ
What is lot tracking in an ecommerce WMS?
Lot tracking means the WMS records which production batch, lot number or expiry-date group each unit belongs to. For ecommerce sellers, the important part is connecting that lot to locations, picks, orders, returns and customer records.
What is the difference between FIFO and FEFO?
FIFO ships the oldest received stock first. FEFO ships the stock with the earliest expiry date first. FEFO is safer for food, supplements, cosmetics and other date-sensitive goods because receipt order and expiry order are often different.
Can Shopify track expiry dates and lot numbers by itself?
Shopify can manage core inventory quantities, but sellers usually need a dedicated inventory app or WMS for batch-level expiry tracking, FEFO picking, recall trails and warehouse scan control.
Do Amazon FBA sellers still need their own lot tracking?
Yes. Amazon may track expiration information inside FBA, but sellers still need their own system to plan inbound batches, prevent mixed shipments, reconcile removals and manage stock across FBA, FBM and other channels.
When should an online seller add lot tracking?
Add it before the first regulated or date-sensitive SKU scales. Retrofitting lot tracking after stock is already mixed across bins, 3PLs and marketplaces is much harder than enabling lot capture at receiving.
Conclusion

Lot tracking ecommerce WMS is not about adding a field called batch number. It is about keeping expiry, lot and quality status attached to inventory from receiving through delivery and support. For online sellers, that control protects marketplace eligibility, reduces expired-stock waste and makes recalls manageable instead of chaotic.

The practical path is clear: capture the lot before stock becomes sellable, pick by FEFO with channel-specific eligibility, verify at packing, and keep the lot on the order record. Sellers that do this early can scale shelf-life categories without turning the warehouse into a spreadsheet investigation after every exception.