How do I trace a batch through spreadsheet records?

No. Save each sheet as CSV UTF-8 first. TraceBench reads comma, semicolon or tab separated text, up to 5 MiB per file, and never changes the original.

Identical repeated rows under the same record ID count once, and every row reference is kept. If rows with the same ID disagree, all of them are set aside as a conflict instead of TraceBench picking one, and the trace names the conflict.

You can still trace with it. Each link then points to the row's record number in the file, marked row numbers only, so you know it refers to a position in that file rather than a stable ID.

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/.