Return-to-refund completeness checklist: eight pass, partial or fail checks for an ecommerce returns trail

Short answer

A return-to-refund trail breaks when a later step settles the money without carrying the reason forward. The usual breaks are a helpdesk ticket matched by email instead of order number, a refund issued before the return exists, an inspection note that covers the whole box instead of each item, and a bundle sold as one line. The hardest case is a package holding only part of a bundle. The eight checks below let a partner mark each break pass, partial or fail from one conversation, without opening an order.

Visual briefFull-size diagram
A gauge rises as eight returns-trail checks are marked in turn, ending at five passes, two partials and one fail on the refund reason check.
Illustrative marks for a fictional kitchenware brand. The marks describe the trail; they do not predict acceptance.

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

#AreaCheckHow to check it at metadata levelPassPartialFail
1CoverageYears in each toolSince when has each of storefront, helpdesk and returns tool held records, and what came before?Five or more joined years, or migrations documentedYears exist but one tool replaced with history lostUnder two joined years
2CoverageExceptions keptAre rejected returns and returns closed by hand kept with their item list?Kept and searchableKept for recent years onlyDeleted or overwritten
3LinkageTicket to orderDoes each helpdesk ticket carry the storefront order number?Linked as a field, refunds issued from the ticketLinked for most; some matched by emailMatched by email only
4LinkageBundle partsAre bundle components listed as separate lines on the order?Separate lines with a bundle IDSeparate since a recent yearOne line, contents only in the product description
5TimestampsDated stepsAre request, receipt, inspection and refund each dated in a system?All four datedReceipt or inspection undatedOnly the refund date survives
6OutcomesInspection per itemDoes the warehouse mark each item received, missing or damaged?Per item, with the order numberOne note per boxNo inspection record
7OutcomesReason on the refundIs a return created before the refund so a reason is recorded?Return first, reason recordedReason typed in the ticket onlyRefund with no reason anywhere
8GapsOut-of-order cases visibleCan the brand find returns that went to review because money moved first?Tagged or reportedKnown to the team, not taggedNot 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 marksWhat it meansHow to describe it
Checks 3, 6 and 7 passThe 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 failReasons exist, but in free text"Reasons survive in ticket notes, not on the refund"
Check 6 failsPhysical evidence missing; the shortfall in a box cannot be shown"Refunds and conversations held; what arrived is not recorded"
Check 1 or 2 failsA 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 saysMarks it impliesWhat 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 passA 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 partialA 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 failAmounts 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.

#CheckAnswer heardMark
1Years in each toolStorefront since 2015, helpdesk since 2018, returns tool since 2021 with the old form archivedPass
2Exceptions keptRejected returns kept in the returns toolPass
3Ticket to orderOrder number on every ticket; most refunds from the sidebarPass
4Bundle partsSets split into lines since 2023Partial
5Dated stepsAll four datedPass
6Inspection per item3PL marks each item, with order numberPass
7Reason on the refundAgents refund before the return in peak season; reasons in ticket notesFail
8Out-of-order cases visibleKnown to the team, not taggedPartial

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.

  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

How many fails rule a brand out?

None on their own. The checklist describes the trail so your introduction is accurate. A brand with two fails that it can explain is still worth describing; SourceX decides fit in its own review.

Why does the order of return and refund matter so much?

Because the tools record different things depending on it. Shopify notes that a refund issued without a return records no return reason, and Loop documents that a partial refund issued before its return is processed can push the return into Needs Review and a manual fix. The sequence decides whether the reason survives.

Can the brand run the checklist without me?

Yes. A customer experience lead can answer it internally and send you the marks. Ask for the marks and one sentence per fail, never the records behind them.

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