Batch & Serial Number Tracking in ERP: Traceability, Recalls & Expiry Control

There is a question that decides whether a bad day at an Indian factory stays a bad day or becomes a bad year: "Which batch was that from?" A customer calls about an off-smell in a consignment of edible oil, a distributor flags tablets that failed a field check, an OEM reports a pump that seized in the first month — and everything that happens next depends on how fast, and how precisely, you can answer. If the answer is a shrug and a scramble through delivery challans, you are about to recall far more stock than you need to, alarm customers who were never affected, and spend weeks proving a negative. If the answer is a batch number that instantly reveals where that lot went and what went into it, you contain the problem to the exact units at risk and move on.

That gap — between a shrug and a batch number — is what batch and serial tracking closes. It is not a nice-to-have reporting feature; for pharma, food, chemicals, electronics and auto components it is the difference between a targeted correction and an existential one. Regulators expect it, large buyers audit for it, and the cost of not having it shows up all at once, on the worst possible day, in rupees you did not budget for.

The good news is that traceability is exactly the kind of disciplined, document-linked, high-volume work an ERP absorbs without adding effort on the floor. When the batch or serial is captured at the moment stock is received and then carried automatically through production, storage and dispatch, traceability becomes a by-product of running the operation — not a separate register someone has to maintain. This article explains the difference between batch and serial tracking, why each matters, the industries that depend on them, how it all works end-to-end inside ApicalERP, and — with a worked rupee case study — what a manual recall actually costs versus an ERP-driven one.

Batch vs Serial: Two Different Answers to "Which One Was It?"

People often use "batch" and "serial" interchangeably, but they solve different problems and are configured differently in an ERP. Getting the distinction right at the item level is the foundation everything else rests on.

Batch (Lot) Tracking — grouping units that share a story

A batch, or lot, is a group of units produced or received together that share the same attributes — the same manufacture date, the same expiry, the same supplier lot, the same quality certificate. A production run of 50,000 tablets is one batch. A tanker of edible oil decanted into 2,000 pouches is one batch. A dye lot of 3,000 metres of fabric is one batch. You do not track each tablet or pouch individually; you track the batch as a quantity that moves through stock and out on dispatch, and you rely on the fact that every unit in it is identical. Batch tracking is the right model whenever goods are consumed or sold by quantity and share a shelf-life or quality profile — which is why it dominates pharma, food, chemicals, cosmetics and agro-inputs.

Serial Number Tracking — a unique identity per unit

A serial number identifies one individual unit uniquely and follows it for life — one motor, one laptop, one gearbox, one instrument, each with its own number carried from inward through sale, warranty and service. Serial tracking is the right model when each unit needs its own identity: to validate a warranty claim, to hold a service history, to enforce accountability on a high-value item, or to prove which specific unit went to which customer. Electronics, appliances, machinery, pumps and instruments live on serial tracking.

When you need both

The two are not mutually exclusive — mature manufacturers use both in the same ERP on different items. An auto-component maker batch-tracks incoming steel, castings and consumables for traceability and quality, then serial-tracks the finished assemblies that carry a warranty. An electronics assembler batch-tracks components and PCBs, then serializes the finished device. The point is that the system supports either mode, item by item, and links them: a serial-tracked finished unit can record exactly which batches of raw material were consumed to build it, so a defect traced to a component batch instantly reveals every serial number it went into.

Why Batch & Serial Tracking Actually Matters

It is easy to treat traceability as a compliance checkbox until the day it earns its keep. In practice it protects the business in five distinct ways, each of which quietly saves money and reputation long before any crisis.

Recalls become targeted, not total

Without batch traceability, a defect found in the field forces a choice between two bad options: recall everything that might be affected, or hope it is isolated and risk shipping more bad product. Both are expensive — one in write-offs and logistics, the other in liability. With batch genealogy, you isolate the exact affected lot, identify precisely which customers received it, and quarantine remaining stock of only that batch. The recall shrinks from "all product in the last three months" to "batch B-2417, these eleven customers" — a difference measured in lakhs.

Expiry and shelf-life stop leaking money

