Item tracking in retail: lot and serial numbers without slowing the till
Item tracking answers one question: which exact units do we have, and where did each one go? Business Central does it well — lot numbers for batches, serial numbers for individual units, package numbers alongside them. The retail mistake is not the setup. It is turning tracking on for everything, then watching receiving and the till slow down to pay for traceability nobody ever uses. Track narrowly, capture the numbers once at receiving, and the till barely notices.
Start with the decision, not the setup
Every tracked item adds work somewhere: a number to assign when stock arrives, a number to select when it leaves, and a mismatch to resolve when the two do not agree. That work is worth paying only when the number itself has value later. Three tests cover most of a retail assortment:
- Could this item be recalled by batch? If a supplier or regulator would ever ask which customers received units from one production batch, the item needs lot tracking at minimum. Without it, a recall becomes a guess.
- Does the warranty belong to the unit? Serialized goods carry per-unit warranty and service history. If a return or repair needs the identity of this unit — not just the model — it needs serial tracking.
- Does the number expire? Stock with an expiration date that staff must respect needs lot tracking so the date travels with the batch instead of living on a shelf label someone has to read.
An item that fails all three tests should not be tracked, however easy the setup looks. Untracked stock moves faster, counts faster, and produces fewer blocked transactions. Clean, minimal master data beats comprehensive master data: every unnecessary tracking requirement is a small tax on every future transaction, forever.
Lot, serial, or no tracking: the retail test
| Question | Lot tracking | Serial tracking | No tracking |
|---|---|---|---|
| Unit of identity | A batch of units that arrived or were made together | One individual unit | The item itself, in quantity |
| Typical trigger | Recall by batch, expiration dates, batch cost | Warranty, service, high-value unit accountability | Nothing downstream needs the number |
| Handling cost | One number per batch inbound; select the lot outbound | One number per unit, inbound and outbound | None |
| Counting cost | Count per lot | Count per unit | Count quantity only |
Two details from the documentation are worth knowing before choosing. First, lot tracking does not require serial tracking: an item tracking code can switch lot tracking on and leave serial tracking off entirely. Second, with lot tracking the item's costing method applies its cost to the whole lot rather than unit by unit, which is exactly right for batch goods and one more reason not to fake lot discipline on items that are really unit business.
Set up tracking codes the narrow way
- Decide the assortment first. List the items that pass one of the three tests above. Everything else stays untracked, deliberately.
- Create one tracking code per behaviour, not per item. Search for Item Tracking Codes and create the few codes the store actually needs — for example one lot-only code and one serial code. Reuse codes across items.
- Set specific tracking only where the number must follow the unit. On the tracking code, SN Specific Tracking and Lot Specific Tracking mean the number assigned when an item enters inventory must be the number specified when it leaves. That is the setting that delivers traceability — and the setting that forces a selection on every outbound transaction, so do not enable it casually.
- Turn on warehouse tracking if the warehouse handles the numbers. Assigning tracking numbers in warehouse activities requires the SN Warehouse Tracking and Lot Warehouse Tracking toggles on the item tracking code.
- Assign the code on the item card. On the Item Tracking FastTab, set the Item Tracking Code plus the Serial Nos. and Lot Nos. number series the store will draw from.
- Pilot on one category. Run receiving, a sale, a return, and a count on a small group before rolling the code out. Tracking problems are cheap in a pilot and expensive chain-wide.
Capture numbers at receiving, not at the till
The single biggest speed decision: assign tracking numbers when stock arrives, not when it sells. Business Central supports both patterns — outbound handling can select from numbers already assigned inbound, or assign new numbers at the outbound stage — but the receiving dock has time and the till does not.
On an inbound document such as a purchase order, open Item Tracking Lines from the line (Line action on the Lines FastTab). Numbers can be assigned four ways: automatically with Assign Serial No. or Assign Lot No. from a predefined number series; automatically with Create Customized SN, which builds numbers from a starting value and an increment and can group the new serial numbers under a fresh lot; manually, by typing the vendor's own numbers; or manually, unit by unit. For most retail receiving, the vendor's printed lot or serial is the number worth recording — it is the number a recall notice will quote.
Once assigned inbound, the numbers follow the stock: posted tracking entries appear on the item ledger entries, and the tracking numbers transfer automatically to outbound warehouse activities. At sale or shipment time the work shrinks to selecting the existing number — through the Serial No. or Lot No. fields, or with Select Entries, which lists all available numbers with availability information. The header quantities on the Item Tracking Lines page must balance to the document line, shown by zero in the Undefined fields; if they do not, the document is not ready to post.
In LS Central estates the same discipline pays off twice, because tracked items ripple into other messages: franchise functions, for example, support retail items set up with serial or lot numbers and create a line per serial or lot number in their messages, and the numbers can be inspected on inbound and outbound messages with the Show Serial Nos./Lot Nos. action. Numbers captured once, correctly, at receiving are the numbers every downstream process reuses.
Trace and verify: recalls, returns, and counts
Tracking earns its cost on three bad days: a recall, a disputed warranty return, and a count that does not agree. Prepare for all three before they happen.
- Recall. The Item Tracing page traces a lot or serial backward and forward through posted transactions — from where a unit came from to where it went. Only applied transactions are shown, so a trace is only as complete as the postings behind it.
- Find every instance. Find Entries, with Search for item references, locates all instances of a serial or lot number in the database — the fastest way to answer "do we still have any of that batch, anywhere?"
- Watch the availability warnings. Item tracking pages warn when some or all of a selected quantity is already used on other documents, or when a number is not available. Treat the warning as a data problem to fix, not a prompt to override.
- Count by number. A tracked item cannot be counted honestly in bulk. The count has to state quantities per lot or per serial, or the adjustment will land on the wrong batch and corrupt the trace the tracking exists to provide.
What success looks like
Pick one tracked item and run the full loop. Receive it and confirm the tracking entries sit on the posted item ledger entries with the vendor's numbers. Sell or ship one unit by selecting the existing number rather than typing a new one. Then open Item Tracing and trace that number from receipt to sale without gaps. If the loop closes in a couple of minutes and the till step was a selection instead of a typing exercise, the setup is right — extend it to the next category on the decision list, and leave everything else untracked.
FAQ
Can an item be lot-tracked without serial numbers? Yes. Configure the item tracking code with lot tracking on and serial tracking off; the lot number then applies to the batch as a whole.
Do tracking numbers have to be typed at the point of sale? No — and they should not be. Assign them on the inbound document; outbound handling then selects from the existing numbers.
What if staff select the wrong lot on a sale? The posting carries the wrong trace until it is corrected, which is why the availability warnings matter: a lot that shows as already used or unavailable is the system catching exactly that mistake.
IndexBack to all guides →