Combine order exports without silently deleting lines

Two CSV exports can contain the same order number from different stores or the same order exported twice. A blind merge can either lose a real line or double-count a shipment.

Prepare your input

Keep the original channel exports and note their source names. If stores reuse order numbers, map a channel field or provide a constant source name for each file. Where available, include a stable line ID.

Work through the task

Add each file to Order File Merger and map its columns independently. The merged view retains every line with source file and row references. Review values distinguish unique lines, repeated identical lines, conflicting line IDs and ambiguous repeats without a line ID. Status aliases such as fulfilled and complete normalize to completed, while unknown values remain visible. Export a new normalized review CSV.

Example to try

Two exports may both include order 102, while one export repeats the same line after a status refresh. With channel and stable line ID, the repeated row can be flagged without dropping it. Without a line ID, two similar lines may be genuine separate purchases. Review the source row references rather than deciding by matching SKU alone.

Check the result

Check total input and output row counts, inspect every flagged repeat, and resolve ambiguous identities before handing the file to packing staff. Keep channel identity attached to the order number.

Know the current limits

The app does not delete duplicates, combine quantities or fulfill orders. Its output is a review file, not an instruction to ship every row.