Lot Tracking is where ERP discipline either begins or breaks.
Lot / Batch Tracking Through the Supply Chain looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: 100% lot traceability from vendor to customer; recall response time <1 minute for lot identification; regulatory compliance for food, pharma, and electronics.
The control flow a finance team actually needs.
Step 1
Lot Number Mandatory For Lot-Tracked...
Step 2
Lot Number Inherited Through...
Step 3
FEFO Or FIFO Lot Selection Configurable...
Step 4
Lot Qty Cannot Exceed Receipt Qty
Step 5
Partial Lot Consumption Supported
The ERP surface involved.
Module
Lot Tracking
Actors
Warehouse Receiver, Quality Inspector, Warehouse Picker, Platform API
Tier
Tier 1
Finance area
Inventory & Warehouse Management
Region lens
US and UK finance teams
Publication date
May 4, 2026
Lot number mandatory for lot-tracked items at receipt; lot number inherited through manufacturing/kitting operations; FEFO (first-expiry-first-out) or FIFO lot selection configurable per item; lot qty cannot exceed receipt qty; partial lot consumption supported; lot split and merge operations with full audit; lot hold/quarantine flag blocks picking without supervisor override; lot genealogy report (forward: lot → customers; backward: lot → vendors); lot number printed on pick lists, packing slips, and delivery notes; lot recall workflow identifies all affected shipments within 60 s.
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | Lot number mandatory for lot-tracked items at receipt | Given a lot-tracked item and a goods receipt with vendor lot number |
| Control 2 | lot number inherited through manufacturing/kitting operations | when receiver assigns the lot and completes the GRN |
| Control 3 | FEFO (first-expiry-first-out) or FIFO lot selection configurable per item | then a lot record links item, receipt qty, and cost layer |
| Control 4 | lot qty cannot exceed receipt qty | during picking, system directs to correct lot per FEFO/FIFO |
| Control 5 | partial lot consumption supported | lot number appears on delivery note |
| Control 6 | lot split and merge operations with full audit | 100% lot traceability from vendor to customer; recall response time <1 minute for lot identification; regulatory compliance for food, pharma, and electronics. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | On goods receipt, the receiver assigns or scans the vendor lot number and records it against the GRN line. The system creates a lot record linked to the item, receipt quantity, and cost layer. During picking, the system directs the picker to a specific lot (FEFO or FIFO selection based on item configuration). On shipment, the lot number is captured in the delivery note and sales order for end-to-end traceability. A lot genealogy report can trace from raw material lot to finished goods to customer shipment. |
| Control rules | Lot number mandatory for lot-tracked items at receipt; lot number inherited through manufacturing/kitting operations; FEFO (first-expiry-first-out) or FIFO lot selection configurable per item; lot qty cannot exceed receipt qty; partial lot consumption supported; lot split and merge operations with full audit; lot hold/quarantine flag blocks picking without supervisor override; lot genealogy report (forward: lot → customers; backward: lot → vendors); lot number printed on pick lists, packing slips, and delivery notes; lot recall workflow identifies all affected shipments within 60 s. |
| Acceptance proof | Given a lot-tracked item and a goods receipt with vendor lot number; when receiver assigns the lot and completes the GRN; then a lot record links item, receipt qty, and cost layer; during picking, system directs to correct lot per FEFO/FIFO; lot number appears on delivery note; lot genealogy traces vendor to customer within 60 s; (negative) when picking attempts to exceed lot qty then 422 LOT_QUANTITY_EXCEEDED. |
| Data record | |
| System event | |
| Lifecycle state | |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`inventory_lot` { id: string, external_id: string, item_id: string, entity_id: string, lot_number: string, vendor_lot_ref: string, received_qty: int, remaining_qty: int, receipt_date: date, expiry_date: date?, status: enum(AVAILABLE,ON_HOLD,QUARANTINE,EXHAUSTED) }; `lot_transaction` { lot_id, transaction_type, qty, transaction_ref_id, posted_at: timestamp }; (reference, product may differ).API and events
`POST /v1/inventory-lots` { item_id, lot_number, received_qty, expiry_date?, grn_id, external_id } -> 201 { id }; `GET /v1/inventory-lots/{id}/genealogy` -> 200 { upstream:[vendor, grn], downstream:[so, customer] }; `POST /v1/inventory-lots/{id}/hold` { reason } -> 200 { status: ON_HOLD }; `GET /v1/inventory-lots` { filters: item_id, status }; emits `inventory.lot_created` event; idempotent via `external_id`.State transitions
`AVAILABLE -> ON_HOLD -> AVAILABLE`; `AVAILABLE -> QUARANTINE`; terminal `EXHAUSTED`; guard: ON_HOLD blocks picking without supervisor override; recall workflow identifies all shipments for a lot within 60 s.Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.