Do I need a separate record for lot traceability?

No. The trail is read from the documents in Logo; when receipt, transfer and dispatch are done as usual, the trail builds itself.

Is the impact of a lot used in production visible?

If the lot was consumed on a production order, the lots produced on that order and their customers are traced too. For consumption not tied to a production order, Logo keeps no such link, so it cannot be shown.

Can the recall list be exported?

Yes. The list downloads as CSV or prints.

Lot recall: being ready for "who received this batch?"

The hard part of a recall is not the decision but producing the list. When where a lot came from, where it is and who received it are recorded inside the operation, the list is queried, not searched for.

The supplier calls: there is a problem with a production batch. The first question is simple, yet in most warehouses the answer takes hours: where is this batch here, and who received it? Waybills, dispatch notes and someone's spreadsheet are combed through one by one.

Two directions of traceability

In good practice two directions are known for a lot: backward (who we got it from, with which document) and forward (which transactions it went through, how many units went to which customer). A manufacturer has one more step: if the lot was consumed in production, the lots produced from it and their customers are affected too.

The lot trail in iyibir WMS

On the Traceability screen of the web panel, a lot or serial number is scanned or typed. One page shows:

The item and its expiry date.
Where it came from: purchase waybill, production receipt or count surplus; supplier and date.
Where it is now: remaining quantity by warehouse and shelf.
What happened: transfer, consumption on a production order, scrap, count shortage, return.
Who received it: sales waybills, customer, quantity and date.

If the lot was consumed on a production order, the lots produced on the same order and their customers are traced too. The trail is read from the documents in Logo; no separate copy is kept.

The recall list

The recall view lists affected customers with net quantities. The list downloads as CSV or prints. Instead of "we cannot be sure, so let's call everyone", you go only to those actually affected.

The trail starts at receipt

The query is only as good as the lot recorded at the start. At goods receipt the lot is scanned or a new lot is opened; the lot label is printed from the device at the end of the receipt. On a GS1-128 labelled case, item, lot, expiry date and serial come in with one scan. Picking scans the lot too, and the suggested lot is shown with its expiry date.

Step by step: Producing a recall list for a lot

Open the Traceability screen in the web panel.
Scan or type the lot or serial number and open the result.
Check the came-from, where-now, what-happened and who-received sections.
Switch to the recall view to see affected customers with net quantities.
Download the list as CSV or print it.

Frequently asked questions

Do I need a separate record for lot traceability?: No. The trail is read from the documents in Logo; when receipt, transfer and dispatch are done as usual, the trail builds itself.
Is the impact of a lot used in production visible?: If the lot was consumed on a production order, the lots produced on that order and their customers are traced too. For consumption not tied to a production order, Logo keeps no such link, so it cannot be shown.
Can the recall list be exported?: Yes. The list downloads as CSV or prints.