Batch Tracking: Complete Implementation Guide (2026)

Every unit tells a story — if you track it

Batch tracking is the practice of assigning a unique identifier to a group of products that were manufactured, processed, or received together, and following that identifier through every subsequent transaction: storage, sale, transfer, return, and disposal.

In principle, every business in India agrees batch tracking is important. In practice, fewer than 20% of SMEs track inventory at the batch level. The rest track at the product level — they know they have 200 units of Product X, but they cannot tell you which 200 units, when they were manufactured, when they arrive, or when they expire.

This gap between knowing "how many" and knowing "which ones" is the difference between a business that reacts to problems (expired stock, recalls, compliance failures) and one that prevents them.

Why batch tracking matters in India specifically

FSSAI compliance requires it

The 2026 FSSAI enforcement update mandates quarterly reporting of expired stock through the FoSCoS portal. The report requires product-wise breakdown including batch numbers. You cannot file this report accurately without batch-level records.

GST audit trails depend on it

When GST inspectors cross-reference your purchase invoices with your sales records and current stock, batch numbers are the linking thread. Purchase invoice shows you bought 100 units of Batch XY789. Your sales records show you sold 82 units. Your stock shows 18 units remaining. If the numbers do not reconcile at the batch level, you have an audit finding.

Drug regulations mandate it

For pharmacies, batch tracking is not optional. The Drugs and Cosmetics Rules require batch-level recording for all drug sales, with additional requirements for Schedule H1 drugs. A pharmacy that cannot trace a dispensed drug back to its batch number, manufacturer, and supplier is operating in violation.

Consumer protection demands it

When a product recall occurs — and in India, food and pharmaceutical recalls happen regularly — the manufacturer identifies specific batch numbers that are affected. Without batch-level tracking, you cannot determine whether the recalled batches are in your inventory, have been sold, or have already expired. Your only option is a blanket check of all stock, which is slow, expensive, and often incomplete.

The anatomy of a batch record

A complete batch record in an Indian business context includes:

At receiving (goods receipt)

• Product name and code — your internal identifier
• Batch number — assigned by the manufacturer (printed on packaging)
• Manufacturing date — when the batch was produced
• Expiry date — when the batch should not be sold after
• Quantity received — number of units in this batch
• Supplier/distributor — who delivered this batch
• Purchase invoice number — for GST cross-referencing
• MRP — maximum retail price (mandated on all packaged goods in India)
• Purchase rate — your cost price per unit
• Storage condition — ambient, refrigerated, or frozen

During storage

• Location — warehouse, shelf, or cold room position
• Current quantity — updated with each sale, transfer, or write-off
• Days to expiry — continuously calculated
• Alert status — green (>90 days), amber (30-90 days), or red (<30 days)

At sale

• Sale quantity — deducted from this specific batch
• Sale date and time — timestamp of the transaction
• Invoice number — the GST invoice that recorded this sale
• Customer — for B2B sales; optional for B2C

At disposal/return

• Disposal quantity — units expired, damaged, or otherwise removed
• Disposal reason — expiry, damage, recall, customer return
• Disposal method — destruction, return to supplier, donation
• Disposal date — when the action was taken

Implementing batch tracking: the step-by-step approach

Phase 1: Product master setup (Week 1)

Before you can track batches, your product master must be batch-ready. For each product, define:

• Is this product batch-tracked? — not every product needs batch tracking. Paper towels and cleaning supplies probably don't. Food, medicines, and cosmetics do.
• Default shelf life — so the system can validate expiry dates at receiving. If a product has a 6-month shelf life but arrives with only 2 months remaining, the system should flag this.
• Alert thresholds — when should red/amber/green alerts trigger for this product category?
• FEFO enforcement level — strict (system blocks non-FEFO sales) or advisory (system recommends FEFO but allows override)?

Phase 2: Batch receiving workflow (Week 2-3)

This is the most important phase. If batch data is not captured at receiving, it cannot be tracked downstream.

Option A: Manual entry

For each line item on a delivery:

• Enter the product code
• Enter batch number (from the package)
• Enter manufacturing date and expiry date
• Enter quantity and rate
• System creates the batch record

Time per delivery: 15-30 minutes for a 30-item delivery.

Option B: [Invoice OCR](/invoice-scanner)

• Photograph the supplier's invoice
• System extracts all line items including batch numbers and dates
• Verify and confirm
• System creates batch records for all items

Time per delivery: 2-3 minutes for a 30-item delivery.

Option C: Barcode scanning

• Scan the product barcode
• System identifies the product
• Scan or enter the batch number (some products encode batch in the barcode)
• Enter or confirm expiry date
• Enter quantity

Time per delivery: 10-15 minutes for a 30-item delivery.

For most Indian businesses, Option B (invoice OCR) provides the best balance of speed and accuracy.

Phase 3: FEFO at point of sale (Week 3-4)

Once batches are in the system, configure your billing/POS to enforce FEFO:

Strict FEFO: When a product is scanned at the POS, the system automatically deducts from the batch with the nearest expiry date. The cashier does not choose. The system decides.

Advisory FEFO: The system recommends the nearest-expiry batch but allows the cashier to select a different one (with a reason). Use this for situations where the nearest-expiry batch has a quality concern.

