This checklist is part of the return-to-refund records guide, which walks one partial bundle return through Shopify, Gorgias and Loop. Use that guide for the mechanics; use this page to judge a brand's trail.
Running the checklist in a single call
Ask the head of customer experience for 30 minutes, and invite the warehouse or 3PL contact for checks 5 and 6. Read each question as written and mark what you hear:
- Pass when the brand describes a routine that holds across most orders.
- Partial when it holds for some years, some channels or some agents.
- Fail when it does not happen, or nobody knows.
Do not total points. Read the marks in the bands under the scorecard, and write one sentence per partial or fail in the brand's own words. That sentence is what goes into an introduction.
The scorecard: eight checks across coverage, linkage, timestamps, outcomes and gaps
| # | Area | Check | How to check it at metadata level | Pass | Partial | Fail |
|---|---|---|---|---|---|---|
| 1 | Coverage | Years in each tool | Since when has each of storefront, helpdesk and returns tool held records, and what came before? | Five or more joined years, or migrations documented | Years exist but one tool replaced with history lost | Under two joined years |
| 2 | Coverage | Exceptions kept | Are rejected returns and returns closed by hand kept with their item list? | Kept and searchable | Kept for recent years only | Deleted or overwritten |
| 3 | Linkage | Ticket to order | Does each helpdesk ticket carry the storefront order number? | Linked as a field, refunds issued from the ticket | Linked for most; some matched by email | Matched by email only |
| 4 | Linkage | Bundle parts | Are bundle components listed as separate lines on the order? | Separate lines with a bundle ID | Separate since a recent year | One line, contents only in the product description |
| 5 | Timestamps | Dated steps | Are request, receipt, inspection and refund each dated in a system? | All four dated | Receipt or inspection undated | Only the refund date survives |
| 6 | Outcomes | Inspection per item | Does the warehouse mark each item received, missing or damaged? | Per item, with the order number | One note per box | No inspection record |
| 7 | Outcomes | Reason on the refund | Is a return created before the refund so a reason is recorded? | Return first, reason recorded | Reason typed in the ticket only | Refund with no reason anywhere |
| 8 | Gaps | Out-of-order cases visible | Can the brand find returns that went to review because money moved first? | Tagged or reported | Known to the team, not tagged | Not identifiable |
Two of the eight rest on vendor documentation rather than habit. For check 3, the helpdesk's own guide describes refunding a storefront order from inside a conversation, with a stated reason, and notes that doing so also opens a matching return record; agents who work that way leave the conversation and the order tied together. For check 7, the storefront's help explains that money can go back with no return attached, but then no return reason exists, and once items are refunded a return can no longer be opened for them. The payment history still shows an amount; the why is gone.
Reading the marks: when a returns trail is complete enough to discuss
| Pattern of marks | What it means | How to describe it |
|---|---|---|
| Checks 3, 6 and 7 pass | The reasoning for a partial refund is recoverable from records | "Ticket, inspection and refund join on the order number, with reasons recorded" |
| Checks 3 and 6 pass, 7 partial or fail | Reasons exist, but in free text | "Reasons survive in ticket notes, not on the refund" |
| Check 6 fails | Physical evidence missing; the shortfall in a box cannot be shown | "Refunds and conversations held; what arrived is not recorded" |
| Check 1 or 2 fails | A short or trimmed history | "Joined history from a stated year; exceptions not kept" |
None of these patterns disqualifies a brand. They change how you describe it and what SourceX looks at first.
One probing question, and the three answers you will hear
The hub follows one incomplete set through every tool. On a call you will not have that much time, so use a single prompt and listen for which of three routines the brand describes: "Say a four-piece pan set comes back and the warehouse finds no lid. Walk me through what happens to the money and to the paperwork."
| What the team says | Marks it implies | What a later reader of the records would find |
|---|---|---|
| "The 3PL logs the missing lid, the return closes, then the agent sends back the rest" | Checks 6 and 7 pass | A per-piece receiving note and a credit with a reason attached |
| "The agent usually credits something straight away to keep the customer happy, then we tidy it up" | Checks 7 and 8 partial | A credit, a return stuck in review and closed by hand, and the reason only if someone typed it |
| "Depends who picks it up" | Checks 7 and 8 fail | Amounts that reconcile and no explanation |
The middle answer is the one Loop warns about in its help center: crediting part of an order in the storefront before Loop has processed the return can trigger an error that parks the return for review, and the documented remedy is to reject it and finish by hand. Nothing is wrong with the totals afterward. What disappears is the reasoning, which is the part SourceX looks at first.
A marked example (Illustrative)
A fictional 280-person kitchenware brand selling cookware sets online, scored with its customer experience lead and 3PL account manager. Every answer is invented.
| # | Check | Answer heard | Mark |
|---|---|---|---|
| 1 | Years in each tool | Storefront since 2015, helpdesk since 2018, returns tool since 2021 with the old form archived | Pass |
| 2 | Exceptions kept | Rejected returns kept in the returns tool | Pass |
| 3 | Ticket to order | Order number on every ticket; most refunds from the sidebar | Pass |
| 4 | Bundle parts | Sets split into lines since 2023 | Partial |
| 5 | Dated steps | All four dated | Pass |
| 6 | Inspection per item | 3PL marks each item, with order number | Pass |
| 7 | Reason on the refund | Agents refund before the return in peak season; reasons in ticket notes | Fail |
| 8 | Out-of-order cases visible | Known to the team, not tagged | Partial |
Summary sentence: "Joined order, ticket and inspection history since 2021, per-item inspection, bundle parts split from 2023; refund reasons often only in ticket notes." That is what an introduction needs.
Owners, authority and what stays open
The checks name the owners: the head of customer experience for checks 3, 7 and 8, ecommerce operations for checks 1, 2 and 4, and the warehouse or 3PL contact for checks 5 and 6. None of them normally authorizes a licensing discussion; that is the CEO, or the founder in a founder-run brand.
Confirm the company basics: 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. The company fit checker covers the same tests.
SourceX licenses business data directly from companies and pays them for it. We are their counterparty from agreement through delivery and payment. Partners never ask for or handle orders, tickets or inspection notes. For why recorded judgment matters, see what human-in-the-loop data is; for a wider screen of a brand's operations, see how to identify ecommerce operating workflows; and if the conversation comes up during a yearly review, the annual client review handoff checklist helps. To record systems and owners in a shareable form, use the sibling return-to-refund metadata packet.
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.
Once you can describe the brand's returns trail in one honest sentence from its marks, register as a partner, confirm it on who qualifies and read the program terms before you introduce its sponsor.