Lot Traceability in Business Central Manufacturing: How to Track Every Batch for FSMA and FDA Compliance

When a regulator, auditor, or OEM customer asks which finished goods contain a specific raw-material lot, the answer has to come out of your ERP in hours, not days. For mid-market manufacturers running Dynamics 365 Business Central, lot traceability in Business Central manufacturing is built into the core item tracking engine. However, how well it works under audit pressure depends almost entirely on how it was configured.

This guide covers three things. It explains how Business Central tracks a batch from receipt through production to shipment. It identifies the configuration decisions that quietly break traceability. Finally, it maps native capabilities against the requirements food, pharma, and automotive manufacturers actually face.

What Is Lot Traceability in Business Central?

Lot traceability in Dynamics 365 Business Central is the ability to follow a lot number in both directions across every posted inventory transaction.

• Backward: from a finished lot back to the component lots and vendors it came from.
• Forward: from a component lot to every finished lot, customer shipment, and open document it touched.

It is driven by three elements working together:

1. Item Tracking Codes, which define when a lot number is mandatory.
2. Item Tracking Lines, which capture the lot on every inbound, outbound, and manufacturing posting.
3. The Item Tracing page, which reconstructs the lot genealogy on demand.

In Item Tracing, the Usage→Origin method performs backward tracing, which is what you use for root cause analysis. The Origin→Usage method performs forward tracing, which is what you use for recall scoping.

How Business Central Tracks a Batch Through Manufacturing

Each stage of the production cycle writes the lot number into the item ledger. Here is how that works in practice, building on Business Central's manufacturing capabilities.

1. Receipt: the lot enters inventory

On the purchase order line, the lot is either assigned from the item's Lot Nos. series or entered manually, usually as the supplier's lot or a combination of internal and supplier lot. If expiration dates are enabled, BC calculates or requires the expiration date at this point. The Lot No. Information card becomes the master record for that lot, holding quality notes, certificate references, and the Blocked flag.

2. Production consumption: components are linked to the order

When you post consumption against a released production order, each component's item tracking lines record exactly which lots were used. This is the link that creates genealogy. Without lot-level consumption, there is no backward trace.

3. Output: the finished lot is born

Output posting assigns a lot number to the finished or intermediate item. BC ties this output entry to the same production order as the consumption entries. That is how the Item Tracing page later connects a finished lot to its ingredient or component lots, including across multi-level BOMs.

4. Warehouse handling and FEFO

With Lot Warehouse Tracking enabled on the tracking code, lots are carried through put-aways, picks, and movements. Locations configured for FEFO picking (first-expired, first-out) direct pickers to the earliest-expiring lot, which matters for any shelf-life-sensitive product. Pairing this with mobile warehouse scanning removes manual lot entry, which is the most common source of traceability errors on the floor.

5. Shipment: the forward link to customers

Sales shipments record which lots went to which customer, completing the forward chain. That chain runs from supplier lot to production order, then finished lot, then customer shipment.

Five Configuration Decisions That Make or Break Traceability

Most traceability failures we see in Business Central are configuration problems, not software limitations.

1. Turn on Lot Specific Tracking for regulated items. Setting Lot Specific Tracking on the item tracking code forces every outbound transaction to apply against the specific lot that came in. Without it, users can record lots inconsistently and the genealogy fragments.
2. Watch your flushing methods. Forward and backward flushing are popular because they cut manual consumption posting. For lot-tracked components, though, the system still needs to know which lot was consumed. That means lot assignment on the component lines or lot-carrying warehouse picks. Decide this during design, not after go-live.
3. Know the Item Tracing blind spot. Microsoft's documentation notes that Item Tracing shows only applied transactions. If the same lot was received on multiple documents, not every receipt may appear in the trace. Your recall procedure should always pair Item Tracing with Find Entries, which surfaces every posted and open record for a lot number.
4. Use the expiration controls deliberately. The item tracking code offers three settings:

• Use Expiration Dates calculates expiry.
• Require Expiration Date Entry forces capture at receipt.
• Strict Expiration Posting prevents expired lots from leaving inventory.

Food and pharma manufacturers usually need all three.

5. Block suspect lots immediately. Selecting Blocked on the Lot No. Information card stops that lot from being used in further transactions. This is your first containment action in any quality event.

Lot Traceability Business Central Manufacturing Requirements by Industry

The table below maps common regulatory requirements to native Business Central coverage. It is written for food and agriculture manufacturers, pharma and nutraceutical producers, and automotive suppliers.