For retail and pharmacy, strict FEFO is recommended. For restaurants and manufacturing, advisory FEFO gives more flexibility.

Phase 4: Alert configuration (Week 4)

Set up expiry alerts at three levels:

Store/pharmacy level:

• Daily alert at 8 AM listing items in red zone (0-7 days) and amber zone (8-30 days)
• Weekly summary of items in green zone (31-90 days) with total value at risk

Management level:

• Weekly summary across all locations (for multi-store businesses)
• Monthly trend: is total value at risk increasing or decreasing?

Operational level:

• Real-time alert when a batch enters the red zone
• Alert when a return window deadline is approaching for a batch

Phase 5: Reconciliation and reporting (Month 2)

After one month of batch-level operation, run your first full reconciliation:

For each batch-tracked product:

• Opening stock (by batch): quantities at the start of the month
• Purchases (by batch): quantities received during the month
• Sales (by batch): quantities sold during the month
• Returns received (by batch): customer returns added back
• Returns to supplier (by batch): near-expiry returns processed
• Write-offs (by batch): expired or damaged units removed
• Closing stock (by batch): what remains

Opening + Purchases + Returns received = Sales + Returns to supplier + Write-offs + Closing

If this equation balances, your batch tracking is working. If it doesn't, the gap tells you where data is leaking — usually at receiving (items received but not entered) or at the POS (items sold but not deducted from the correct batch).

Common implementation challenges

Challenge 1: "We have too many SKUs to batch-track everything"

You don't need to track everything. Start with the 20% of products that account for 80% of your expiry risk:

• All perishable items (dairy, bread, fresh produce)
• All medicines (regulatory requirement)
• All items with less than 6 months shelf life
• All items where you have historically experienced expiry losses

Once the high-risk items are tracked, expand to medium-risk items. Low-risk items (long shelf life, fast movers) can be tracked at the product level initially.

Challenge 2: "Staff won't enter batch data at receiving"

This is the most common failure point. Three approaches that work:

• Make it faster than manual. Invoice OCR reduces entry time by 80%. When it is faster to use the system than to skip it, staff comply.

• Make it required. Configure the system so that goods receipt cannot be completed without batch and expiry data. No batch, no GRN. No GRN, no payment to supplier.

• Make it visible. Display a daily "receiving compliance" metric. "Today: 95% of deliveries had complete batch data." The competitive instinct of staff handles the rest.

Challenge 3: "Our products don't have batch numbers"

Some products — particularly loose items, locally manufactured goods, and fresh produce — don't come with manufacturer batch numbers. In this case, create internal batch numbers:

Format: YYMMDD-SEQ (date of receiving + sequential number)

"260303-001" means the first batch received on 3 March 2026. This internal batch links the product to its receiving date, which serves as the reference for shelf life calculation.

Challenge 4: "Existing stock doesn't have batch data"

You have a store full of products without batch records. Options:

• Clean start: Pick a date. All stock received after that date gets batch-tracked. Existing stock is tracked at the product level and gradually sold through. Within 3-6 months (depending on average shelf life), all stock will be batch-tracked.

• Weekend audit: Over a weekend, physically check batch numbers and expiry dates on all products and enter them into the system. Labour-intensive but creates immediate batch visibility.

• Hybrid: Do a weekend audit for high-risk items (top 100 perishable SKUs) and clean-start for everything else.

Option 1 is recommended for most businesses. It requires zero disruption to current operations and achieves full batch coverage within one shelf-life cycle.

Batch tracking for multi-location businesses

For businesses with multiple stores, warehouses, or branches, batch tracking adds a critical capability: inter-location stock transfers with expiry awareness.

When Store A has 20 units of a product with 25 days to expiry, and Store B (which sells 15 units/week of the same product) is running low, a batch-aware system flags this as a transfer opportunity. The transfer saves the stock from expiry at Store A and prevents a stockout at Store B.

Without batch-level visibility across locations, this opportunity is invisible. Each store manages its own inventory in isolation, and transfers happen only when someone manually notices a surplus at one location and a deficit at another.

The technology decision

When evaluating batch tracking software for an Indian business, verify these capabilities:

• [Batch-level inventory](/shelf-life-management) — not just product-level with a batch field, but true batch-level deduction at every transaction
• [FEFO enforcement](/fefo-inventory-management) — automatic at POS, not just a suggestion
• [Invoice OCR](/invoice-scanner) — for fast batch data capture at receiving
• [WhatsApp alerts](/alerts) — because dashboards require remembering to log in
• GST integration — batch records link to purchase and sale invoices for audit trails
• Multi-location — if applicable, batch visibility across all stores
• [FSSAI reporting](/blog/fssai-expiry-compliance-2026-food-business-guide) — quarterly expired stock report generation

ShelfLifePro covers all seven, designed for Indian businesses from single-store pharmacies to multi-location retail chains.

The first step is the smallest

Pick your top 10 products by expiry risk. For the next delivery of each, record the batch number and expiry date. Just those 10. Just once.

Within a week, you will know more about your inventory's expiry profile than you have in years. And that knowledge — specific, actionable, batch-level knowledge — is where waste reduction starts.