Does this connect to Shopify?

No. You provide the two exports.

Does a match prove GA4 was corrected?

No; validate the analytics refund event separately.

Free tool by Clarvivo · no login

Upload matching order and refund exports to find identifier gaps before gross revenue is mistaken for net revenue.

Upload matching order and refund exports. We compare order IDs and refund totals; this does not by itself prove an analytics refund event fired.

This tool answers: Do the refunds in this export still match known orders, or is revenue likely overstated?

Enable JavaScript to run the check — the diagnosis itself is free and needs no account.

A store can issue refunds while analytics and acquisition reporting continue to show the original purchase value.

Matching refunds to orders is a necessary first step, but it is not proof that every analytics platform received a refund event.

These answer the questions this one tends to raise.

So you can trust the result — and your developer can verify it.

Normalise order references
Common transaction and order ID columns are compared.
Total refund amounts
The result exposes unmatched IDs and the refund amount affected.

Different provider identifiers: Order and refund exports use incompatible values.
Refund event is missing: Analytics receives purchase but not the reversal.

Does this connect to Shopify?: No. You provide the two exports.
Does a match prove GA4 was corrected?: No; validate the analytics refund event separately.

Clarvivo keeps refunds and acquisition claims in one revenue picture.