Food Traceability WMS Integration: Validate Lots at Receipt and Dispatch

Document supplier lot, source, SKU, pallet, case, order, and location as different identities. A barcode scan helps only if decoded fields map to the intended records.

Specify multi-lot receipts. One purchased SKU can need several lot allocations; solve an interface that permits only one lot per line before relying on downstream reports.

A pick can split one lot between customers or combine several lots in one order. Record actual dispatch allocations rather than inferring them later from FIFO settings.

Preserve previous IDs through returns and replacement labels. Review the activity actually performed; an inventory adjustment should not erase links to the original receipt.

Replay an offline scanner message twice and out of order. Prove that retries neither duplicate stock nor create duplicate event records.

A scan returning success while saving only the SKU is a silent failure. Missing lot identity should produce a visible exception and a working correction path.

FoodChainAPI suggests candidate Food Traceability List categories from product descriptions. Save the reviewed result beside the product specification; a category match does not establish exemptions, complete operational records, or certify compliance.