Item tracking — lots and serial numbers in Business Central
How Business Central's item tracking handles lot and serial numbers — tracking codes, the item tracking lines window, picking specific lots, expiration dates, and the costs of getting it wrong.
Item tracking in Business Central is the mechanism that lets the system follow individual lots or individual serial numbers through every transaction — from purchase receipt to production consumption to final sale and warranty claim. Without it, an item is fungible; with it, every unit (or every batch) carries identity.
Lot vs serial.
- Serial number — uniquely identifies a single unit. Used for high-value or traceability-critical items: medical devices, vehicles, premium electronics. Quantity per serial is always 1.
- Lot number — identifies a batch of identical units produced or received together. Used in food, pharma, chemicals, anything with shelf life or recall obligations. Quantity per lot is many.
An item can require both (lot + serial), but that's unusual and operationally heavy.
Item Tracking Code. Tracking behaviour is defined on an Item Tracking Code record, then assigned to the item. The code captures:
- Lot specific tracking — whether lots are required on every transaction.
- Serial specific tracking — same for serials.
- Warranty date — if and how warranty dates are captured.
- Expiration date — if and how expiration dates are captured, and whether FEFO (First Expired First Out) applies.
- Strict expiration posting — prevents posting transactions for items past expiration.
You design a few tracking codes (e.g. FOOD, MEDICAL, SERIAL-WTY) and reuse them across items.
The Item Tracking Lines window. Whenever a tracked item appears on a document line — sales order, purchase order, transfer, production output — the user opens Item Tracking Lines (Ctrl+Shift+I in some role centres) to specify which lots or serials. The window enforces:
- The total tracked quantity equals the line quantity.
- The specified lots/serials exist in inventory (for outbound) or are valid (for inbound).
- No double-allocation across documents.
For inbound documents, the user enters new lot/serial numbers — either typed, captured by barcode scan, or auto-assigned from a number series.
Expiration dates and FEFO. For pharma and food, expiration is the dominant dimension:
- Inbound transactions capture the expiration date per lot.
- Outbound transactions automatically pick the earliest-expiring lots first (FEFO) if
Pick According to FEFOis enabled. - Reports list lots approaching expiration so they can be sold, transferred, or scrapped.
Reservation. Item tracking integrates with reservations: a sales order can reserve specific lots (e.g. for a customer that pre-paid for a specific batch). The reservation engine prevents anyone else from allocating the same lots.
Posting and traceability. When a transaction posts, an Item Ledger Entry is created with the lot/serial number. The Item Tracing function lets you trace any lot or serial backwards (origin) or forwards (destinations) through every transaction it appeared in. For a recall, item tracing is the difference between an hour's work and a week.
Warehouse integration. In a warehouse-managed location, lots and serials are captured at the bin level too — the Warehouse Entry records which bin holds which lot. Picking and put-away workflows enforce tracking capture.
Common pitfalls.
- Enabling tracking after go-live. Switching an item from non-tracked to tracked is operationally painful — existing inventory has no lot/serial. The fix is a counting journal with retroactive tracking, but it's tedious.
- Lot number duplication. Lot numbers are not unique across all items by default. Two different items can have lots called "L001". For unambiguous tracing, prefix lot numbers with vendor or production codes.
- Strict expiration posting forgotten. Without it, expired stock can still be shipped — a regulatory and reputational hit.
- Slow item tracking lines window. On high-volume warehouses with millions of lot ledger entries, the tracking lines window slows down. Indexes and archival of old entries help.
Audit and recall. Lot/serial traceability is a regulatory requirement in many industries (FDA 21 CFR Part 11, EU food law, medical device regulations). Auditors will test recall capability: pick a lot, trace it forward, confirm you can identify every customer who received it. BC's item tracing is the tool that makes that audit pass.
Operational discipline. Item tracking only works if it's captured at every step. A warehouse operator who skips lot capture on an inbound receipt breaks traceability for every subsequent transaction touching that stock. Training, scanner-driven workflows, and process design matter more than the system configuration itself.
Related guides
- Item attributes and variants in Business CentralHow Business Central handles product variations — variants for stock-keeping, attributes for searching, and where the model fits and where it doesn't.
- Item availability and order promising in Business CentralHow Business Central computes item availability — on-hand, projected, ATP, CTP — and the order-promising engine that turns availability into delivery commitments.
- Item categories in Business CentralHow to structure a Business Central catalogue with item categories — hierarchy, defaults, attributes, and the integration with templates and reporting.
- Item substitutes and cross-references in Business CentralHow Business Central handles item alternatives — substitutes when stock is short, cross-references for customer / vendor part numbers, and the operational impact.
- Item templates in Business CentralHow item templates standardise product creation in Business Central — defaults, categories, and the integration with item attributes.