Rastro do lote

There is no screen where someone types "lot A came from lot B". The tree on this screen is built from the stock movements that production already records: the order's component issues point to the inputs, the finished goods receipt points to the lot produced. That's why the trail can never disagree with stock — it's the same book, read another way.

The search ignores upper and lower case, but it doesn't guess a lot typed with an extra space or a different suffix. If a lot doesn't show up, check how it was recorded on the production order — that's what names the lot, and the rest of the chain copies from there.

The lot on the stock movement was born just now. Earlier movements have no lot, and the screen says exactly that, in grey, instead of hiding the row. Hiding it would give the impression of a complete chain that doesn't exist; and a trail that looks complete and isn't is worth less than no trail, because whoever reads it believes it. The badge at the top counts how many consumptions are still in that situation.

The automatic component issue knows HOW MUCH went out, not FROM WHICH LOT — only whoever fed the machine knows which roll went in. Copying the knit's lot there would make the trail point the lot to itself, and nothing would raise an error. That's why the row is born blank and the pencil next to it records the declaration, on the very screen where the gap appears: sending whoever saw the gap to look for another menu is where the data dies. Leaving the field blank erases the declaration and returns the row to "not recorded".

BACKWARD: the input lots are the stock issues generated by the order that produced this lot. FORWARD: the invoices and orders that carry this lot in their items. They are two different paths because the information lives in different places — and forcing them into one would make the screen invent the missing half.

Whoever opens a lot's tree almost always does so because a piece came out wrong — so the button to open an NCR (non-conformance report) lives on this screen, not in a distant menu. The NCR isn't a new table: it's the ticket workflow engine configured with a quality cycle — open, root-cause analysis, corrective action, effectiveness check, closed. Each step requires a comment, and there's no shortcut from opening to closing: without the effectiveness check, "fixed" means "someone touched it", not "the problem stopped". A closed one doesn't reopen either — recurrence is exactly what the audit looks for, and erasing it would hide what matters most. Did it happen again? A new one is opened, pointing to the previous one.

No. The DPP is a regulated European format whose delegated act for textiles hasn't been published yet — the expectation is ~end of 2027, with application after that. What exists here is the lot's internal trail, which is the input for any future passport and, today, a commercial differentiator: showing the customer where the knit came from before anyone requires it.