How to Set Up Lot and Serial Number Tracking in SyteLine
how to set up lot and serial number tracking in SyteLine
Also searched as
- syteline lot tracked item setup
- syteline serial number tracking setup
- how to assign lot numbers on receipt syteline
- syteline lot serial mask auto generate
Short answer
Lot and serial tracking is turned on per item on the Items form, with a tracking type of None, Lot, or Serial. Once enabled, every receipt, job move, and shipment transaction for that item prompts for a lot or serial number assignment, and SyteLine keeps a full genealogy you can trace forward to customer shipments or backward to the receiving vendor.
Applies to: Infor SyteLine 8.03/8.04/9.x and CloudSuite Industrial (CSI) 10.x, standard Inventory module.
Enable and configure tracking on an item
- 1Open the Items form for the part number and set the lot/serial tracking option to Lot or Serial instead of None.
- 2Decide whether lot/serial numbers will be system-generated or manually entered, and if generated, define the numbering mask/prefix so numbers are traceable to a batch or date.
- 3For lot-tracked items, decide whether the lot is assigned at the warehouse level or split further, and whether you need lot expiration or shelf-life tracking.
- 4Save the item. New transactions from this point forward for this item require a lot/serial assignment; existing on-hand quantity does not retroactively get one unless you run an inventory adjustment to assign it.
- 5On the next PO receipt, job receipt, or miscellaneous receipt for the item, use the lot/serial entry prompt to assign or split quantity across multiple lot/serial numbers.
- 6On issues, job moves, and shipments, select the specific lot or serial being consumed or shipped, using FIFO, a specific lot, or a customer-requested lot if required.
- 7Use the lot/serial genealogy or trace inquiry to confirm you can walk from a shipped serial number back to the receiving PO and vendor lot, and forward from a receipt to every order it shipped on.
Lot versus serial: pick the right one
Lot tracking groups a quantity of the same item that shares a common attribute, usually a manufacturing batch, a chemical lot, or a raw material heat number. You track quantity per lot, not one record per unit, which is why lot tracking is the right choice for raw materials, chemicals, and any item where traceability by batch is what regulators or customers actually ask for.
Serial tracking assigns a unique identifier to every single unit, quantity of one per serial number. It is the right choice for finished goods with warranty obligations, regulated medical or aerospace components, or any item where a customer or auditor might ask "tell me exactly which unit this is and where it has been." Mixing the two up, for example serializing a bulk chemical, creates a mountain of serial records for no traceability benefit and slows every transaction down.
Numbering masks and auto-generation
If you let SyteLine auto-generate lot or serial numbers, define a mask that encodes something useful, commonly a date code or a site prefix, so operators and auditors can eyeball a number and know roughly when or where it was created without a lookup. A generic sequential number with no structure is technically compliant but makes visual spot-checks on the shop floor much harder.
If your industry or a specific customer requires you to carry their supplied lot or serial number instead of generating your own, use manual entry rather than auto-generation for that item, and train receiving staff to key in the vendor's actual lot number rather than substituting a SyteLine-generated one, which breaks traceability back to the vendor's records the moment there is a recall.
Where the prompt shows up and where it does not
Every inventory-affecting transaction for a lot/serial tracked item triggers the assignment prompt: PO receipts, job receipts from production, miscellaneous receipts, job material issues, job moves between operations if the item is a serialized sub-assembly, and customer shipments. Cycle counts and physical inventory also require you to count and reconcile by lot or serial, not just by item, which is a heavier process than counting a non-tracked item.
What it will not do automatically is retroactively tag existing on-hand quantity the moment you flip the tracking flag on. If you turn on lot tracking for an item that already has stock on the shelf, that existing quantity sits untracked until you process an inventory adjustment or cycle count transaction that assigns it a lot or serial number, so plan the cutover for a low-stock moment or right after a physical count.
Items > [item] > Lot/Serial tracking option: None | Lot | Serial
Items > [item] > numbering mask / auto-generate flag
PO Receipts / Job Receipts > lot-serial assignment popup
Inventory > Lot/Serial Trace or Genealogy inquiry
Common pitfalls
- !Turning on tracking for an item that already has on-hand stock, without a plan to assign lots/serials to the existing quantity.
- !Serializing a bulk or chemical item that should have been lot-tracked, creating unnecessary transaction volume.
- !Auto-generating lot numbers for an item where the customer or regulator requires you to preserve the vendor's original lot number.
- !Not training shipping staff on FIFO or specific-lot selection, leading to older lots sitting unshipped while newer lots go out first.
- !Forgetting that cycle counts and physical inventory take longer and require lot/serial-level reconciliation once tracking is on.
How an ERP-grounded AI assistant handles this
ERPray, grounded on your SyteLine lot and serial genealogy, can answer a trace question in seconds, for example "which customer orders shipped units from lot 24601" or "what vendor lot did the material in job 88213 come from," instead of someone manually chaining together receipt, issue, and shipment records. That turns a recall or a customer audit request from an hours-long lookup into a direct answer.
Frequently asked questions
Can an item be both lot and serial tracked at the same time?
No, the tracking option on the Items form is one setting per item: None, Lot, or Serial. If you need both a batch identity and a unit-level identity, that is typically modeled as a lot-tracked sub-assembly built into a serialized finished good, not a single item with both flags.
Does lot/serial tracking slow down transaction entry?
Yes, modestly. Every receipt, issue, move, and shipment for a tracked item requires an extra assignment or selection step compared to a non-tracked item, which is the tradeoff for having full traceability.
How do I fix a lot number that was entered wrong on a receipt?
Depending on whether downstream transactions have already consumed that lot, you may be able to correct it directly on the receipt record, or you may need an inventory adjustment that reverses the wrong lot and assigns the correct one, so check for downstream usage before correcting.
Can I set lot expiration dates in SyteLine?
SyteLine supports shelf-life and expiration tracking on lot-tracked items, which can flag or block transactions against an expired lot depending on your configuration; confirm this is enabled if your industry requires it, since it is not automatic just from turning on lot tracking.
Related
How to Run a Cycle Count in SyteLine
Cycle counting in SyteLine runs through Inventory > Cycle Count: generate a count list by ABC class or location, print or enter tags, key the counted quantities into Cycle Count Entry, then review the variance report before posting the count to update on-hand quantity.
How-toHow to Receive a Purchase Order and Return Goods to a Vendor in SyteLine
Receiving happens in PO Receipts against open PO lines, updating on-hand quantity and open PO balance. Returning goods is a separate return-to-vendor transaction that reverses the receipt, references the original PO and receipt, and should tie to an AP debit memo so the vendor invoice and payment reflect the returned quantity.
How-toHow to Handle Landed Cost and Voucher a PO Receipt in SyteLine
Landed cost charges such as freight, duty, and brokerage are added against the PO or the receipt, allocated across the received line items by value or quantity, and rolled into the item's received cost before it is vouchered. Vouchering itself is the 3-way match between PO price, receipt quantity, and vendor invoice, and mismatches beyond your tolerance percentage get held for review instead of posting automatically.
Error fixTroubleshooting SyteLine MRP and APS regeneration that fails or hangs
A SyteLine MRP or APS run that fails to complete, hangs indefinitely, or errors partway through is most often caused by data integrity problems (a BOM loop, an item with an invalid lead time or missing routing), a scheduling engine (APS) process that is stuck or resource-starved, or a concurrent MRP run conflict. Check the MRP/APS log first for the specific item or job it stopped on before assuming it is a system capacity issue.
Error fixFixing SyteLine's 'Object reference not set to an instance of an object' error
This is a generic .NET NullReferenceException surfacing through the SyteLine IDO Runtime, not a SyteLine-specific error code. It almost always means a form, script or IDO method referenced a field, row or object that came back null, usually after a customization, a missing related record, or a view/IDO method call before the form finished loading. Turn on detailed client logging and check the most recent customization or form event first.
Error fixDiagnosing and fixing SyteLine session timeout errors
SyteLine session timeouts come from one of three independent layers: the IDO Data Service session timeout on the app server, the IIS/application pool idle timeout for the web (Mongoose Web) client, or a load balancer/proxy idle timeout in front of a CloudSuite hosted environment. Fixing the wrong layer is the most common mistake - you need to identify which layer is actually expiring the session before changing anything.
AI for ERPAI for Infor SyteLine and CloudSuite Industrial
Add grounded AI to Infor SyteLine or CloudSuite Industrial: natural-language answers, agents over IDOs and ION, on-prem or CloudSuite deployment.
Stuck on Infor SyteLine (CloudSuite Industrial)?
Talk to engineers who work inside Infor SyteLine (CloudSuite Industrial) every week, and who build private AI that answers these questions from your own ERP data.