OPERATIONS / DAILY ORDER REVIEW
Compare order exports
without matching the wrong line.
A purchase order can contain several items. Matching on the PO number alone can hide a changed quantity or pair the wrong records. This example uses PO + line number and checks the fields that matter.
Choose a stable key
Use values that identify the same record in both exports: usually PO and line. A part number alone is insufficient if that part occurs on several orders. Do not use quantity, status or due date as a key when those are the values you want to track.
Choose the comparison fields
Compare quantity, due date, status and optionally part. A changed date is a useful exception. A renamed CSV header is a mapping problem; it does not mean the order itself changed.
Try it with small, inspectable files
Download earlier.csv and latest.csv. Each has four records. The newer export uses Order and Item instead of PO and Line.
- Open the free tool. Select earlier.csv as Earlier export and latest.csv as Latest export.
- Set the first key mapping to PO ↔ Order. Click + Add key column, then set Line ↔ Item.
- Include Part, Quantity, Due date and Status. Match each to the same-named latest column. Leave the other fields unchecked. Use text comparisons with trim and ignore case off for this example.
- Click Compare order exports. Inspect the results below, then download the Change report CSV.
The tool's built-in “Load example orders” button uses a separate, larger example with a duplicate key. Use the downloadable files for the exact result on this page.
The expected review
| PO / line | Result | What to review |
|---|---|---|
| PO-1042 / 1 | Changed | Quantity 120 → 100; due date 5 → 7 October 2026; status Accepted → Revised. |
| PO-1042 / 2 | Unchanged | 500 BOLT-M8 units, same date and status. |
| PO-1043 / 1 | Changed | Status Pending → Accepted. |
| PO-1044 / 1 | Removed | Present only in the earlier export. |
| PO-1047 / 1 | Added | Present only in the latest export. |
Download the expected report. There are zero duplicate or blank-key issues in this dataset.
“Removed” means absent from this export. It does not prove cancellation. Check whether the export filter, date range or order status selection changed.
When the result needs investigation
Several records share the same key
Order Delta Desk sets duplicate-key groups aside. It does not guess which row matches. Check whether PO + line is genuinely unique, whether the source includes split schedules, or whether the export accidentally repeats rows. Add a schedule identifier to the key only when it is stable in both files.
Every row looks changed
Check formatting first. Exact text comparison treats 10 and 10.0 as different. Likewise, 2026-10-05 and 05/10/2026 differ. Normalize dates in your export; the tool does not guess date formats. Full-edition numeric comparison can handle numeric quantity differences with an explicit tolerance.
Identifiers lose leading zeroes
Keep identifiers as text in the source. The tool preserves the CSV text 001, but cannot restore zeroes already removed by spreadsheet software.
Free check or repeatable daily workflow?
The free edition compares up to 250 rows per file with composite keys, text rules and CSV/JSON reports. Use it to see whether the review fits your work.
The €19 full offline edition adds up to 100,000 rows per file, saved mapping recipes, numeric tolerances and a Node.js command-line runner. It includes editable source, documentation and examples. Both editions require UTF-8 CSV/TSV; neither connects to your order system.