TLDR
Lot tracking is the process of tracing products by batch from the moment they arrive at a warehouse through storage, picking, shipping, returns, and recalls. It connects a lot number to real operational data so a business can answer one critical question: which customers received units from a specific batch, and where are the remaining units right now? Lot tracking is essential for food, supplements, cosmetics, healthcare products, medical devices, and any SKU with expiration dates or recall risk.
Lot tracking is inventory tracking at the batch level. It helps a business know which products came from the same production run, where those units are stored, which orders received them, and what to quarantine or recall if a quality, safety, or expiration issue surfaces.
A lot number printed on a bottle or carton is not the same thing as lot tracking. The number is just a label. Lot tracking is the operational record behind it, the system that ties that label to receiving logs, bin locations, pick lists, order confirmations, customer shipments, and recall reports.
Here is a quick example. A supplement brand receives 5,000 bottles of Vitamin D from Lot VD-0426, expiring 2027-04-30. A warehouse with proper lot tracking records that lot at receiving, stores it in designated bins, picks it according to expiration-based rules, and logs which customer orders received bottles from that lot. If the manufacturer later recalls Lot VD-0426, the brand can identify every affected order and isolate remaining inventory rather than recalling the entire SKU.
That is the difference between having a lot number and having lot tracking.
What Is Lot Tracking?
A lot (sometimes called a batch) is a group of products that share a common attribute: the same production run, manufacturing date, supplier shipment, expiration date, or raw material source. A lot number is the code assigned to that group.
Lot tracking is the system and workflow that uses that code to trace inventory movements and order history across receiving, storage, picking, shipping, returns, quarantine, and disposal.
The FDA defines a traceability lot code as “a descriptor, often alphanumeric, used to uniquely identify a traceability lot” within a firm’s records. For dietary supplements, federal regulations define a batch or lot number as “a distinctive group of letters, numbers, symbols, or any combination” from which the complete history of manufacturing, packaging, labeling, and holding can be determined (eCFR 21 CFR 111.3).
The important distinction: a single SKU can have many lots. Every time a manufacturer produces a new run of the same product, that run gets a new lot number. The SKU tells you what the product is. The lot number tells you which batch it came from.
Why a Printed Lot Code Is Not Enough
Many brands assume they have traceability because lot codes appear on their packaging. They don’t. Traceability requires that lot code to be captured in a system at receiving, linked to storage locations, tied to outbound orders, and retrievable during a recall or audit.
If a team cannot pull up a report showing every order that shipped units from Lot X, they do not have recall-ready lot tracking. They have a sticker.
How Lot Tracking Works in Fulfillment
Lot tracking is a chain of events, not a single step. Here is how it works in a 3PL warehouse, from first touch to last.
Step 1: Pre-Inbound Setup
Before inventory arrives, the SKU must be flagged as lot-tracked in the WMS. This means defining required fields (lot number, expiration date, manufacture date, supplier, PO or ASN) and setting allocation rules like FEFO or FIFO.
This step cannot be skipped. Flexport’s documentation states that lot tracking and FEFO must be enabled per SKU before inventory arrives and cannot be applied retroactively to units already in the network (Flexport Help Center). Practitioners on Reddit report similar pain with NetSuite: one commenter described lots as a “PIA” because failing to plan for lot-numbered items early can require recreating inventory items later (r/Netsuite).
Step 2: Receiving
When inventory arrives, the receiving team captures the lot code and expiration date from each unit or carton. The WMS creates a record linking the SKU, lot number, quantity, expiration date, supplier, and PO. If multiple lots arrive in the same shipment, they should be separated during receiving to avoid mixing.
Flexport requires expiration dates or lot codes to be printed on each physical unit and visible during inbound, with one lot code or expiration date per SKU per shipping plan to reduce confusion (Flexport Help Center).
Step 3: Putaway
Lot-tracked inventory is stored by lot and bin location. The WMS knows which lots sit in which bins, and in what quantities. Mixing lots in a single bin is possible if the system tracks lot-level quantities per location, but avoiding physical mixing is simpler and less error-prone.
Step 4: Allocation and Picking
When an order comes in, the WMS allocates inventory based on the defined rule. FEFO allocates the earliest-expiring lot first. FIFO allocates the oldest-received lot first. Some situations require manual lot selection or customer-specific lot assignment.
The picker scans or verifies the lot during fulfillment. ShipHero, for example, offers a “Verify Lot when picking” setting that forces the picker to confirm the correct lot before proceeding. It also allows a picking disabled period before expiration, so lots nearing their expiry date are automatically excluded (ShipHero Help Center).
Step 5: Shipping and Order History
When an order ships, the lot number and quantity are written to the shipment record. This is the link that makes recalls actionable. Without it, a brand knows it shipped the product but cannot say which batch went to which customer.
Step 6: Recall and Quarantine
If a problem surfaces with a specific lot, the brand (or its 3PL) can stop fulfillment for that lot, quarantine remaining units, and pull a report of every order that received units from the affected batch. Flexport describes this capability directly: lot tracking allows merchants to “stop fulfillment for a specific lot code and view orders associated with that lot code” to support direct communication with affected customers (Flexport Help Center).
Step 7: Returns and Disposition
Returned inventory creates a traceability gap that many brands overlook. Some fulfillment networks cannot re-associate returned units with their original lot. Flexport states plainly that returned inventory “cannot be FEFO or lot tracked once received” and goes into an untracked status (Flexport Help Center).
This means returned units need clear disposition rules: inspect, restock into original lot if verifiable, quarantine, destroy, or send back to manufacturer.
Lot Tracking vs. Batch Tracking vs. Serial Tracking
These terms overlap but are not identical. Here is how they differ.
| Term | What it identifies | Example | When to use it |
|---|---|---|---|
| SKU | Product type or sellable variant | Vitamin D 60-count | Catalog and sales |
| Lot number | A batch or group of units | VD-0426 | Recall, quality, expiration |
| Batch number | Same concept as lot (common in manufacturing) | Batch A123 | Manufacturing traceability |
| Serial number | One individual unit | SN-000583 | Warranty, high-value items, devices |
| Expiration date | Shelf-life cutoff | 2027-04-30 | FEFO, stop-ship, compliance |
| Traceability lot code | FDA term for covered foods under FSMA | TLC assigned at initial packing | Food Traceability Rule records |
Lot tracking and batch tracking are used interchangeably in most fulfillment contexts. The distinction matters more in manufacturing, where “batch” sometimes refers to a single production cycle and “lot” to a larger grouping.
Serial tracking is unit-level, not group-level. It is typically used for medical devices, electronics, firearms, and high-value goods where each individual item needs its own identity.
Most ecommerce brands selling supplements, cosmetics, food, or healthcare products need lot-level tracking. Serial tracking adds cost and complexity that only makes sense when regulations or product value demand it.
Lot Tracking vs. FIFO and FEFO
These are related but different.
FIFO (First In, First Out) ships the oldest-received inventory first, regardless of expiration date. It works well for non-perishable goods.
FEFO (First Expired, First Out) ships the inventory with the earliest expiration date first. ShipBob describes FEFO as especially useful for “perishable goods, pharmaceuticals, cosmetics, and time-sensitive products” (ShipBob FEFO Guide).
Lot tracking supplies the data. FEFO is a picking rule that uses that data. You cannot run FEFO without lot and expiration date tracking, but you can track lots without using FEFO (for example, if your products don’t expire).
One important nuance for brands using distributed fulfillment: FEFO at the network level does not always mean “ship the single oldest-expiring unit from any warehouse nationwide.” Flexport’s documentation explains that network-level allocation considers expiration date, destination, inventory distribution, fulfillment cost, and on-time delivery. At the individual warehouse level, the oldest expiration date ships first. But across multiple nodes, the system may ship a unit from a closer warehouse if the expiration risk is low and the routing supports faster, cheaper delivery (Flexport Help Center).
Why Lot Tracking Matters
Targeted Recalls
Without lot-level traceability, a recall means pulling every unit of the affected SKU from shelves and warehouses. With lot tracking, the recall narrows to the specific batch. DCL Logistics notes that a 3PL can “hold all items associated with a lot number when a defect is discovered, preventing faulty goods from reaching consumers and avoiding broader recalls of unaffected inventory” (DCL Logistics).
The financial stakes are real. Industry studies commonly estimate the average direct cost of a food recall at roughly $10 million, not counting brand damage and lost sales (Manufacturing.net). ETQ’s 2025 analysis reports that nearly half of manufacturers experiencing a recall faced remediation costs between $10 million and $50 million (ETQ). Narrowing recall scope from an entire SKU to a single lot can reduce those costs dramatically.
Expiration and Waste Control
FEFO, powered by lot and expiration data, ensures that the earliest-expiring units ship first. This reduces waste from expired inventory sitting in a warehouse while newer stock gets picked instead.
Bloom Nutrition’s SVP of Operations noted that manually checking expiration dates at scale would be impossible, and that lot capabilities provide operational peace of mind (ShipBob). For any brand with dozens of SKUs and thousands of units across multiple lots, automation is not optional.
Compliance and Audit Readiness
For foods on the FDA’s Food Traceability List, the Food Traceability Rule requires records tied to Critical Tracking Events (CTEs) and Key Data Elements (KDEs), including traceability lot codes. Records must be available to FDA within 24 hours of a request.
A critical detail many articles get wrong: this rule does not apply to all food products. It applies specifically to foods on the Food Traceability List and to defined CTEs like harvesting, cooling, initial packing, first land-based receiving, shipping, receiving, and transformation. The original compliance date was January 20, 2026, but FDA has indicated it will not enforce the rule before July 20, 2028, following congressional direction.
Another detail worth knowing: the traceability lot code does not have to appear on food labeling or packaging. It can be communicated through a bill of lading, ASN, email, QR code, or another method that lets the receiver maintain required records (FDA Traceability Lot Code).
Healthcare and Medical Device Traceability
FDA’s Unique Device Identification (UDI) system requires production identifiers that can include the lot or batch number, serial number, expiration date, and manufacture date (FDA UDI Basics). The Quality Management System Regulation (QMSR), effective February 2, 2026, incorporates ISO 13485:2016 into medical device quality management requirements (FDA QMSR).
GAO analyzed FDA medical device recall data for fiscal years 2020 through 2024 and found 3,934 recall events, with 350 classified as Class I (the most serious). Terminated Class I recalls averaged 632 business days between initiation and termination (GAO Report). That is nearly two years of operational disruption per recall, which reinforces why precise lot-level traceability matters for faster identification and resolution.
Customer Trust
Expired, recalled, or batch-defective products create support tickets, refunds, negative reviews, and lasting brand damage. In ecommerce, receiving an expired or past-prime product is one of the fastest ways to lose a customer permanently.
Which Products Need Lot Tracking?
Lot tracking is a risk-based decision. Some brands need it because of legal requirements. Others need it because a single bad batch could create customer safety issues, marketplace suspensions, or retailer chargebacks.
Strong candidates for lot tracking:
- Dietary supplements and vitamins
- Food and beverage
- Cosmetics, skincare, and SPF products
- Pet food and pet supplements
- Healthcare products and diagnostic kits
- Medical devices
- Pharmaceuticals and OTC products
- Electronics and components with version control
- Automotive and industrial parts
- Chemicals and industrial materials
- Subscription boxes containing perishable or regulated components
- B2B and wholesale brands shipping to retailers that require lot data on invoices or ASNs
Speed Commerce and 3PL Center both list similar categories as typical lot tracking use cases (Speed Commerce, 3PL Center).
If a product has a shelf life, a recall risk, or a retailer/marketplace that demands batch-level data, lot tracking is not optional.
Minimum Viable Lot Tracking: The Data You Need to Capture
Most guides tell brands to “track lots” without specifying what that actually means in a WMS or fulfillment system. Here is the minimum set of data fields a lot-tracked process should capture and maintain:
- SKU / product ID — What product is this?
- Lot number / batch code — Which production run is this?
- Quantity received — How many units entered the system under this lot?
- Supplier / manufacturer / PO / ASN — Where did the lot come from?
- Manufacture date, best-by date, or expiration date — What shelf-life constraint applies?
- Receiving date and receiving location — When and where did the lot enter the network?
- Storage location (bin, pallet, zone, facility) — Where is the lot right now?
- Status — Sellable, on hold, quarantined, expired, damaged, returned, disposed, or recalled?
- Pick allocation rule — FEFO, FIFO, specific lot, blocked lot, or manual?
- Order and shipment history — Which orders, customers, or marketplace shipments received units from this lot?
- Return and disposition history — Were returned units inspected, restocked, quarantined, destroyed, or sent back?
- Audit trail — Who changed the lot status, quantity, location, or disposition, and when?
If the system cannot connect lot to location to order to customer, it is not enough for precise recall response. A strong system should also surface reporting views like lot-by-location, expiry-by-lot, orders-by-lot, and expiring-soon alerts.
Practitioners on Reddit confirm this gap is real. One NetSuite user described struggling to generate a simple report showing all inventory with lot numbers and expiration dates, even though the data technically existed in the system (r/Netsuite). Another thread noted that NetSuite’s native inventory count process captures quantity by lot and bin but does not validate expiration dates during counts because expiration is metadata tied to the lot record, not something counted (r/Netsuite).
Common Lot Tracking Mistakes
Mistake 1: Enabling Lot Tracking After Inventory Is Already Received
This is the most expensive mistake. Retrofitting lot data after inventory is already mixed in bins is painful, incomplete, or impossible. Both fulfillment platform documentation and practitioner experience confirm this. Plan for lot tracking before the first inbound shipment, not after a recall forces the issue.
Mistake 2: Treating Shopify Quantity Tracking as Lot Traceability
Shopify’s native inventory system tracks quantities. It does not track lots, batches, or expiration dates. A Shopify community thread from December 2025 confirmed that Stocky does not support batch tracking (Shopify Community). Practitioners on Reddit describe supplement sellers using Google Sheets for batch numbers and expiry dates because Shopify has no native solution (r/shopifyDev). Another thread in r/shopify_growth suggested creating a SKU per batch as a workaround (like “Black Hoodie - M - Batch 2026-01”), while acknowledging this is not ideal for scaling brands (r/shopify_growth).
Spreadsheets and SKU-per-batch workarounds break down once a brand operates across multiple warehouses, sells through wholesale and DTC, handles returns, or faces a recall.
Mistake 3: Not Enforcing Lot Scan at Picking
If a picker can bypass lot verification, the WMS record may not match what actually shipped. The system says Lot A went out, but the picker grabbed Lot B. During a recall, the data is useless. Any serious lot tracking implementation should require lot scan or confirmation at the pick step.
Mistake 4: Mixing Lots From Different Suppliers
A NetSuite practitioner warned against mixing identical-looking stock from different vendors because recall traceability depends on knowing which vendor batch shipped to which customer. The recommendation: make lot identifiers unique enough by including manufacturer, date, vendor, or PO when needed (r/Netsuite).
Mistake 5: Ignoring Returns
Returns are where lot traceability often breaks. If returned inventory goes back into sellable stock without inspection or lot re-association, the brand loses visibility into what batch those units came from. Some fulfillment networks explicitly cannot re-track returned inventory at the lot level. Brands need a clear returns disposition workflow: inspect, verify lot if possible, quarantine if not, and define whether returned units can re-enter sellable inventory.
Mistake 6: Tracking Lots but Not Expiration Dates
Lot tracking and expiration tracking are related but not identical. A lot number identifies the batch. The expiration date determines when it should stop shipping. Both fields should be captured together. Without expiration dates linked to lots, FEFO is impossible and stop-ship rules cannot be automated.
Mistake 7: Using FIFO When FEFO Is Needed
FIFO moves the oldest-received inventory first. FEFO moves the earliest-expiring inventory first. If a newer receipt has a shorter shelf life than an older receipt (which happens regularly when suppliers ship from different production runs), FIFO will ship the wrong units. Any product with an expiration date should use FEFO.
Mistake 8: Overlooking Kits
Kits create a traceability challenge because a single sellable parent SKU may contain components from multiple lots with different expiration dates. ShipHero warns against enabling lot tracking on kit SKUs and recommends managing lots at the component level instead (ShipHero Help Center). If one component in a kit is recalled, the brand needs to know which kit orders contained that component lot.
Barcode Standards and Lot Data
GS1 Application Identifiers (AIs) give lot and expiry data machine-readable structure. AI 10 represents the batch or lot number (up to 20 alphanumeric characters), and AI 17 represents the expiration date in YYMMDD format. Multiple AIs can be carried in a single barcode.
But a barcode is only useful if the WMS is configured to parse and store the lot and expiry fields it contains. Scanning a GS1-128 barcode that encodes lot and expiration data is meaningless if the system discards those fields during receiving.
What to Ask a 3PL About Lot Tracking
Not every 3PL that claims lot tracking capability actually enforces it in daily operations. Before outsourcing fulfillment for lot-tracked products, brands should ask specific questions:
- Can your WMS track inventory by SKU, lot number, expiration date, bin location, and facility?
- Can lot tracking be enabled before receiving, and what data must appear on the ASN or inbound shipment?
- Do you support FEFO, FIFO, manual lot allocation, and configurable stop-ship-by-days?
- Are pickers required to scan or verify the lot at pick and pack?
- Can you generate an order and customer list by lot number during a recall?
- Can you quarantine a specific lot across all warehouse nodes?
- Can you prevent expired or quarantined inventory from syncing as sellable to sales channels?
- How do you handle returned lot-tracked inventory? Does it maintain traceability or go into an untracked status?
- How do you handle kits where components have different lot numbers or expiration dates?
- Can you support healthcare workflows like chain-of-custody documentation, quarantine holds, and FEFO rotation?
- What are the fees for lot tracking and FEFO? (For reference, Flexport lists $0.10 per unit received for FEFO, lot tracking, or both combined. This is one data point, not a universal benchmark.)
The answers reveal whether lot tracking is a checkbox feature or an enforced operational workflow. Ask to see the lot report before shipping any inventory.
Brands selling healthcare products, supplements, cosmetics, or any shelf-life-sensitive SKU should look for a 3PL that offers lot and expiry tracking, FEFO logic, quarantine procedures, chain-of-custody processes, and real-time WMS visibility as core capabilities, not add-ons. 4fillment positions these as part of its healthcare logistics and tech-powered fulfillment operations, with same-day shipping and multi-node coverage from facilities in California, Texas, Georgia, and New Jersey.
Amazon FBA and Lot Tracking Considerations
For brands using FBA prep services, lot and expiration discipline starts before inventory reaches Amazon. Amazon considers products with shelf life (or products that lose effectiveness over time) to be expiration-dated, even if no date appears on the package. Expiration-dated products requiring prep must have expiration-date labels applied outside the prep packaging (Amazon Seller Forums).
Practitioners on Reddit report that while Amazon asks for expiration dates when sending perishable products to FBA, finding that information later in reports is difficult (r/FulfillmentByAmazon). Another seller described maintaining a master list of lots and expiration dates with internal SKUs, noting that ingestible products require dates on individual items and outside shipping containers (r/AmazonFBA).
The takeaway: brands should maintain their own lot and expiration records for FBA inventory rather than relying on Amazon to provide that traceability. A 3PL that handles FBA prep can capture lot data during the prep process, before units leave for Amazon’s network.
FAQs
What is lot tracking in simple terms?
Lot tracking is the process of recording which batch of a product was received, where it is stored, which orders it shipped in, and what should happen if that batch has a problem. It turns a batch code into searchable, actionable data.
Is lot tracking the same as batch tracking?
In most fulfillment and ecommerce contexts, yes. The terms are used interchangeably. “Batch tracking” is more common in manufacturing. “Lot tracking” is more common in warehousing and distribution. The underlying concept is the same: tracing a group of products that share a common production or shipment origin.
What is the difference between a SKU and a lot number?
A SKU identifies a product variant (Vitamin D, 60-count bottle). A lot number identifies a specific production run of that variant (Lot VD-0426, manufactured March 2025, expiring April 2027). One SKU will have many lot numbers over its lifetime.
What is FEFO and how does it relate to lot tracking?
FEFO stands for First Expired, First Out. It is a picking rule that prioritizes inventory with the earliest expiration date. FEFO depends on lot and expiration date data. Without lot tracking that captures expiration dates, FEFO cannot function.
Do all products need lot tracking?
No. Products without expiration dates, recall risk, or regulatory requirements may not need it. But any product with a shelf life, safety concern, or quality variance between production runs benefits from lot-level traceability. When in doubt, consider what would happen if a customer reported a defect and the brand could not identify which batch it came from.
Is lot tracking required by the FDA?
It depends on the product category. For foods on the Food Traceability List, the FDA’s Food Traceability Rule requires specific records tied to Critical Tracking Events and traceability lot codes, with 24-hour record availability upon request. For dietary supplements, current Good Manufacturing Practice regulations require batch and lot identification. For medical devices, the UDI system includes lot or batch number as a production identifier. Not every product falls under these requirements, but many regulated categories have some form of lot-level recordkeeping obligation.
Can Shopify track lot numbers natively?
Not in a meaningful way for traceability purposes. Shopify’s inventory system tracks quantities, not lots, batches, or expiration dates. Merchants selling perishable or regulated products typically need a third-party app, an external WMS, or a 3PL system to manage lot-level data.
What should a recall report show?
At minimum, a recall report should show: the affected lot number, total units received under that lot, current inventory quantity and location, lot status (sellable, quarantined, expired, disposed), and a complete list of orders and customers that received units from that lot. Without the order-to-lot link, a recall becomes a SKU-wide event instead of a targeted response.
Brands that need lot tracking for healthcare, supplement, cosmetic, food, or other shelf-life-sensitive products should evaluate their 3PL’s actual capabilities, not just their marketing claims. 4fillment supports lot and expiry tracking, FEFO, quarantine workflows, chain-of-custody documentation, and real-time WMS visibility as part of its fulfillment operations. Reach out to discuss your SKU profile, compliance requirements, and onboarding timeline.