Shelf-life goods that are not tracked by expiry expire on the shelf, and every expired unit is a straight write-off plus the cost of disposing of it safely. Batch tracking with expiry dates and FEFO picking means the oldest-to-expire stock always moves first, near-expiry lots are flagged for action while they still have value, and expiry write-offs fall towards zero. For a business carrying seasonal or slow-moving SKUs, this alone often pays for the system.

Warranty claims are validated, not guessed

When a serialized product comes back under warranty, the serial number instantly reveals its manufacture date, batch of components, dispatch date and customer — so genuine claims are honoured quickly and out-of-warranty or grey-market units are identified rather than serviced by mistake. That both improves customer experience on legitimate claims and stops warranty leakage on illegitimate ones.

Root cause becomes findable

Backward traceability — from a finished batch to the raw-material lots that made it — turns quality investigation from guesswork into evidence. When several finished batches show the same defect, genealogy reveals the common input: a specific supplier lot, a particular resin batch, one shift's run. Fix that, and you prevent the next failure instead of just cleaning up this one. This is where traceability and quality control reinforce each other.

Compliant, defensible stock movement

Batch numbers carried onto the tax invoice, delivery challan and e-way bill mean the lot that physically moved is the lot documented — essential for branch transfers, job-work challans, sales returns and credit notes. For regulated goods, printing manufacture and expiry alongside the batch is often a statutory requirement, and a batch-aware ERP produces the compliant document automatically.

The Capabilities That Make Traceability Effortless

The difference between traceability as a burden and traceability as a by-product comes down to a handful of system capabilities — each removing a manual register or a moment where the thread of identity could break.

How It Works End-to-End Inside ApicalERP

Traceability only works if the batch or serial is never lost between one step and the next. In ApicalERP the identity is captured once, at inward, and then travels with the stock through every transaction automatically — nobody re-keys it, so nobody can break the chain.

Inward: identity is fixed at the door

When materials arrive, each lot is booked against its goods-receipt note with a batch number, supplier lot reference, manufacture date and expiry. Serialized items get their serials captured at the same moment. From this instant the stock is fully identified, and every later movement inherits that identity rather than needing it re-entered. This is where good warehouse management and traceability meet: batch stock is held bin-wise, so the physical location and the logical batch stay in step.

Quality gate: batch status controls availability

Incoming inspection is recorded against the batch, and the result governs what happens next. Rejected or under-test lots are quarantined — visible in stock but not available to issue — while approved lots carry their QC status and certificate of analysis forward. Because status lives on the batch, a lot can never be accidentally consumed before it clears, and the inspection record is always one click from the batch it belongs to.

Production: genealogy is built as materials are consumed

When a production order draws materials against its bill of materials, the exact batches issued are recorded against the run. The finished output then receives its own batch (or serials) with fresh manufacture and expiry dates. In that single step, ApicalERP builds the genealogy link — this finished batch was made from those input lots — which is the backbone of every future recall and root-cause investigation. Tie this to disciplined production planning and every run is traceable end to end.

Stock: batch-wise balances, FEFO-aware

Inventory is held not just as "3,200 units of SKU X" but as batch-wise balances, each with its own expiry and location. When it is time to pick, the system proposes the correct batch by expiry (FEFO) or receipt order (FIFO), so warehouse staff move the right stock without having to read dates off cartons and reason about rotation themselves.

Dispatch: the batch rides the document

At dispatch, the batch or serial is stamped onto the invoice, delivery challan and e-way bill, and linked to the customer. Forward traceability is now complete: from any batch you can list every customer, invoice and quantity that received it. For serialized goods, the serial-to-customer link becomes the spine of the warranty record.

Recall & warranty: one lookup, both directions

Because identity was preserved at every step, the payoff is a single lookup. Enter a batch, and ApicalERP shows every customer it reached (to notify and recall) and every input lot it came from (to find the cause). Enter a serial, and it shows the unit's full history — build date, component batches, dispatch, customer, and warranty status — so a claim is validated in seconds. The lifecycle that took seven careful steps to build collapses, at the moment of crisis, into one instant answer.

Industries That Cannot Operate Without It

Some businesses can treat traceability as optional. These cannot — for them it is a licence to operate, a condition of supply to large buyers, or a legal obligation.

