# Return-to-refund referral metadata packet | SourceX

Canonical: https://refer.sourcex.si/resources/return-to-refund-metadata-packet
Last updated: 2026-11-04

A referral partner can describe a brand's return-to-refund records with a one-page metadata packet: which systems hold orders, tickets and returns and since when, which object types exist, rough yearly volumes, whether bundles are common and how their parts are recorded, who owns each link, which gaps the brand already knows about and what stays unknown. Filling it in never requires opening an order, a ticket or a return label.

The packet belongs to the [return-to-refund records guide](/guides/chain-return-to-refund), which shows how the order number joins Shopify, Gorgias and Loop. This page gives you the fields to fill in and a completed example.

## What the packet is for, and what it is not

The packet answers one question for SourceX: is there a return-to-refund history here worth a closer look, and who can speak for it? It does that with descriptions only. Think of it as the cover sheet on a box nobody opens yet.

It is not a sample, an export or an assessment of quality. It does not need amounts, customer names, order numbers, ticket text, inspection photos or labels, and it should not contain any of them. If the brand offers "just one example", decline; a partner who handles raw records creates a privacy problem for the brand and for themselves.

For company-level fit (size, sector, geography) use the [online retail screening worksheet](/resources/a-referral-screening-worksheet-for-ecommerce-businesses). This packet covers one workflow inside a company that already looks like a fit.

## The packet fields, section by section

Eleven fields in four sections. Each has the question to ask and the person who usually knows.

| Section | Field | Question to ask | Usually answered by |
|---|---|---|---|
| Systems | Store platform | Which platform holds orders and refunds, and since which year? | Online sales manager |
| Systems | Helpdesk | Which helpdesk holds customer conversations, and since which year? | Support lead |
| Systems | Returns tool | Which tool manages return requests, and what handled returns before it? | Operations lead |
| Records | Object types | Which of these exist: orders, refunds, returns, inspection results, tickets, warehouse notes? | Support lead |
| Records | Return volume | Roughly how many returns a year, as a range? | Online sales manager |
| Records | Bundle share | Are bundles or kits a meaningful share of sales, and are their parts listed on the order? | Merchandising lead |
| Links | Refund path | Do agents refund from inside the ticket, in the store admin, or both? | Support lead |
| Links | Inspection record | Does the warehouse or 3PL record results per item, and does each note carry the order number? | Warehouse or 3PL contact |
| Gaps | Known breaks | Refunds before returns, returns rejected and finished by hand, a returns tool replaced mid-history? | Operations lead |
| Gaps | Retention | Are closed tickets, rejected returns and warehouse notes kept, and for how long? | Support lead |
| Gaps | Unknown until review | What would only become clear in a formal review? | Partner's own note |

Two fields carry the most weight. **Refund path** matters because Gorgias documents that an agent can refund an order from inside a ticket, with a reason, and that refunding items this way also creates a store return; refunds made elsewhere do not leave that link. **Known breaks** matters because the tools themselves describe the failure: Loop's help center says a partial refund issued in Shopify before a return is processed can send the return to Needs Review, where the documented fix is to reject it and finish in Shopify, and Shopify notes that a refund without a return records no return reason.

## An Illustrative filled packet

A fictional 240-person pet supplies brand selling direct online, with a third-party warehouse. Every entry is invented to show the level of detail.

| Field | Entry |
|---|---|
| Store platform | Shopify since 2016 |
| Helpdesk | Gorgias since 2019; shared inbox before that, not kept |
| Returns tool | Loop since 2021; returns handled by email form before |
| Object types | Orders, refunds, returns, tickets, 3PL inspection notes |
| Return volume | Between 15,000 and 25,000 returns a year |
| Bundle share | Starter kits are about a fifth of orders; parts listed as separate lines since 2022 |
| Refund path | Mostly from tickets; finance refunds in admin for escalations |
| Inspection record | 3PL portal, per item since 2022, order number on every note |
| Known breaks | Refunds before returns during peak season; rejected returns closed by hand |
| Retention | Tickets kept since 2019; 3PL notes kept 24 months under its contract |
| Unknown until review | Export fields, customer-data exclusions, what the 3PL contract allows |

Read it the way SourceX would. The joined history realistically starts in 2022, when bundle parts became separate lines and inspection notes went per item. The 3PL's 24-month window is the edge of physical evidence, and the contract question is a rights issue to flag, not solve. "Refunds before returns during peak season" tells SourceX the partial-bundle case exists at volume without anyone counting it.

## Fields that stay blank on purpose

Some entries should read "not known" or "not discussed", and that is a strength of the packet, not a weakness.

- **Amounts and averages.** Refund totals, average order value and return rates are commercial information the brand does not need to share at this stage.
- **Customer details of any kind.** Not even counts by region unless the brand volunteers them.
- **Export formats.** Whether a field exports cleanly is a question for the formal review. Guessing creates expectations nobody can check.
- **Quality judgments.** "Our agents always note the reason" is a claim. Write it as the brand said it, or leave it out.

The broader method is set out in [how to prepare a metadata-only inventory of business systems](/guides/how-to-prepare-a-metadata-only-inventory-of-business-systems). The live [HubSpot inventory template](/resources/a-metadata-only-hubspot-inventory-template-for-company-introductions) shows the same approach for a CRM, and the [workflow map template](/resources/workflow-map-template-business-records) helps when the brand wants to sketch the steps itself. Brands on a different helpdesk can borrow field ideas from the [Zendesk systems page](/systems/zendesk).

## Turning the packet into an introduction

A finished packet names two people: the sponsor who can authorize a licensing discussion, the CEO (in a founder-run brand, usually the founder), and the person who answered most fields, usually the support lead. Put both in your introduction.

Before you submit, confirm the company: 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. Partners sign the Channel Partner Agreement before submitting introductions.

What stays unknown until SourceX reviews it with the company: how customer personal data would be excluded or de-identified, what marketplace, payment and 3PL contracts allow, which years a buyer would value and what the brand would be paid. To test whether the trail is complete enough to discuss, score it with the companion [return-to-refund completeness checklist](/resources/return-to-refund-completeness-checklist); to see what one refund loses when read alone, use the [return-to-refund missing-context walkthrough](/guides/return-to-refund-missing-context).

## 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 you can fill in most of the packet in one call and name the brand's sponsor, [register as a partner](/register), check the brand on [who qualifies](/who-qualifies) and read the [program terms](/terms) before you send the introduction.

## Sources

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