Lot tracking: what it is and who actually needs it

Lot tracking means recording, for every inbound batch, which lot or batch number the units came from — so that when a supplier recalls production run B-2403, you can answer three questions the same afternoon: which of my stock is that batch, which customers got it, and what's left on the shelf. It is batch-level bookkeeping sitting on top of normal SKU counts. Not every store needs it; for some product categories it's close to non-negotiable, and the honest starting point is knowing which side you're on.

Who actually needs lot tracking

The dividing line isn't industry size — it's whether "which production run?" could ever matter:

• Food and beverage. Any packaged food carries batch or date codes from the producer. If a supplier issues a recall, batch traceability is how you find the affected units instead of pulling everything with that flavor.
• Supplements. Production batches are the unit of quality; a defective batch is a batch, not a flavor.
• Cosmetics and skincare. Batches drive both traceability and expiry rotation (the date-driven side is its own topic).
• Anything with certification or compliance papering — e.g., a toy line where a paint batch failed a test, electrical goods where a component lot was faulty.

If you resell sealed, stable, non-regulated goods — phone stands, hiking socks, enamel pins — a recall that discriminates by batch is unlikely, and the discipline below buys you little. That's the honest scope: lot tracking is a cost you take on when batch identity carries real information.

On the regulatory side, food traceability requirements are tightening for suppliers: the U.S. FDA's Food Traceability Rule under FSMA Section 204 requires certain food companies to maintain batch-level traceability records along the supply chain (FDA, Food Traceability Final Rule — accessed October 2026; requirements phase in over coming years and details belong to your supplier, not to you). As a small retailer you're usually not the regulated record-keeper, but your ability to say "I received batch X on date Y, sold Z units" is what makes you a usable link in that chain.

What a lot record actually contains

A usable lot record has five fields, and no more:

The distinction that matters: a lot is a group of units produced together (one-per-batch); a serial number is one-per-unit (electronics, warranty goods). If your product is a $12 hot sauce, you track lots. If it's a $400 espresso grinder, you track serials — different discipline, different article.

Recalls are the scenario that justifies the effort, and they're not exotic: a supplier emails that run B-240317 of the chipotle hot sauce may contain undeclared allergens. With lot records, the answer is 20 minutes of work — you received 120 units Mar 24, sold 41 since (order export filter), 79 remain in bin A-02, customers who received it are listed from orders shipped after Mar 24. Without lot records, the same question is "pull everything and inspect the codes," and if you'd already sent the batch to a promotion, you're reconstructing it from memory.

GS1 standards formalize exactly this: barcodes can encode batch/lot numbers and dates as product attributes alongside the product identifier (GS1 Barcodes, gs1.org/standards/barcodes — accessed October 2026), which is why supplier cases often carry both a product barcode and a lot code on the label. Reading the second code at receiving is the entire discipline in one gesture.

Lightweight lot tracking without ERP software

Full lot tracking — lot fields on every transaction, lot-level availability, traceability reports — is ERP territory, and mainstream inventory apps for Shopify mostly don't do it (Shopify's own count tooling works at SKU/variant and quantity level with no batch dimension — Shopify Help Center, "Stock counts," accessed October 2026). Be aware of what each level actually delivers:

1. The receiving log (works for almost everyone at small scale). A spreadsheet with the five fields above, one row per lot received. When stock of a SKU comes from two live lots, keep them in separate, labeled locations — the physical separation is the lot tracking at small scale. If you already maintain an inventory spreadsheet, this is one tab, not a new system.

2. Separate SKUs per lot (for short-dated or high-risk goods). For products where you might genuinely need to isolate one batch — say a supplement arriving with 6 months of shelf life — some sellers add a lot suffix to the SKU on intake (SAUCE-HOT-CHIP-5OZ-B2403). This makes lot visible in every screen including Shopify counts, at the cost of a new "SKU" per batch that you retire when the batch sells through. Workable, but it multiplies records; reserve it for goods where batch isolation is a real scenario, not a hypothetical.

3. Dedicated batch/lot apps. A handful of Shopify apps add lot/expiry fields — they sit in the same tier of narrow utilities as other add-ons (the app landscape changes quickly, so evaluate against your actual recall scenario rather than feature lists). The honest test of any of them: can it answer "which orders got lot B-2403?" in one report?

4. ERP-class systems. Platforms like Cin7 and Katana treat lots as first-class inventory data. That's the correct answer once batch complexity is real — and a heavy answer before it is.

The honest tooling note

InventoryX doesn't do lot tracking, and we won't pretend otherwise — lot/batch fields are ERP-level functionality and sit outside its V1 scope, which is built around the replenishment side: a per-SKU ledger of out-of-stock days, estimated lost sales, and a weekly buying list. For a store that needs both, lot discipline stays in the receiving log while the buying decisions live elsewhere. This article is the same position most operators are in: the spreadsheet method above is what the work actually looks like at sub-5,000-SKU scale, tooling claims aside.

Common questions

What is lot tracking in inventory? Lot tracking records which production batch (lot number) each unit of stock came from, along with receive date and supplier. It lets you isolate, quarantine, and trace a specific batch — for a recall, a quality issue, or expiry rotation — instead of treating every unit of a SKU as interchangeable.

What's the difference between lot tracking and serial number tracking? A lot is one number shared by every unit produced together (a batch of hot sauce); a serial is unique to each unit (an espresso grinder). Lots answer "which batch is this from"; serials answer "which specific unit is this." Food, supplements, and cosmetics track lots; electronics and warranty goods track serials.

Do I legally need lot tracking for my Shopify store? It depends on what you sell and your jurisdiction, and this isn't legal advice. In the U.S., the FDA's FSMA Section 204 traceability rule pushes batch-level record-keeping through the food supply chain, and producers/suppliers are the primary regulated parties. Small retailers are generally best served by keeping simple receiving records (lot, date, units) so they can respond to a supplier recall quickly.

How do I track lots without expensive software? A five-field receiving log (lot number, SKU, units, receive date, supplier/PO) plus physical separation of live lots on the shelf covers most small operations. For goods needing true batch isolation, a temporary lot-suffix SKU per batch works. Dedicated lot apps and ERPs make sense once volume or regulation makes the spreadsheet the bottleneck.

What information goes in a lot record? Lot number from the producer's packaging, the SKU, units received, the receive date, and the supplier or PO reference. When a recall notice arrives, those five fields plus an order export let you name affected units still on hand and the customers who received the rest — the whole point of the discipline.

Next step

Pull one recently received carton of your most batch-sensitive product and find the lot code on it — then create the five-column log and enter that receipt as row one. If you can't find a lot code on the packaging, that itself is a finding worth a message to your supplier, because a recall notice without a batch identifier leaves you with nothing to filter by. The broader buying and replenishment context around this discipline is in the Shopify inventory management guide.