Pharmaceuticals & nutraceuticals

Batch numbers, manufacture and expiry dates, and full backward-forward traceability are non-negotiable. Recalls must be executable at batch precision, retest dates tracked, and every finished lot linked to its raw-material lots and quality certificates. This is the most demanding traceability environment, and the one where a manual system fails most expensively.

Food & beverage processing

Edible oils, spices, snacks, dairy and packaged foods carry shelf-life and food-safety obligations. FEFO rotation, expiry alerts and batch recall capability protect both the consumer and the brand, and large retail and export buyers audit for exactly this before they place orders.

Chemicals, paints & cosmetics

Lot-to-lot consistency, shelf-life, safety documentation and batch-level recall matter across chemicals, coatings, adhesives and personal care. Dye lots and colour batches also need traceability so that a shade complaint maps to the exact production run.

Electronics & appliances

Serial tracking anchors warranty and service, while batch tracking on components lets a defective capacitor or board lot be traced to every finished serial it entered — the two modes working together to contain a component-level fault without recalling good units.

Auto components & machinery

OEM supply chains demand traceability from their vendors: batch-tracked raw materials and castings for quality investigation, and serial-tracked finished assemblies for warranty and field-failure analysis. A traceability gap can cost the vendor the OEM relationship entirely.

Benefits of Running Traceability Inside the ERP

Implementation Checklist: Getting Traceability Right

Batch and serial tracking succeeds or fails on setup discipline. The businesses that get clean traceability from day one follow the same handful of steps — deciding modes deliberately, capturing identity at the earliest point, and never letting the chain break.

1. Decide the tracking mode item by item

• Classify every item: batch-tracked (shelf-life or quality-grouped), serial-tracked (warranty or high-value individual), or neither — and set it in the item master so the choice is enforced, not left to the person entering a voucher
• Define batch attributes each item needs — manufacture date, expiry, supplier lot, QC status, retest date — so nothing essential is missing when the batch is created

2. Capture identity at the earliest possible point

• Assign the batch or serial at goods receipt, not at dispatch, so the whole downstream chain inherits it automatically and nobody re-keys it
• Use a consistent batch-numbering scheme — encode date and line where helpful — so batch numbers are meaningful and collision-free across the year

3. Wire batch consumption into production

• Record the exact batches issued against each production order so finished-goods genealogy is built automatically as the run consumes materials
• Assign a fresh finished-goods batch with manufacture and expiry dates to every production output, so output is traceable in both directions from the moment it exists

4. Enforce FEFO/FIFO and expiry alerts

• Turn on batch-suggested picking by expiry (FEFO) for shelf-life goods and by receipt order (FIFO) where that governs, so rotation is automatic rather than dependent on floor judgement
• Set alert windows per item so near-expiry batches surface while they still have value, and block expired lots from saleable stock

5. Carry the batch onto every document and rehearse a recall

• Print batch or serial on the invoice, delivery challan and e-way bill so compliant, traceable documentation is automatic at dispatch
• Run a mock recall on a real batch during rollout — trace it forward to customers and backward to inputs — so the team trusts the system before a real event tests it

What a Recall Actually Costs: Manual vs ERP-Driven

The value of traceability is abstract until a recall puts a number on it. Consider a mid-size food processor that discovers a contamination issue in one production run. Under a manual system, the batch that shipped cannot be cleanly separated from adjacent runs, so the recall is cast wide to be safe — say three months of that SKU, roughly ₹40 lakh of finished goods pulled back, of which perhaps only ₹6 lakh was genuinely at risk. On top of the ₹34 lakh of needlessly destroyed good stock come the logistics of retrieving it, the credit notes to hundreds of distributors who were never affected, days of staff time reconstructing where product went, and the reputational hit of a broad public recall.

Under an ERP-driven recall, the affected batch is isolated in minutes. Only the ₹6 lakh genuinely at risk is recalled, from the eleven distributors who actually received it; the root cause is traced backward to a single supplier lot of an input, quarantined so it cannot recur; and the recall is quiet, targeted and defensible to any regulator. The write-off falls from ₹40 lakh to ₹6 lakh, the logistics and credit-note load shrinks proportionally, and the brand damage is contained to the customers involved rather than the whole market. That single event — one recall — can justify the entire traceability investment several times over, before counting the expiry write-offs and warranty leakage it prevents every ordinary month.

