Lot tracking is one of those features that looks finished the day it is switched on and only shows its gaps the first time someone asks a hard question: which customers received product made from this supplier lot, and where is the rest of it right now? A manufacturer that can answer in ten minutes has lot tracking. One that needs two days and three spreadsheets has lot numbers. This post covers how lot tracking works in NetSuite, how to set it up for manufacturing, how to trace forward and backward, and how to run a mock recall that proves the setup works before a real one tests it.
How lot tracking works in NetSuite
With the Lot Numbered Inventory feature enabled, an item can be created as lot numbered. From then on, every transaction that moves it, whether a receipt, a transfer, an issue to a work order, a build or a shipment, has to say which lot or lots were involved. NetSuite records that in the inventory detail on each line. Lots can carry an expiration date, and with Inventory Status enabled they can also carry a status such as quarantined, released or on hold, which controls whether that stock can be picked or committed.
The traceability itself comes from those transactions chaining together. A supplier lot is received; it is issued to a work order; the work order produces a finished lot; that lot ships on a sales order. Because every link carries a lot number, NetSuite can walk the chain in either direction. The Lot and Serial Trace view does exactly that, showing where a lot came from and where it went.
Who needs it, and how much of it
Any manufacturer whose customers or regulators may ask for a recall needs lot tracking: food and beverage, nutraceuticals, cosmetics, chemicals, medical devices and anyone supplying them. For food producers handling foods on the FDA’s Food Traceability List, the FSMA 204 rule makes it a legal requirement, with compliance due by July 20, 2028. The rule expects records of critical tracking events and the ability to hand the FDA a sortable spreadsheet within 24 hours of a request, which in practice means the trace has to come out of the system, not out of a filing cabinet.
The useful question is not whether to track lots but which items to track. Tracking every fastener and label adds work at every transaction for no benefit. Track the ingredients and components that carry safety, quality or regulatory risk, plus every intermediate and finished good made from them. Leave genuinely low-risk consumables untracked.
Setting it up for manufacturing
- Enable the features. Lot Numbered Inventory is under Setup, Company, Enable Features, Items and Inventory. Enable Inventory Status if you quarantine incoming material or hold finished lots for release, and Bins if lots need to be found on the shelf as well as in the system.
- Decide the item list. Mark the risk-bearing raw materials, intermediates and finished goods as lot numbered. Converting an existing item usually means creating a new lot-numbered item and moving stock across, so plan this before go-live where possible.
- Define the lot numbering rule. Supplier lot numbers on receipt, your own numbers on production. A consistent format for production lots, such as product, date and batch sequence, makes lots readable on the floor and in a recall.
- Capture expiration dates at receipt for anything with a shelf life, and set the picking rule (first expired, first out) so the system and the warehouse agree.
- Record lots at the point of work. Component lots must be recorded on the work order issue or completion. This is where most traces break, covered below.
Tracing forward and backward
A backward trace starts from a finished lot and asks what went into it: which component lots, from which suppliers, received on which dates. It is the question to answer when a customer complains or a finished lot fails testing. A forward trace starts from a component lot and asks where it went: which work orders consumed it, which finished lots they produced, and which customers received them. It is the question to answer when a supplier tells you an ingredient is contaminated.
Both work in NetSuite as long as every link in the chain carries a lot. A single work order where the component lot was not recorded breaks the chain at that point, and the trace either stops or, worse, looks complete while missing a branch. Our page on inventory and lot traceability in NetSuite covers the setup in more detail.
Why traces break
- Lots reconstructed after the fact. When the floor writes lot numbers on a paper batch sheet and someone keys them in days later, the system records what the office believed was used. That is not the same as what was used.
- Backflushing lot-controlled components. NetSuite needs lot numbers on consumption, so a completion that backflushes lot-numbered components either fails or forces someone to pick lots arbitrarily to get it to save. Lot-controlled components should be issued with the lots actually used. See backflush vs. manual issue for how to set this per component.
- Rework and repack outside the system. Product that is reworked, blended back or repacked without a transaction loses its genealogy at that step.
- Negative inventory on lot items. Lot-numbered items cannot go negative, so teams sometimes work around receipts entered late in ways that scramble lots. The fix is timely receipts, covered in our post on negative inventory in NetSuite.
Running a mock recall
A mock recall is the only reliable test of lot tracking. Run one at least twice a year, and after any significant process change.
- Pick a real lot without warning. Choose a raw material lot received two to three months ago, so it has had time to flow through production and out to customers.
- Start the clock. The target for a food manufacturer should be the FSMA 204 standard of 24 hours; a well-run system gets there in under an hour.
- Trace forward to every work order that consumed the lot, every finished lot produced, and every shipment of those finished lots, with customer, quantity and date.
- Account for every unit. Received quantity should reconcile to consumed, on hand, scrapped and shipped. A gap is the finding.
- Trace one finished lot backward to confirm the chain works in the other direction too.
- Write up the gaps and fix them at the source: usually a step where lots are not captured at the point of work.
Capturing lots where the work happens
Almost every broken trace comes back to the same cause: the lot was not recorded at the moment the material was used. Consule’s FactoryBridge puts work order execution on a tablet at the line, so operators scan the component lot as they add it and the finished lot is created at completion. For batch producers, ProShop records the actual lots, substitutions and quantities that went into each batch, which is what a regulator expects a trace to show. Both write straight into NetSuite’s own lot records, so the native trace keeps working.
Consule Solutions implements lot traceability for food, chemical and other process manufacturers on NetSuite and runs mock recalls as part of go-live. If your last trace took longer than it should have, talk to our team. For industry specifics, see our pages on food and beverage and process manufacturing.
Frequently asked questions
Does NetSuite support lot tracking?
Yes. With the Lot Numbered Inventory feature enabled, items can be set up as lot numbered and every transaction records the lots involved. Lots can carry expiration dates and, with Inventory Status enabled, statuses such as quarantined or released. The Lot and Serial Trace view shows where a lot came from and where it went.
What is the difference between lot tracking and serial tracking?
A lot number identifies a quantity of material produced or received together, such as a batch of 500 kilograms. A serial number identifies a single unit. Process and food manufacturers usually use lots; makers of equipment and devices use serials for finished units and often lots for the components inside them.
Is NetSuite FSMA 204 compliant?
No software is compliant on its own; compliance depends on what is recorded. NetSuite can hold the lot genealogy FSMA 204 requires and produce the trace as a report, but only if lots are captured at every critical tracking event, including receiving, transformation in production and shipping. The compliance date is July 20, 2028.
How do you run a mock recall in NetSuite?
Pick a raw material lot received a few months ago, trace it forward to every work order, finished lot and customer shipment, and reconcile the received quantity to consumed, on hand, scrapped and shipped. Then trace one finished lot backward. Time the exercise and fix any step where the chain breaks.
Can lot-numbered components be backflushed in NetSuite?
Not blindly. NetSuite requires lot numbers when lot-numbered components are consumed, so the completion has to specify which lots were used. Most manufacturers issue lot-controlled components manually, or capture the lots at the line, and backflush only untracked, low-value components.