Services
Industry
Resources
Company
Summarize this blog post with:
TL;DR
• Batch traceability tracks groups of units made together. Serial traceability tracks individual units. Most regulated manufacturers need both.
• The test of a traceability system is a mock recall: pick a finished batch, identify every raw material lot in it and every customer who received it. Target is under four hours.
• India tightened the rules in 2026. A June 2026 notification expanded QR code traceability under Schedule H2 of the Drugs Rules, 1945 beyond the top 300 brands to all vaccines, antimicrobials, anti-cancer drugs, and narcotic and psychotropic medicines, on a phased timeline.
• Traceability works only when the ERP holds genealogy: the links between raw material lots, work orders, output batches and shipments.
• The failure point is almost never the software. It is manual steps at goods receipt, sub-assembly and dispatch where lot identity gets dropped.
• Start by making lot capture mandatory at three points: receipt, consumption and dispatch.
Every manufacturer says they can trace a batch. Fewer can prove it under time pressure.
The honest test is not whether the data exists somewhere. It is whether a quality head, given a batch number at 10am, can name every affected customer by lunchtime. Most cannot, because the chain breaks at one or two manual handoffs that nobody thought of as critical.
Batch or lot traceability tracks a quantity of product manufactured together under the same conditions. Food, pharmaceuticals, chemicals, paints and cosmetics use it because units are not individually distinguishable.
Serial traceability tracks each unit with a unique identifier. Automotive components, electronics, medical devices and industrial equipment use it because individual units matter for warranty, service and safety.
Many manufacturers need both. A pharmaceutical company batches the tablets and serialises the shipper cartons. An automotive supplier batches the raw casting and serialises the finished assembly.
Forward traceability answers: this raw material lot was defective, where did it go?
Backward traceability answers: this finished unit failed, what went into it?
A system that only does one of these is half a system, and the missing half is usually forward traceability.
Indian manufacturers now operate under noticeably tighter traceability expectations than they did three years ago.
In pharmaceuticals, the government created Schedule H2 under the Drugs Rules, 1945 in November 2022, and from 1 August 2023 manufacturers of the country’s top 300 drug brands had to print or affix a barcode or QR code on medicine packs carrying batch number, expiry date, manufacturer details and other data elements.
In June 2026, the Ministry of Health and Family Welfare expanded that framework substantially. QR code-based traceability now extends to all vaccines, antimicrobials, anti-cancer medicines, and narcotic and psychotropic drugs, applied in phases, with antimicrobials covered from 1 July 2028. The shift is significant: coverage moved from a revenue-based list of brands to entire risk-based therapeutic categories. GS1 India has noted that harmonised global standards matter here, because Indian medicines trade internationally and fragmented systems create friction at borders. For a fuller breakdown of what this means operationally, including how Schedule M batch record requirements and lot traceability fit together in a single system, see our guide to NetSuite for Indian pharmaceutical companies.
Food manufacturers face parallel expectations through FSSAI recall and labelling requirements, and export-oriented manufacturers face customer-mandated traceability that is often stricter than domestic law.
The practical consequence is the same across sectors. Traceability is moving from a quality department capability to a systems capability, because manual records cannot support serialised data at pack level, a shift we cover in more depth in our overview of ERP for the manufacturing industry in India.
Traceability is not a report. It is a data structure.
Genealogy is the recorded chain of links between:
• Supplier lot received
• Storage location and any repacking
• Work order that consumed it
• Sub-assemblies produced
• Finished batch or serial produced
• Sales order, shipment and customer
Each link must be captured at the moment the transaction happens. Reconstructing it later from delivery notes and production diaries is exactly the exercise that turns a four-hour recall into a four-day one.
The three points where the chain most often breaks:
1. Goods receipt- Material accepted without recording the supplier lot, or lots merged into one bin.
2. Sub-assembly and rework- Components pulled from an unlabelled WIP tray and consumed without lot capture.
3. Dispatch- Picking without scanning, so the shipment records a quantity but not which batch went to which customer.
Fix those three and most traceability problems disappear.
The capabilities to specify:
• Lot and serial numbering rules configured by item, with automatic generation and format control.
• Mandatory capture at transaction points, enforced by the system rather than by training. If the system allows a receipt without a lot number, someone will do it.
• Expiry and shelf-life management, including FEFO picking where relevant, with automatic blocking of expired stock.
• Quality holds that follow the lot, so a hold placed in quality immediately blocks the material for picking, production and shipping.
• Full genealogy inquiry in both directions, from a single screen, without an export.
• Recall simulation, so mock recalls can be run without disturbing live records.
• Retained sample and certificate of analysis linkage, so documents attach to the lot rather than sitting in a folder.
Oracle NetSuite handles lot and serial tracking, expiry management and quality holds within its inventory and manufacturing modules, which suits mid-market manufacturers who want traceability in the same system as their financials. SAP and Microsoft Dynamics 365 cover similar ground at larger scale. Sector-specific platforms such as those built for GxP environments add validation documentation, and Tulip is often used for the frontline data capture layer. SaasWorx configures this specific capability set, including QC quarantine enforcement, BOM-level genealogy and recall simulation, as part of its NetSuite lot traceability and serial number tracking implementations for Indian manufacturers, so the traceability logic sits inside the same instance that runs your financials rather than as a bolt-on.
For pack-level serialisation and regulatory reporting, most Indian pharmaceutical manufacturers layer a serialisation solution above the ERP that handles code generation, printing, vision verification and aggregation.
This is the exercise that reveals whether the system works.
1. Choose a finished goods batch dispatched in the last six months. Pick at random, not the easy one.
2. Start a clock.
3. Identify every raw material lot consumed in that batch, and the supplier for each.
4. Identify every other finished batch that used those same raw material lots.
5. Identify every customer, quantity and dispatch date for all affected batches.
6. Identify remaining stock of the affected batches in your own warehouses and in transit.
7. Stop the clock.
• Under 2 hours: Strong. Your genealogy is intact and your data capture is disciplined.
• 2 to 4 hours: Acceptable for most sectors, and the standard many customer audits expect.
• 4 to 24 hours: You have manual links in the chain. Find them, because they are the same links that will fail in a real event.
• Over 24 hours: You do not have traceability. You have records.
Run it quarterly, rotate who runs it, and write down where the time went. The log of where time was lost is more valuable than the result.
A recall costs more than the product returned. The full cost includes:
• Product replacement and logistics
• Investigation and root cause work
• Regulatory reporting and inspection response
• Customer credits and penalty clauses
• Line downtime during containment
• Legal exposure and insurance impact
• Brand damage, which is real but difficult to quantify
Narrow traceability directly reduces most of these. A manufacturer who can prove that only three batches are affected recalls three batches. A manufacturer who cannot recalls three months of production. That difference is usually larger than the entire cost of the traceability system, and it compounds the same margin pressure we’ve written about in how stockouts and excess inventory quietly erode manufacturing margins: both problems come from the same root cause, inventory and lot data that isn’t trustworthy in real time.
This is the argument to take to a board. Traceability is not a compliance cost. It is a containment capability, and its value is measured by how much of a recall you do not have to do.
1. Decide the tracking level per item: Not everything needs serialisation. Match the level to risk, regulation and customer requirement. Over-tracking creates transaction burden that erodes compliance.
2. Make lot capture mandatory at receipt, consumption and dispatch: System-enforced, not policy-enforced.
3. Deploy barcode scanning at those three points: Manual keying of lot numbers produces error rates that make genealogy unreliable. This is usually where an integration and automation layer connecting scanners, printers and the ERP in real time pays for itself fastest.
4. Standardise on GS1 identifiers where you export or supply regulated markets: Proprietary formats create rework later.
5. Connect quality holds to inventory status: This single link prevents most of the shipments that turn into recalls.
6. Run a mock recall: Then fix what it exposed.
7. Extend to supplier lot data by requiring lot numbers on inbound documentation and, for critical materials, advance shipping notices.
• Bin merging: Two supplier lots in one bin destroys backward traceability, regardless of what the ERP records.
• Optional fields: A lot number field that can be left blank will be left blank during a rush.
• Rework without identity: Reworked material re-entering production without carrying its original lot reference.
• Spreadsheet bridges: Any point where data leaves the system and returns manually is a break in the chain.
• Untested systems: Traceability that has never been tested under time pressure is an assumption, not a capability.
Batch tracking assigns one identifier to a quantity produced together under the same conditions. Serial tracking assigns a unique identifier to each individual unit. Batch suits food, pharmaceuticals and chemicals. Serial suits automotive components, electronics and medical devices. Many manufacturers use both at different packaging levels.
Schedule H2 of the Drugs Rules, 1945 specifies drug formulations that must carry a barcode or QR code on the packaging for authentication and traceability. It applied to the top 300 brands from 1 August 2023, and a June 2026 notification expanded it to all vaccines, antimicrobials, anti-cancer medicines and narcotic and psychotropic drugs on a phased timeline.
Under four hours from batch number to a full list of affected customers, quantities and remaining stock is the working standard many customer audits expect. Under two hours indicates a well-implemented system with disciplined data capture.
Most mid-market manufacturers can meet requirements within the ERP if lot and serial control, expiry management and quality holds are properly configured. Pack-level serialisation for regulated pharmaceuticals usually requires an additional layer for code generation, printing and aggregation. Our own manufacturing industry practice configures this inside a single NetSuite instance for most mid-market clients before recommending anything additional.
Manual handoffs. Data capture that depends on someone remembering to write a lot number, particularly at goods receipt and dispatch. System-enforced capture with barcode scanning removes most of the risk, and the same audit trail discipline, a record of who approved every exception, and a log that can’t be edited after the fact, is what makes the system hold up under a customer or regulator audit, a point we cover in more depth in what makes a NetSuite instance genuinely audit-ready.
Traceability gets treated as paperwork until the day it becomes the only thing that matters. On that day, the difference between a contained event and a company-defining one is whether the links in the chain were captured at the moment they happened.
Test it before someone else does.
SaasWorx works with manufacturers on ERP lot and serial control, quality integration and traceability readiness across regulated and export-facing operations.
