9 November 2025 · Refunds

Refund spikes as product feedback, not just finance noise

Finance closes refund tickets. Product should open them. The timestamp is usually sitting next to the paywall event you already log.

Teams treat refund rate as a finance KPI: lower is better, spikes are fraud or “store policy,” and the product roadmap does not move. That posture lasts until a paywall rewrite ships and refunds jump the same afternoon. Then everyone discovers that in-app purchase analytics had the join key all along — purchase token, original transaction id, paywall exposure — and nobody had used it.

Three reasons before you close

Refund Forensics Workshop insists on a taxonomy with at least three product-shaped reasons: unexpected charge (trial end surprise), broken restore or entitlement, and value mismatch after first session. Fraud and genuine buyer’s remorse exist; they should not be the only two buckets. If your tags are only “fraud / other,” you have not started.

Align refund time with what the person just saw

A spike six hours after a permission prompt often means the person thought they bought access and then hit a wall. A spike after a restore-purchase failure means your entitlement code, not your price. A spike on a Monday after a Thailand billing holiday may be retry catch-up, not a new paywall. Chart refunds against last paywall impression, last entitlement error, and local banking calendar. The overlay is usually more honest than a weekly refund % tile.

Do not wait for App Store reviews

Star ratings lag. Refunds do not. If you wait for review text to explain a Wednesday spike, you have given the catalog three extra days of the same wound. In-app purchase analytics that pages a monetization owner when refunds exceed a quiet baseline — by SKU, not blended — pays for itself faster than another dashboard theme.

What we will not claim

Reading refunds will not automatically lower them. Sometimes the honest outcome is “this SKU is mis-sold and should be pulled.” That sentence is harder than a growth deck. It is still the job.

The workshop listing sits on the catalogue. If you already have a spike and a redacted export, write the studio before you book a seat — we may tell you the join is enough to do at your own desk.