- Order ID or order number
- Original transaction/payment reference
- Refund reference only when it clearly links back to the order export
Order + refund workflow
Merge Orders with Refunds
Connect order exports with refund records to identify refunded orders, add refund amounts or reasons, and keep a clean order-level dataset for analysis.
🔒 Local processing for normal jobsOne-to-many warnings
Recommended setup
Master + Enrich keeps all orders and adds refund information where a refund record matches.
Use Keep Everything if you also need to see refund rows that do not map to any order in the export.
How to join the files
- Add the order and refund exports and select the real data sheets.
- Choose Master + Enrich or Keep Everything, depending on whether unmatched refund rows should remain visible.
- Map the order-level reference. Avoid customer email for transaction-level refund matching.
- Review duplicate/multiplication warnings, choose the refund fields you need and download.
An order can have several partial refunds. Multiple refund rows for the same order can be correct and may create multiple output rows.
Common refund issues
One order can legitimately have several refund records.
A refund ID is not necessarily the same as the original order ID.
A customer email can connect many orders and should not be the first choice for refund-level matching.
🔒
Normal jobs stay local.
Order and refund spreadsheet contents are processed in the browser for normal jobs.
Build the order/refund dataset
See exactly which refunds connect before exporting the final workbook.
Open MergeStudio →Confirm that the selected reference identifies the same order in both files.