ERPNext Serial & Batch Tracking: Setup Guide (2026)

I lead ERPNext and Frappe implementations at MithTech, a team of Frappe specialists in Bengaluru. Traceability is the feature pharma, food and electronics buyers ask me about first: serial and batch tracking looks like two checkboxes, but the decisions behind them are hard to reverse. The most expensive traceability mistakes I fix are not wrong settings; they are items that went live with tracking switched off and could not be corrected without recreating the item.

What is serial and batch tracking in ERPNext?

Serial and batch tracking are two optional, per-item settings inside the ERPNext Stock module that attach identity to inventory. A serial number pins down one individual unit and follows it through its whole life. A batch groups many interchangeable units that were made or received together, under one lot identifier with a shared expiry date.

Both features answer the same audit question, "where did this exact stock come from and go?", at different resolutions. Once you enable either, ERPNext prompts for the serial or batch at every relevant document: purchase receipt, delivery note, stock entry, and manufacturing consumption. Because stock and accounting share one ledger, that identity travels with the value, giving regulated businesses the paper trail they are required to keep. For the wider context of how stock documents behave, my ERPNext inventory management guide covers the transaction model this sits on top of.

Skimmable summary: serials track individual units, batches track lots; both add auditable identity to every stock movement.

Serial numbers or batch numbers: which should you use?

Choosing between serials and batches comes down to whether units are individually identifiable or interchangeable. Serial numbers fit high-value, warranty-bound goods where you need per-unit history. Batches fit anything produced or received in lots that share an expiry or manufacturing run. Some items use both: a serialised device built from batch-tracked components.

The trade-off is effort against precision. Serialising fast-moving, low-value stock buries your team in data entry for traceability nobody will ever query. Batching a unique high-value machine loses the per-unit warranty history you actually need. Match the method to how the goods are recalled, warrantied and audited, not to a blanket policy.

Skimmable summary: Use serials for individually identifiable, warranty-bound units; use batches for lot-grouped goods with expiry; combine them only when the product genuinely needs both.

How do you set up serial number tracking in ERPNext?

Serial number setup happens on the Item master before any stock exists for that item. Enabling "Has Serial No" tells ERPNext to demand a serial at every inward and outward movement. Add a serial number series and ERPNext generates the numbers, so your team never types them during receipts.

Skimmable summary: on v16 activate serial/batch in Stock Settings, tick "Has Serial No" on an item with no stock, attach a series, generate serials at receipt, and pick specific units at dispatch.

How do you set up batch tracking with expiry dates?

Batch setup also lives on the Item master and, like serials, must be enabled before any transaction (on v16, after the same Stock Settings switch). Ticking "Has Batch No" reveals batch options including expiry handling and sample retention. For perishables and regulated goods, the two fields that matter most are automatic batch creation and shelf life, which together drive expiry control.

For batch-tracked raw materials feeding production, the same identity flows into your Work Orders and consumption entries, covered in the ERPNext manufacturing guide for India.

Skimmable summary: enable "Has Batch No" on a fresh item, switch on automatic batch creation with a series, and set shelf life so ERPNext derives expiry dates for every lot.

How does ERPNext handle expiry and FEFO dispatch?

Expiry control is where batch tracking earns its keep. Once a batch carries an expiry date, ERPNext compares it with each transaction's posting date and refuses to dispatch stock from an expired batch. Which batch it picks when you leave the batch blank depends on Stock Settings → Pick Serial / Batch Based On: FIFO (the default), LIFO or Expiry. Set it to Expiry and ERPNext picks the batch nearest to expiry first, the First-Expiry-First-Out (FEFO) rule that keeps perishable stock rotating.

With that set, nobody has to eyeball a shelf and guess which lot to ship: the system picks the usable batch that expires soonest and stops anything past its date. Pick Lists follow the same setting, so warehouse staff are guided to the right batch without a separate expiry register.

Skimmable summary: ERPNext blocks expired batches; set picking to "Expiry" for FEFO, and make sure every batch carries an expiry date.

How does serial and batch tracking work for pharma, food and electronics?

Industry fit is what turns two checkboxes into a compliance backbone. Pharma and food lean on batch tracking for expiry, recall, and lot genealogy; electronics and machinery lean on serials for warranty and per-unit history. ERPNext supports both as standard, which is part of why open-source ERP is a realistic option for regulated Indian manufacturers.

Traceability reports tie it together. ERPNext v16 adds a Serial & Batch Traceability report that traces backward (which components and lots built a product) and forward (every customer or location a batch reached). That is the report a recall or audit depends on.

Skimmable summary: Batches serve pharma and food expiry compliance; serials serve electronics and machinery warranty; traceability reports link raw lots to finished units in both directions.

What are the common setup mistakes, and what changed with the Serial and Batch Bundle?

The single most common mistake is enabling tracking too late. ERPNext blocks changing "Has Serial No" or "Has Batch No" once submitted stock transactions exist for the item, to protect ledger integrity. Recovering means cancelling every stock transaction for that item, or creating a new tracked item and moving the stock to it; both are painful after go-live.

A second point that trips up teams upgrading from older versions: how transactions store serials and batches changed. From v15 onward, ERPNext replaced the old free-text serial and batch fields with a dedicated Serial and Batch Bundle document. Each transaction gets its own bundle listing the serials or batches involved, and a bundle cannot be reused across transactions. With "Use Serial / Batch Fields" ticked in Stock Settings, users can still type the serial or batch on the row and ERPNext builds the bundle on submit. ERPNext v16 (January 2026) keeps the bundle model and adds the Stock Settings switch that must be on before items can be serialised or batched. The change fixed real data-integrity problems with the old text fields, but scripts and reports written against the pre-v15 fields need updating.

Skimmable summary: enable tracking before transactions exist, and know that v15 and v16 record serials and batches through a per-transaction Serial and Batch Bundle rather than free-text fields.

Frequently asked questions