A quality issue surfaces on one specific production lot, and the question everyone needs answered immediately is simple: exactly which customers received product from that lot, and where is any remaining stock right now. If the honest answer takes hours of manual digging through paper records or half-complete system data instead of a single traceability report, the lot tracking setup wasn't actually built for this moment — it was built to look complete during a routine audit, which is a very different bar.
Item tracking in Business Central is genuinely capable of full lot and serial traceability from receipt through to the customer who ultimately received the item. The gap between that capability and what most companies actually have running is almost always a setup and discipline issue, not a platform limitation.
Lot Tracking vs. Serial Tracking: Different Tools for Different Needs
Lot tracking follows a batch or production run as a single unit — appropriate for items where individual units within a batch share identical characteristics and don't need separate identity, like a production run of a chemical product or a batch of food items sharing an expiration date. Serial tracking follows each individual unit distinctly — appropriate for higher-value items like equipment or electronics, where a specific unit's history matters on its own, separate from others manufactured at the same time.
Choosing the wrong one for a given item category creates real problems: lot tracking on an item that actually needs individual serial-level traceability means losing the ability to distinguish one specific problem unit from others in the same batch. Serial tracking on high-volume, low-value items that don't need individual identity creates unnecessary transactional overhead for no real traceability benefit.
Where Tracking Actually Breaks: The Chain, Not the Setup Screen
Configuring an item for lot or serial tracking on the item card is the easy part. The part that actually determines whether traceability works when it matters is whether the tracking number gets carried correctly through every single transaction the item passes through — receipt, put-away, transfer between locations, pick, shipment. A single point in that chain where tracking information doesn't get properly captured or carried forward — a manual adjustment posted without the lot number attached, a transfer where tracking wasn't required — creates a genuine gap in the traceability chain, even though the item was technically "tracked" at the point of receipt.
This is why lot tracking that looks complete during a quiet audit can fail during an actual recall: the audit typically checks whether tracking is configured, not whether every single transaction in the item's history actually carried the tracking number through cleanly.
Expiration Dates Need Their Own Deliberate Setup
For lot-tracked items with genuine shelf life — food, pharmaceuticals, and similar categories — expiration date tracking needs to be configured specifically, not assumed to come automatically with lot tracking alone. Getting this right means the system can actively enforce FEFO (first-expired, first-out) picking logic rather than simply recording an expiration date passively as a data field nobody's actively using to drive picking decisions.
The E-Commerce Connector Gap Worth Knowing About
Worth flagging directly for any company selling lot- or serial-tracked items online: Microsoft's native Shopify connector does not handle lot tracking or serial numbers as part of its standard integration. A business selling tracked items through an e-commerce channel needs a deliberate plan for how tracking information gets captured on those orders — this typically means additional configuration or a warehouse management integration layered on top of the standard connector, not something that works automatically out of the box.
What a Real Traceability Test Looks Like
The only genuine way to know whether lot or serial tracking actually works end to end is to run a real test: pick a specific lot or serial number already in the system, and trace it forward through every transaction it's touched — receipt, any transfers, any picks, the final shipment — confirming the tracking number carried through cleanly at every step, with no gaps. If that trace can be completed cleanly and quickly, the traceability chain is genuinely reliable. If it requires manual digging or hits a dead end partway through, that's exactly the gap that would surface at the worst possible moment — during an actual quality issue or recall, not during a planned test.
Where to Start
For any company relying on lot or serial tracking for quality, compliance, or regulatory reasons, it's worth running that end-to-end trace test on a handful of actual items now, deliberately, rather than waiting to discover a gap during a real recall. It's also worth confirming whether expiration date tracking is actively driving FEFO picking or just sitting as an unused data field, and whether any e-commerce-sold tracked items have a real plan for capturing tracking information on those specific orders.