How the CSV checks and examples work
Supplier Desk Team · Updated
Supplier Desk Team is the product's creator and maintains these tools and explanations. The pages are product documentation, not independent customer reviews. We have not established customer time savings, search ranking or willingness to pay from these examples.
Deterministic calculations, explicit matching keys
The tools apply fixed calculations to the CSV records you supply. They do not call an AI API or infer product identities. Each tool documents the columns, matching keys and conditions needed to interpret its report. A result describes the supplied files; it cannot verify the physical stock, contractual terms or completeness of those files.
Reproduce an example before using your own data
Sample records and worked cases are synthetic. The pack-size case includes both source CSVs and the unit-cost formula. The partial-receipt case includes order and receipt CSVs, the open-quantity calculation and assumptions. The delivery-date history example explains how three retained reports produce observed ETA changes and where missing observations remain unknown. Use the sample action on each tool, then compare the report with the explanation.
Choose the file format your tool supports
The ten CSV review tools accept pasted tables and CSV/TSV files, not XLSX uploads. Date Trail also accepts XLSX report snapshots. Its worksheet selection and explicit date mapping do not recalculate workbook formulas. Export confirmed values when a report depends on formulas.
Check the meaning of a warning
A missing mapping is not a guessed match. An open PO quantity is not automatically a confirmed shortage. A valid barcode check digit is not proof of ownership. Reports support human review and do not post inventory, accounting entries or supplier claims.
What leaves your browser?
CSV calculations run in your browser; source file contents are not uploaded for processing. The site separately records basic usage events and stores feedback that you voluntarily submit. Checkout is handled by Stripe. Read the data-use policy for details.
Sources and corrections
Links to vendor documentation describe the underlying workflow. Public discussions show that a problem has been discussed; they are not endorsements of Supplier Desk or proof of demand for it. If a result differs from its documented method, send the tool name, expected result and a minimal synthetic example. Do not include confidential supplier files, account credentials or customer records.