Real-World Success Story

Frequently Asked Questions

What is the difference between batch tracking and serial number tracking?

Batch (or lot) tracking groups many identical units made or received together under one batch number — a run of tablets, a lot of oil, a dye lot of fabric — all sharing the same manufacture date, expiry, supplier lot and quality certificate, and tracked as a quantity. Serial tracking identifies each individual unit uniquely — one motor, one laptop, one pump — with its own serial carried from inward through sale into warranty and service. Use batch tracking when units are consumed or sold by quantity and share a shelf-life or quality profile; use serial tracking when each unit needs its own identity for warranty, service history or high-value accountability. Many businesses need both, on different items, in the same ERP.

Which industries need batch and serial number tracking?

Batch tracking is essential wherever products have a shelf-life, a quality certificate or a recall obligation — pharmaceuticals, nutraceuticals, food and beverage, spices, edible oils, chemicals, paints, cosmetics and agro-inputs. Serial tracking is essential wherever units carry warranty or service history — electronics, appliances, motors, pumps, auto components, machinery and instruments. Auto-component and electronics makers frequently use both: batch tracking on raw materials and components for traceability, and serial tracking on finished units for warranty and field-failure analysis.

What is FEFO and how does it differ from FIFO?

FIFO — First In, First Out — issues the oldest-received stock first, by the date it entered the godown. FEFO — First Expiry, First Out — issues the stock that expires soonest first, by each batch's expiry date, regardless of when it arrived. For shelf-life goods FEFO is safer, because a batch received later can carry an earlier expiry that FIFO alone would leave to expire on the shelf. A batch-aware ERP suggests the correct batch to pick by expiry at dispatch, so staff physically rotate stock in the sequence that minimises expiry write-offs.

How does batch tracking help with a product recall?

A recall is only as fast as your ability to answer two questions: where did this batch go, and what went into it. Batch genealogy links a batch number backward to every raw-material lot and supplier that fed the run, and forward to every customer, invoice and quantity that received finished goods from it. So a defect is isolated to the exact affected batch — not your whole stock — the precise customers are identified, remaining stock is quarantined instantly, and the root cause is traced to a specific input lot. The recall becomes a targeted action against a named batch rather than a panicked, guess-the-scope sweep across all customers.

Does batch and serial tracking affect GST compliance?

Batch and serial details are not a separate GST levy, but they make compliant stock movement cleaner and defensible. Batch numbers carry onto the tax invoice, delivery challan and e-way bill, so the lot that physically moved is the lot documented — important for branch transfers, job-work challans, sales returns and credit notes. When goods are returned, the batch ties back to the original dispatch so stock and input-tax positions reconcile. For regulated goods, printing manufacture and expiry alongside the batch is often statutory, and a batch-aware ERP produces the compliant document automatically.

Conclusion

Batch and serial tracking is not conceptually complicated — it is simply the discipline of never losing a thread of identity from the moment stock enters to the moment it reaches a customer. What makes it hard in a spreadsheet world is that the thread has to survive dozens of movements a day, across receiving, quality, production, storage and dispatch, and in that world it always eventually snaps. When it does, the cost is not spread out; it lands all at once, on the day a recall or a warranty dispute or an audit tests exactly the link that broke.

The lifecycle — capture the batch or serial at inward, gate it through quality, build genealogy in production, hold and pick it by expiry, carry it onto the dispatch document, and trace it in both directions on demand — is not extra work when the system that already records the receipt and the issue carries the identity for you. It turns traceability into a by-product of running the operation well, and turns "which batch was that from?" from a dreaded question into a one-line answer. Alongside disciplined quality control and accurate warehouse management, batch and serial tracking is what lets a manufacturer contain a bad batch instead of being contained by it. ApicalERP tracks every lot and every unit end to end — FEFO picking, expiry alerts, two-way genealogy and batch-on-the-document built in. See the full ApicalERP feature set and the manufacturing solution, then bring us one product and one recent recall scare — we will show you what it looks like when every batch answers for itself.