Industry / Regulation	What It Requires	Native Business Central Coverage	Typical Gap
Food: FSMA 204 (enforcement from July 20, 2028)	Traceability lot codes, Key Data Elements at each Critical Tracking Event, sortable records to FDA within 24 hours	Lot capture at receiving, production, and shipping; Item Tracing; exportable entries	Structured KDE capture (e.g., location identifiers, traceability lot code source) and a one-click FDA-format report usually need an extension or Power BI report
Food: GFSI / BRCGS / SQF audits	Mock recalls with mass balance, completed within a set time	Backward and forward tracing, quantity reconciliation from item ledger	Automated mock-recall report with mass balance
Pharma: 21 CFR Part 211	Batch production records, component traceability, expiry control	Production order consumption/output by lot, expiration rules, lot blocking	Electronic signatures and validation documentation (Part 11) are not native; typically added via extension and a validation package
Pharma: DSCSA (manufacturer exemption ended May 2025)	Product identifiers including lot and expiration, transaction data exchange	Lot and expiration on shipments; serial tracking available	Serialization and EPCIS data exchange require a specialist integration
Automotive: IATF 16949	Traceability of components to finished parts and customers, scoped recall capability	Multi-level lot genealogy, package tracking for containers	Supplier-portal lot capture and OEM-specific labeling formats

The pattern is consistent. Business Central natively handles the lot genealogy itself. What usually needs to be added is the regulation-specific data capture and reporting layer on top of it.

How to Run a Mock Recall in Business Central: 6 Steps

A mock recall is the real test of whether your configuration works. Here is the procedure we use with manufacturing clients.

1. Contain. Open the Lot No. Information card for the suspect lot and set it to Blocked.
2. Trace backward. In Item Tracing, enter the finished lot, set Show Components to Item-tracked Only, and run Usage→Origin. This identifies the component lots, the production orders, and the supplier receipts involved.
3. Trace forward. From the suspect component lot, run Origin→Usage, or use Trace Opposite – from Line. This finds every finished lot and customer shipment containing it.
4. Find open exposure. Run Find Entries on each affected lot to catch open sales orders, transfer orders, and production orders before more product moves.
5. Reconcile quantities. Compare quantity received against quantity consumed, quantity shipped, and quantity on hand. Any gap is unaccounted product and an audit finding.
6. Time and document it. Record how long steps 1 through 5 took. Under FSMA 204's 24-hour records expectation, a multi-day trace is a red flag.

Many manufacturers move steps 2 through 5 into Power BI traceability dashboards connected to Business Central's item ledger. That turns a two-hour manual exercise into a filtered report that quality teams can run themselves.

Where Standard Business Central Stops

Closing these gaps doesn't require replacing Business Central. Most manufacturers extend it with targeted custom extension development for regulation-specific data capture, Power BI traceability dashboards for recall reporting, and integrations with labeling, scanning, and quality systems. For agriculture and fresh-produce businesses, Folio3's AgriERP extends Business Central with farm-to-shipment visibility. The right mix depends on your regulatory scope, which is why scoping should come before configuration. 

Ready to Make Every Batch Audit-Ready?

Traceability gaps rarely surface until a recall or audit forces the question. Folio3 brings 20+ years of Microsoft Dynamics delivery, 300+ projects, and 200+ Microsoft-certified experts to Business Central implementations for food, agriculture, and manufacturing businesses. Start with a free 1-hour consultation that covers an honest assessment of your current traceability setup, the gaps against your compliance requirements, and a practical roadmap to close them.

FAQ

Does Business Central support lot traceability out of the box?

Yes. Business Central natively supports lot, serial, and package tracking, expiration dates, lot blocking, and bidirectional tracing through the Item Tracing page. Regulation-specific reporting typically requires configuration or an extension.

What is the difference between Usage→Origin and Origin→Usage in Business Central?

Usage→Origin traces backward from where an item was used to where it came from, which is used for root cause analysis. Origin→Usage traces forward from where a lot entered inventory to everywhere it was used or shipped, which is used for recall scoping.

Is Business Central compliant with FSMA 204?

Business Central captures the lot-level data FSMA 204 depends on. Full compliance also requires capturing the required Key Data Elements at each Critical Tracking Event and producing the FDA's sortable spreadsheet within 24 hours. Most food manufacturers add this through an extension or reporting layer. FDA will not enforce the rule before July 20, 2028.

Why doesn't Item Tracing show all transactions for my lot?

Item Tracing displays only applied item ledger entries. If a lot was received on multiple documents, use Find Entries alongside Item Tracing to see every posted and open record.