One up, one down traceability: linking what came in to what went out

One up, one down is a common baseline in food and supply-chain rules, but what applies to you depends on your products, your markets and your customers, so check with your trade body, certification scheme or adviser. TraceBench does not give legal advice; it shows, from your own records, whether each lot links to its supplier and to its customer.

No. One up, one down is what your records should hold; a traceability exercise tests whether they do, by following a lot both ways against the clock. See /traceability-exercise/.

For both steps, yes: the production file gives the supplier lot in each batch, and the despatch file gives the shipment for each batch. A production file alone shows one step back.

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