How bins, lots, serials, expiry and inventory status work in NetSuite, and how a recall trace actually runs.
Inventory in NetSuite is more than a quantity on hand. Locations, bins, lot and serial numbers, expiry dates and inventory status combine to answer the questions that matter under pressure: can we ship this, where is it, and if something is wrong, what else came from the same source. For manufacturers in food, pharma, medical device and anything audited, this is the module the auditors will actually test.
Traceability is only proven when someone runs it against a real question. In NetSuite the trace works both directions from a lot: backward to the supplier lots of every component consumed, and forward to every finished lot and every customer shipment that included it.
The practical test is time. A trace that takes a day is a trace you will not run until you have to. Food manufacturers should time it before the FSMA 204 compliance date rather than after.
Lots suit anything made in batches. Serials suit equipment and regulated devices where each unit is tracked. Adding either later means a data project, so decide by item class at the start.
Bins add accuracy and effort. If pickers already know where everything lives and accuracy is good, bins can wait. If two people disagree about where an item is, bins are overdue.
The point of quarantine is that not everyone can release it. Set the roles before go-live, not after the first argument.
A supplier notifies you that one lot of a raw material was out of specification. The question from the customer, and possibly from a regulator, is which finished units contain it and where they went.
How long that takes is the honest test of the setup. Where lots are captured at receipt, at issue and at build, it is minutes. Where any one of those three is on paper, it is days, and the answer is a guess with a number attached to it.
Three features decide whether the on-hand number is worth acting on, and they are separate decisions.
The sequence matters. Bins without counts drift within weeks, and statuses without a rule about who can change them become a second, unofficial inventory system.
Native inventory covers the record. Directed picking, mobile scanning and wave planning come with warehouse management. Catch weight, repack traceability and batch genealogy for process manufacturers are what ProShop extends. See also the CPG manufacturing guide.
Yes. Items can be set as lot numbered or serialized, and the number is captured at receipt or at assembly build and carried through every later transaction, which is what makes a two-way trace possible.
Yes. With shelf life managed on lots, picking can follow first expired, first out so the oldest usable stock moves first.
Inventory status marks stock as available, on hold or quarantined without moving it. It keeps nonconforming or untested material out of fulfillment while it is still physically in the warehouse.
A lot number identifies a batch: many units share one number, and the trace runs at batch level. A serial number identifies a single unit, so the trace runs to the individual item. Lots suit anything made in batches, such as food, chemicals and components. Serials suit high-value equipment, anything with a warranty per unit, and anything a regulator wants traced to the device. The choice is made on the item record and is difficult to change once there is history behind it.
Yes. Lot numbered items can carry an expiry date, and NetSuite can be set to pick the earliest expiring lot first rather than the earliest received. That matters wherever shelf life is short: FIFO ships the oldest receipt, which is not always the one closest to expiring. The expiry has to be captured at receipt or at build for it to work, which is the step that gets skipped.
Setting this up, or fixing how it was set up? Get in touch and we will look at it with you. More on the whole production flow in the NetSuite manufacturing guide.
