# Refund abuse review records across systems | SourceX

Canonical: https://refer.sourcex.si/guides/refund-abuse-review-records-across-systems
Last updated: 2026-10-19

Reconstructing a refund abuse review takes five joins: order to return, return to the rule hold, hold to the support ticket, ticket to the reviewer's decision, and decision to the refund. A commerce platform export gives the first and last; the hold, the conversation and the decision live in the returns app and the helpdesk. Each join depends on an identifier, such as an order number in a ticket field or a refund ID in a case note. Partners map which keys exist, never the records themselves.

This system map is part of the [refund abuse review guide](/guides/workflow-refund-abuse-review), which covers what to inventory before a returns platform migration. This page shows where each record sits and which identifier carries one case from tool to tool.

## Three systems, five hops

Most retailers spread a refund review across three tools.

- **Commerce platform.** Orders, line items, refunds and the order history page. Shopify's Timeline keeps order events plus internal remarks that customers do not see, and reviewers often explain themselves there.
- **Returns app.** Return requests with reasons, rule definitions, holds or risk scores, and case notes. Usually a third-party tool connected to the store.
- **Helpdesk.** The customer's messages, agent replies, internal notes and escalations.

A case starts and ends in the store but spends its middle elsewhere. Every hop between tools is a place the trail can break.

## The join table: system, record, linking key, owner

The evidence asset for this page.

| Hop | System | Record | Linking key | Usual owner |
|---|---|---|---|---|
| Order to return | Commerce platform to returns app | Order and line items; return request with reason | Order number and line item ID | Ecommerce manager |
| Return to hold | Returns app | Rule log entry with threshold and timestamp | Return ID and customer ID | Customer operations director |
| Hold to ticket | Returns app to helpdesk | Ticket raised by the customer or agent | Order number in a ticket field, or requester email | Support team lead |
| Ticket to decision | Helpdesk to returns app | Escalation note; reviewer's decision and approver | Ticket ID quoted in the case, or case ID in the ticket | Returns review lead |
| Decision to refund | Returns app to commerce platform | Refund transaction and staff comment | Refund ID, or case ID in the order timeline | Finance |

Two keys do most of the work: the order number recorded as a field in the ticket, and the case or refund ID written back to the order. Ask whether each is a structured field or a phrase an agent typed.

## One case followed across the tools (Illustrative)

A fictional 240-person beauty retailer written for this page, not a real company or customer. Its returns app scores accounts and holds refunds when three or more accounts share a shipping address.

| Step | Tool | Key used | What the record shows |
|---|---|---|---|
| 1 | Commerce platform | Order number | A $68 order of skincare, returned unopened |
| 2 | Returns app | Return ID | Reason "Changed mind"; within the 30-day window |
| 3 | Returns app | Customer ID, hold ID | Refund held: four accounts at one address |
| 4 | Helpdesk | Ticket ID with order number field | Customer explains the accounts belong to family members in one household |
| 5 | Returns app | Ticket ID in the case note | Reviewer checks names and order history; hold cleared, approver recorded |
| 6 | Commerce platform | Refund ID; case ID in a staff comment | $68 refunded two days after the hold |

Followed through all six steps, the trail shows a shared-address rule catching a family, a person who checked, and money released with a stated reason. Missing step 4 or 5, it reads as a slow refund nobody can explain. A step-by-step version of a harder case, a customer flagged after a size chart error, is in the [worked exception example](/guides/refund-abuse-review-exception-examples).

## What exports keep, and what they drop

Before anyone calls the history complete, check what each tool's export actually carries.

- **Steps 1 and 6, the store.** Shopify's order export includes columns such as financial status and refunded amount. The money side of every case survives; what a reviewer typed beside the order is a separate question.
- **Step 6 notes.** Internal remarks on the order page cannot be brought back once deleted, so a tidy-up before a tool change can remove the explanation attached to a refund.
- **Step 4, the conversation.** Zendesk documents that its spreadsheet-style export leaves out ticket comments and descriptions, while its structured export includes them, and that account exports depend on plan and permissions. The format chosen decides whether step 4 keeps its words or only its ticket numbers.
- **Steps 2, 3 and 5, the returns app.** Mark its export options unknown until the company's administrator confirms what the vendor provides. The vendor contract decides what leaves with the retailer.

The [ecommerce operating workflows guide](/guides/how-to-identify-ecommerce-operating-workflows) covers neighboring workflows, and [chargeback representment records](/data-types/chargeback-representment-records) covers the dispute side, where a refund decision sometimes reappears.

## Questions to settle with the customer operations director

Keep to identifiers, tools and years. Partners never ask for orders, tickets or exports.

- Is the order number a required field on tickets, or typed into the text?
- Do cleared holds record the ticket ID and the approver?
- Is the case or refund ID written back to the order?
- How long does the returns app keep the log of each hold?
- Was the helpdesk ever exported during a tool change, and in which format?
- Which years does each tool cover, and has any of them been replaced?

The answers belong in an introduction, not a spreadsheet of records. The [workflow map template](/resources/workflow-map-template-business-records) helps a client draw its own version of this map; finance leads at online brands may recognize the setup from [the fractional CFO guide for ecommerce brands](/guides/fractional-cfo-for-ecommerce-brands), and owners preparing a sale can read [how to sell an ecommerce business](/guides/how-to-sell-an-ecommerce-business). For who can approve a licensing discussion, see [who can license refund abuse review records](/questions/who-can-license-refund-abuse-review-records).

The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 90% of the data is in English. Partners sign the Channel Partner Agreement before submitting; the first valid introduction within the 90-day window is credited when the company submits a verified application. Return and ticket records carry customer details, so counsel decides what could be licensed; buyer interest, the rights review result and any offer stay unknown until SourceX reviews it.

## Next step

> **Refer a company. Earn up to $100,000.** Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a retailer's tickets carry order numbers and its cleared holds point back to them, [register as a partner](/register), check the company against [who qualifies](/who-qualifies) and read the [program terms](/terms) before you ask the customer operations director to sponsor an introduction to the COO or CFO.

## Sources

- https://help.shopify.com/en/manual/shopify-admin/timeline
- https://help.shopify.com/en/manual/fulfillment/managing-orders/exporting-orders
- https://support.zendesk.com/hc/en-us/articles/4408886165402-Exporting-ticket-user-or-organization-data-from-your-account
- https://refer.sourcex.si/terms