Executive Summary: In ERP, a lot is a group of units produced or received together and identified by one number. LOT is not an acronym. Lot tracking records where each lot came from, what it went into, and who received it, so a manufacturer can isolate a quality problem to specific units instead of an entire product line. SAP Business One handles this through batch management, which ties batch numbers, dates, and statuses to every inventory transaction.
A lot is a quantity of product made or received under the same conditions. Every unit in it shares one lot number. ERP systems use that number to follow inventory from the supplier's dock to the customer's door.
People often search "LOT" in capitals and expect an acronym. There isn't one. It's the ordinary word "lot," often printed in caps on labels and system screens.
The definition is simple. The value comes from what an ERP does with the number. Lot tracking is a core function of manufacturing ERP software, and it's the difference between recalling three pallets and recalling a season's worth of product.
A lot is a defined quantity of an item with a common origin. That usually means the same production run, the same supplier shipment, or the same raw material batch.
The ERP stores the lot number on every transaction that touches the lot. Receipts, transfers, production issues, shipments, and returns all carry it. That unbroken record is what makes tracing possible.
A lot number is the unique identifier for one lot. It can come from the vendor, from the ERP, or both. Many manufacturers record the supplier's lot number at receiving and assign their own internal number at the same time.
A typical lot record looks like this:
In practice, yes. Most ERP systems and most industries use "lot" and "batch" interchangeably. Some process manufacturers use "batch" for the production run and "lot" for the resulting inventory. Others use one word for both.
SAP Business One uses "batch." Its batch management features are what other systems call lot tracking.
"Lot" also appears in an unrelated ERP context. In material requirements planning (MRP), lot sizing decides how much to order or produce at once. Lot-for-lot (L4L) is one lot sizing rule: order exactly the net requirement for each period.
Lot sizing is a planning decision. Lot tracking is an inventory record. If you came from an MRP course or a planning screen, lot-for-lot is the term you want. The rest of this article covers lot tracking.
Lot tracking attaches a lot number to inventory the moment it enters the system. After that, every movement requires the number. The chain holds only if no transaction skips it.
A lot moves through five stages:
Receiving starts the chain. The receiving clerk records the supplier's lot number, the quantity, and any dates printed on the container. The ERP then assigns or confirms the internal lot number.
Quality teams often hold new lots until inspection clears them. A held lot stays in inventory but can't be issued to production or shipped.
Production is where lots multiply. A production order consumes specific component lots and creates a new finished goods lot. The ERP links them, so the finished lot carries a record of every ingredient lot inside it.
This link is called lot genealogy. Spreadsheets have the hardest time keeping it intact.
Partial lots add complexity. One raw material lot can feed several production runs. One run can also draw from several lots of the same ingredient. A good ERP records the exact quantity of each lot consumed by each order.
Shipping closes the loop. Each delivery records which finished lots went to which customer, and how many units. Returns come back into inventory under the lot number they left with.
Traceability runs in two directions.
Both directions use the same records. Only the starting point changes.
Here's how one ingredient lot moves through a fictional shampoo manufacturer.
The company receives 500 kg of surfactant. The supplier's lot number is SUP-88213. At receiving, the ERP assigns internal lot RM-0412.
Two production runs draw from RM-0412:
The remaining 20 kg of RM-0412 stays in the raw materials warehouse.
Two weeks later, the supplier reports contamination in SUP-88213.
A forward trace from RM-0412 returns the full exposure in minutes:
The company places the raw material and the 250 bottles on hold. It contacts three customers with specific lot numbers and quantities.
Without lot tracking, the company knows only that SHAMPOO-500 is affected. Every bottle of that SKU from the period becomes suspect, at every customer.
Backward tracing works the same way in reverse. Say Retailer A reports a complaint about a bottle from SH-2610-A. A backward trace lists every component lot in that run: the surfactant, the fragrance, the bottles, the caps. Each one points to a supplier and a receipt date. QC knows exactly what to test.
Some lot data is standard in nearly every ERP. Other data depends on the system, the modules licensed, and how it's configured.
Lot tracking narrows a recall from a product line to specific lots. In the shampoo example, the scope dropped from every bottle of a SKU to three customers and one warehouse. Smaller scope means lower cost, less waste, and fewer strained customer relationships.
Every quality problem gets a starting point. When defects recur, lot records show whether they trace to one supplier, one production line, or one ingredient. Supplier conversations shift from opinion to evidence.
Lot-level records show exactly which lots are on hand and where. Cycle counts verify specific lots, not just item totals. Discrepancies are easier to locate, and that's one of the ways SAP Business One helps reduce inventory variance.
FIFO (first in, first out) ships the oldest received stock first. FEFO (first expired, first out) ships the stock that expires soonest.
The two usually match. They split when a newer receipt has a shorter remaining shelf life than older stock. For perishable goods, FEFO is the safer rule. It only works if every lot carries an expiration date.
Many regulations and customer standards require lot-level records. Auditors and certification bodies often ask for a trace on the spot. An ERP produces it from records that already exist. A spreadsheet produces it after hours of searching.
These three identifiers work at different levels.
One SKU has many lots over time. One lot contains many units. A serial number tracks a single unit.
Lot tracking fits products made in batches and consumed: food, chemicals, cosmetics, pharmaceuticals. Serial tracking fits durable items that need warranty or service history, like equipment and electronics. Some items need both.
SAP Business One handles lot tracking through batch management. The setting applies item by item. A company can batch-manage ingredients and finished goods while leaving low-risk supplies untracked.
Batch management is enabled in each item's master data. Two management methods control when a batch number is required:
Manufacturers that need full traceability generally choose on every transaction. Release-only leaves stock in inventory without a batch number until it ships.
Batch numbers can be entered manually or created automatically from a defined numbering string. Automatic creation keeps formats consistent across receipts and production.
Each batch stores its own details. These include expiration date, manufacturing date, admission date, location, and free-text notes. Batch attribute fields can hold additional identifiers, such as the supplier's lot number.
Every batch also carries a status: Released, Not Accessible, or Locked. Released batches move normally. The other two statuses restrict which documents can issue the batch, which supports quality holds. Enforcement varies by document type, so test it in your own system before relying on it for quarantine.
Production orders issue specific component batches and receive the finished product into a new batch. That link builds batch genealogy inside SAP Business One. For the broader production workflow, see our guide to managing production and manufacturing in SAP Business One.
SAP documents forward and reverse batch and serial trace reports in the Inventory module. The Batch Number Transactions Report lists every receipt, issue, and allocation for a selected batch. Together, they answer both traceability questions from standard data.
Standard SAP Business One covers batch numbering, dates, statuses, production links, and transaction-level tracing. Some requirements go further. Automated FEFO picking, lab results tied to batches, graphical multi-level genealogy, and formal quality workflows typically need configuration work or certified add-ons.
For a quick capability overview, see Can SAP Business One Handle Batch and Serial Numbers?
Turning on batch management is the easy part. The real work is the process around it.
Innormax helps manufacturers decide which items need batch management and which don't. We set numbering conventions, configure receiving and production steps so batch numbers can't be skipped, and train warehouse and production teams on the new workflow. The goal is a trace your team can run in minutes, the first time an auditor asks.
Any company that makes or moves consumable goods benefits. Some industries treat it as mandatory.
Distributors are easy to overlook here. They don't produce anything, but a supplier recall still requires them to know which customers received which lots.
Pharmaceutical companies face the strictest requirements. Our article on pharmaceutical compliance and ERP covers that environment in more detail.
Most lot tracking failures are process failures. The software records what people enter.
LOT doesn't stand for anything. It's the word "lot," meaning a group of units produced or received together under one identifying number. It often appears in capitals on labels and ERP screens.
No. A SKU identifies a product type, such as a 500 ml shampoo. A lot number identifies one specific group of that product, such as the 1,000 bottles made in one production run. One SKU has many lots over time.
Yes, if every transaction records them. Forward tracing follows a lot from the supplier to the customers who received it. Backward tracing follows a finished lot back to its component lots and suppliers.
There's usually no practical difference. Most ERP systems and industries use the terms interchangeably. SAP Business One calls the feature batch management.
Yes. SAP Business One supports batch numbers with expiration and manufacturing dates, batch statuses, production order links, and forward and reverse trace reports. Advanced needs like automated FEFO picking or lab result tracking typically require configuration or add-ons.
No. Lot-for-lot is an MRP lot sizing rule that orders exactly the net requirement for each period. Lot tracking is an inventory record that follows specific lots through the supply chain. They share a word and nothing else.
A recall is the worst time to discover a gap in your lot records. The supplier call comes in, and the questions start: which lots, which customers, how many units. Lot tracking turns those questions into a report.
The technology is mature. The difference between companies that trace in minutes and companies that trace in days is how consistently lot numbers get captured, from receiving to shipping.
If you're evaluating lot tracking in SAP Business One, or your current setup can't produce a clean trace, talk to the Innormax team.
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
Unordered list
Bold text
Emphasis
Superscript
Subscript