# Return-to-refund records across systems | SourceX

Canonical: https://refer.sourcex.si/guides/chain-return-to-refund
Last updated: 2026-11-04

An ecommerce brand connects return-to-refund records by carrying the Shopify order number through every step: the customer's message in Gorgias, the return and inspection result in Loop, and the refund on the Shopify order timeline. The test that shows whether the chain holds is a bundle returned with pieces missing. If the brand can say which record explains the reduced refund, the chain is intact; if the refund stands alone, the reasoning was lost.

## The business task behind the chain

Every return asks the brand to make three judgments. Customer service decides whether the request is valid and what to promise. The warehouse decides what actually came back and in what condition. Finance, or an agent with refund rights, decides how much money goes back. When those three agree, the return is routine. When they do not, someone has to reconcile them, and the reasoning behind that reconciliation is the most informative part of the record.

Bundles make the judgment harder. A customer buys three items at one price, returns some of them, or says they returned all three when the box held two. The refund then has to be split across items the brand may have priced only as a set. Across thousands of orders, the joined history of how a brand handled cases like that is a record of operational judgment. Each tool holds only one part of it.

## Records held in Shopify, Gorgias and Loop

- **Shopify.** The order is the spine. The order Timeline in Shopify admin shows the order's transaction history, including returns, refunds and restocking. Shopify notes that an order can be refunded without a return, but a refund without a return records no return reason, and a return cannot be created for items already refunded.
- **Gorgias.** Gorgias shows Shopify orders in the ticket sidebar and lets an agent refund from there, setting quantities, shipping, a reason, restocking and notification. Quantities above zero also create a Shopify return. That makes the ticket-to-order link strong when agents use the sidebar, and weak when they refund in Shopify directly.
- **Loop.** Loop manages the return request, the label and the outcome. Loop documents that a partial refund issued in Shopify before a Loop return is processed can cause a refund error that sends the return to Needs Review, and that its fix is to reject the return and issue the outcome manually in Shopify. Whether inspection results are recorded per line or as one note is a company practice to ask about.

Warehouse notes about what was physically in the box often live outside all three tools, in a spreadsheet or a shared inbox. Ask where they live and whether they mention order numbers. Nothing on this page implies SourceX connects to Shopify, Gorgias or Loop.

## Example linkage table: one bundle, five events

The case below is Illustrative. A customer returns a $180 fitness bundle: a mat, resistance bands and a foam roller. The brand and customer are fictional.

| Day | Event | System | Join key | Join status |
|---|---|---|---|---|
| 0 | Customer asks to return all three items | Gorgias ticket | Shopify order number in the sidebar | Supported when the sidebar is used |
| 1 | Agent issues a partial refund early to calm the customer | Gorgias, written to Shopify | Order number | Supported by the system |
| 1 | Return for all three items requested | Loop | Order number | Supported by the system |
| 6 | Box arrives with the mat and roller; bands missing | Warehouse note | Order number, if written | Depends on warehouse habit |
| 7 | Loop return hits Needs Review, is rejected, refund finished in Shopify | Loop and Shopify | Order number | Supported, but the reason is lost |

Illustrative. Join status describes how the link would be made, not a tested export.

The money reconciles in the end. The mat is refunded at $70 and the roller at $60 while the bands get $0 because they never arrived, so the customer receives $130 against the $180 bundle. The explanation does not.

## What breaks when the return package contains only part of the bundle

The unresolved case is day 7. Because a partial refund was issued before Loop processed the return, the return went to Needs Review and was rejected, and the rest of the refund was issued by hand in Shopify. Shopify records that refund without a return reason. Anyone reading the order later sees $130 refunded on a $180 bundle and no record of why the bands were not refunded.

Three records decide whether this case can be explained later:

1. **The ticket.** If the agent noted the early refund and the missing bands in Gorgias, the reasoning survives there.
2. **The warehouse note.** If inspection recorded per item that the bands were absent, and the note carries the order number, the shortfall is provable.
3. **The rejected Loop return.** If the brand keeps rejected returns with their original item list, the gap between requested and received is visible.

Ask the brand one question: "When a bundle comes back incomplete, where would I find who decided the refund amount and why?" If the answer points to one place that carries the order number, the chain holds. If it is "it depends who handled it," the reasoning lives in people, not records.

## Authorized sponsor and introduction

Name two people. The sponsor is the CEO, often the founder, who can authorize the brand to explore licensing its own records. The systems owner, often the customer experience lead, answers questions about coverage.

The brand must meet the program's company tests: 50+ full-time employees at peak (contractors excluded), documented operating history, the rights to license 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 70% of the data is in English. Many direct-to-consumer brands run lean, so check headcount early on [who qualifies](/who-qualifies), the [ecommerce industry page](/industries/ecommerce) and the [ecommerce screening worksheet](/resources/a-referral-screening-worksheet-for-ecommerce-businesses).

What stays unknown until SourceX reviews it with the company: how customer personal data is excluded or de-identified, whether marketplace or payment-processor terms limit any records, what the 3PL contract says about warehouse data, and whether the order-level links hold at scale. Partners never ask for or handle raw records. For a wider screen of ecommerce operating records, see [how to identify ecommerce operating workflows](/guides/how-to-identify-ecommerce-operating-workflows); for why human judgment in records like these matters to AI developers, see [what human-in-the-loop data is](/proof/what-is-human-in-the-loop-data). Brands on a different helpdesk will find the [Zendesk systems page](/systems/zendesk) and the [systems hub](/systems) useful. Partners sign the Channel Partner Agreement before submitting introductions.

## Go deeper on return-to-refund records

- [What a single-system return export loses](/guides/return-to-refund-missing-context): a before-and-after reading of one return, with and without its surrounding records.
- [Return-to-refund metadata packet](/resources/return-to-refund-metadata-packet): a fill-in packet of the facts a partner can share without touching orders or tickets.
- [Return-to-refund completeness checklist](/resources/return-to-refund-completeness-checklist): a pass, partial or fail scorecard for judging whether the returns trail is complete enough to discuss.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a brand you advise can trace its partial returns from ticket to inspection to refund, [register as a partner](/register), confirm the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before introducing its sponsor.

## Sources

- https://help.shopify.com/en/manual/fulfillment/managing-orders/returns/creating-returns
- https://help.shopify.com/en/manual/fulfillment/managing-orders/refunding-orders
- https://docs.gorgias.com/en-US/shopify-actions-461552
- https://help.loopreturns.com/en/articles/1910657
- https://refer.sourcex.si/terms
