# Return-to-refund missing context: before/after | SourceX

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

A single-system export of an ecommerce order keeps the amounts: what was charged, what went back and when. It loses why. The customer's request, what the warehouse actually received, the conversation that settled a disputed item and the reason a refund was partial all live elsewhere, usually in the helpdesk, the returns app and a warehouse note. Read alone, a careful partial refund can look like a mistake or a short-changed customer.

This page is part of the [return-to-refund records guide](/guides/chain-return-to-refund), which shows how the order number joins those systems. Here one fictional case is read twice: first as the order record presents it, then with everything around it restored.

## Before: what the order record says on its own

Illustrative. A fictional 210-person travel goods brand sells a three-piece luggage set for $260. Every value below is invented, and the rows describe this example, not a tested export format.

| What the order record shows | Value |
|---|---|
| Order total | $260, one line: luggage set |
| Fulfilled | Yes, shipped in one parcel |
| Refunded | $220, issued nine days after delivery |
| Return attached | None |
| Return reason | None recorded |

Shopify's documentation explains the last two rows. An order can be refunded without a return, but a refund issued that way records no return reason, and once items are refunded a return can no longer be created for them. The order Timeline still shows the transaction history, so the reader knows money moved. Nothing in the record says why.

### What a reader concludes from the order alone

1. The customer paid $260 and got $220 back.
2. No return exists, so nothing came back to the warehouse, or nobody logged it.
3. The $40 difference has no explanation. It might be a restocking fee, a goodwill credit gone wrong or an agent error.
4. Conclusion: an unexplained partial refund, possibly a customer who was short-changed.

Each step is reasonable. The conclusion is wrong.

## After: the same refund with its ticket, return and inspection note

Restore three more records and the story changes. Same fictional brand, same invented values.

- **Helpdesk ticket, opened on delivery day plus two.** The customer writes in Gorgias asking to return the whole set: carry-on, toiletry bag and packing cubes.
- **Returns app record, same day.** A Loop return is requested for all three items, with a prepaid label.
- **Warehouse note, delivery day plus eight.** The parcel holds the carry-on and the toiletry bag. The packing cubes are not in it.
- **Ticket again, the next day.** The customer chases the refund. An agent sends $220 back from inside the ticket, covering the carry-on at $150 and the toiletry bag at $70, and writes "cubes not received, told customer to check with carrier."
- **Returns app, afterward.** Because money already went back on the order, the Loop return lands in Needs Review. Loop's help center documents exactly this: a partial refund issued in Shopify before the return is processed can cause a refund error, and the fix is to reject the return and handle the outcome manually in Shopify. The return is rejected.

Now the $40 has a reason: the packing cubes never arrived, and the agent told the customer so in writing. Gorgias can create a store return when an agent refunds specific items from a ticket. In this case the agent refunded an amount, so no return was created on the order. Whether a reason was typed depends on habit, not on the tools.

## The lost-context table: what disappears and where it lives

The table below is the core of this page. Each row is context the order record drops, where it usually lives at a mid-size brand, who owns it and the key that reconnects it.

| Lost context | Order record alone | Where it usually lives | Usual owner | Reconnecting key |
|---|---|---|---|---|
| What the customer asked for | Not shown | Helpdesk ticket and returns app request | Customer experience lead | Order number on the ticket |
| What actually arrived | Not shown | Warehouse or 3PL inspection note | Warehouse or 3PL contact | Order number, if the note carries it |
| Why the refund was partial | Amount only | Agent note on the ticket | Customer experience lead | Free text, if typed |
| Whether the return was processed normally | Not shown | Returns app status, including rejected returns | Ecommerce operations | Order number |
| A recorded return reason | None, refund issued without a return | Ticket note or warehouse note only | Customer experience lead | Typed reference |
| Which components the set contains | One bundle line | Product catalog or bundle app | Merchandising | SKU or bundle ID |

Illustrative. The table describes the example above; whether each key exists at a given brand is a question to ask, not an assumption.

Two rows matter most. "What actually arrived" is the only record of physical evidence, and it often lives outside every software tool, in a 3PL portal or a shared spreadsheet. "Which components the set contains" decides whether the $40 can be tied to an item at all; a bundle sold as one line with its contents only in a product description cannot be split later.

## Why the joined version is the one with training value

The standalone order shows a number. The joined history shows a judgment made under uncertainty: the customer says three items went back, the warehouse found two, and a real agent decided what to refund and explained it. That is the kind of record that is hard to find elsewhere, and the reason a single-system export undersells what a brand holds. The general pattern is covered in [what data is missing from AI training](/questions/what-data-is-missing-from-ai-training).

The same logic runs through payment disputes. A chargeback read without its customer history looks similar to this refund read without its ticket; [chargeback representment records](/data-types/chargeback-representment-records) describes that adjacent workflow.

## Checking for missing context without reading an order

A partner never needs to see the order, the ticket or the note to test this. Three questions to the customer experience lead are enough:

1. "When a refund is partial, where would I find the reason?" One named place that carries the order number is a strong answer.
2. "Where does the warehouse record what was in a returned box, and does it note the order number?"
3. "Do you keep returns that were rejected or closed by hand, with their original item list?"

Then confirm the company. The brand must have 50+ full-time employees at peak (contractors excluded), documented operating history, 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; advisors such as [fractional CFOs for ecommerce brands](/guides/fractional-cfo-for-ecommerce-brands) often know it offhand.

What stays unknown until SourceX reviews it: how customer personal data is excluded, what the 3PL contract says about warehouse records, whether marketplace or payment terms limit anything and what the brand would be paid. The sponsor is the founder, CEO or COO; the customer experience lead answers questions. Partners sign the Channel Partner Agreement before submitting introductions. To record the answers in a shareable form, use the sibling [return-to-refund metadata packet](/resources/return-to-refund-metadata-packet); to judge whether the trail is complete enough to discuss, use the [return-to-refund completeness checklist](/resources/return-to-refund-completeness-checklist).

## 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 point to where the reason for a partial refund lives, [register as a partner](/register), check it against [who qualifies](/who-qualifies) and read the [program terms](/terms) before introducing its founder or COO.

## 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
