What is forward and backward traceability?

Yes. Each code column is declared as a material lot or batch, or as a serial unit, with its own numbering name. A serial number and a lot number are never joined to each other.

No. One file is enough: a production file alone shows what went into each batch and where each lot was used in production. Add a second file, such as despatch, when you need to trace across systems.

Because matching codes are only possible links. Confirm the exact pair or declare the shared numbering under Links between the two files, then run the trace again. Until then the result names the unconfirmed link as a gap.

TraceBench is a reading of the records you load, not a recall decision or proof of what physically happened. It has no recall, hold, stock or customer-notification actions, does not allocate or reconcile quantities, and never links records because their codes, times, descriptions or row order look alike. Two current files at a time, each UTF-8 CSV with column names in the first row, up to 5 MiB, 5,000 data records and 40 columns, and 10,000 recorded facts across both. A trace follows up to 20 manufacturing steps and stops at its limits with a stated reason. XLSX files are not read, and there is no connection to your ERP or any other system.

Your files stay in this browser. Work is held in memory until you choose Save on this device, which keeps the whole project, original files included, in this browser. Files are read and fingerprinted on your device and never uploaded, and there is no account or email step. Reports and backups contain your records and file names, so check them before sharing. Google Analytics is optional and loads only after you accept; it never receives codes, rows, file names or results. Use Analytics settings to change your choice; see /privacy/.