Return-to-refund records in Shopify, Gorgias and Loop: joining a partial bundle return from ticket to refund

Short answer

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.

Visual briefFull-size diagram
A reconciliation grid for an illustrative three-item bundle: all three items requested for return, two received at inspection, two refunded, and a warning that the refund in Shopify carries no return reason after the Loop return was rejected.
Illustrative bundle return. The money reconciles; the explanation does not.

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.

DayEventSystemJoin keyJoin status
0Customer asks to return all three itemsGorgias ticketShopify order number in the sidebarSupported when the sidebar is used
1Agent issues a partial refund early to calm the customerGorgias, written to ShopifyOrder numberSupported by the system
1Return for all three items requestedLoopOrder numberSupported by the system
6Box arrives with the mat and roller; bands missingWarehouse noteOrder number, if writtenDepends on warehouse habit
7Loop return hits Needs Review, is rejected, refund finished in ShopifyLoop and ShopifyOrder numberSupported, 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, the ecommerce industry page and the ecommerce screening worksheet.

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; for why human judgment in records like these matters to AI developers, see what human-in-the-loop data is. Brands on a different helpdesk will find the Zendesk systems page and the systems hub useful. Partners sign the Channel Partner Agreement before submitting introductions.

Go deeper on return-to-refund records

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, confirm the company against who qualifies, and read the program terms before introducing its sponsor.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Is return-to-refund history mostly customer data?

It contains customer details, which is why partners never handle it. What may be licensable is the brand's own operating pattern: how exceptions were judged and settled. Exclusions and de-identification are settled in SourceX's review with the company.

Does the brand need all three tools for this to matter?

No. Three tools are the example on this page. A brand on one platform with a helpdesk still records the same steps; what matters is whether they can be linked and whether the company has the right to license them.

Does the reward come out of the brand's payout?

No. SourceX pays any eligible reward separately; it is never deducted from the company's payout. The default formula and conditions are on the terms page.

Sources

  1. help.shopify.com/en/manual/fulfillment/managing-orders/return…
  2. help.shopify.com/en/manual/fulfillment/managing-orders/refund…
  3. docs.gorgias.com/en-US/shopify-actions-461552
  4. help.loopreturns.com/en/articles/1910657
  5. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment