Are customer instructions linked to inspection and final refund approval?
Ask the owner in those words and listen for gaps between systems. A brand that can trace one return from the customer's stated reason to the inspector's grade to the refund or decline has a complete decision chain.
The chain is easy to overlook because each piece looks routine on its own. Shopify records the status: a return is requested, approved and opened, declined, or closed once every item is processed and a restock decision is made. Shopify also keeps a decline reason that is internal only and never shown to the customer, which makes it a candid record of why a refund was refused. The inspection in between, meaning condition grades, photos, notes and whether the item was resalable, frequently lives in the returns app or the warehouse system rather than in Shopify.
ShopifyA replacement project focuses on getting the new app live, the new portal styled and open returns migrated. Closed returns, and the inspection records that explain them, are easier to leave behind. A complete chain is what makes return history interesting to AI training and evaluation: a customer's claim, an independent check and a judgment with money attached.
The trigger is real for many stacks. Shopify introduced return processing in Admin API version 2025-07 and asks existing returns apps to migrate to the new returnProcess flow. Some brands will use that change, or an app contract renewal, as the moment to switch providers. An agency running the switch sees exactly which fields the old app held and which the new one will import.
The decision chain, system by system
Illustrative. A 180-person apparel brand on Shopify Plus replacing its returns app.
| Step | Record | Typical home | Ask, without opening anything |
|---|---|---|---|
| Customer instruction | Return reason, free-text comment, exchange or refund choice | Returns portal in the current app | Does the reason text survive the app change? |
| Approval or decline | Return status and internal decline reason | Shopify admin | Are decline reasons used consistently? |
| Inspection | Condition grade, photos, inspector note, restock decision | Returns app or warehouse system | Who keeps inspection history after cutover? |
| Refund approval | Refund amount, deductions, exceptions approved by a person | Shopify plus finance or helpdesk | Are manual overrides recorded with a reason? |
| Dispute or follow-up | Chargebacks, support tickets about the refund | Payments and helpdesk tools | Can they be tied back to the return? |
Followed through for a single order, the chain looks like this. A shopper sends back a merino base layer as "too itchy, wore it once" and asks for store credit. The brand approves the request in Shopify under its 30-day policy. At the warehouse, a packer notes a missing hang tag and faint deodorant marks, grades it "seconds" and routes it to the outlet bin rather than full-price stock. A customer-care lead then overrides the brand's usual 15% deduction because the shopper is a repeat buyer, and records "loyalty exception" as the reason. Four people, three systems and one judgment call: the packer's grade is the link that only the outgoing app holds.
Four metadata questions after the opener
- How many returns per year, and for how many years, has the brand graded and recorded? A range such as 30,000 to 40,000 returns a year since 2019 is enough to describe the set.
- Which systems hold the instruction, the inspection and the refund decision today? Note the names only. If inspection sits with a 3PL, ask whether the brand receives the grades or only a restock count.
- Does the replacement plan migrate closed returns and their inspection records, or only open ones? Most plans migrate open returns; closed history is the part at risk.
- Who owns the decision about the old app's data once the contract ends? Usually the brand's owner or COO, sometimes with the head of ecommerce. Ask whether an export of closed returns has been requested and in what format.
Does the brand qualify, and what stays unknown?
Many Shopify Plus brands run lean, so headcount is the first check.
- 50+ full-time employees at peak, contractors excluded. Warehouse staff count if they are full-time employees; 3PL staff do not.
- A documented operating history and rights to license the records, including any limits in 3PL or app agreements.
- An authorized contact who can open a licensing discussion.
- 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 90% of the data is in English.
| Known at introduction | Unknown until SourceX reviews it |
|---|---|
| Return volumes, years and systems as the owner describes them | SourceX's current data needs for returns decision data |
| Whether the chain is complete or broken, and where | The rights review result, including 3PL and app terms |
| Old app contract end date | Any offer to the brand |
| That the reward was disclosed | Whether a reward becomes payable |
Partners never handle customer records. For more on which ecommerce workflows tend to matter, see ecommerce referrals and identifying ecommerce operating workflows. For system replacements more broadly, see ERP replacement introductions and the ERP replacement introduction plan, or browse the partner hub and the network opportunity finder.
Reward disclosure and owner permission
Sign the Channel Partner Agreement before submitting. The first valid introduction within the 90-day window is credited when the company submits a verified application; one partner per company. Tell the owner you may receive a referral reward that SourceX pays separately, so it never reduces the brand's payout. Illustrative arithmetic only: if the brand were paid $40,000 for a qualifying completed handoff, the reward would be $10,000. 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.](/rewards) explains each condition. A short introduction then names the app contract end date, the return volumes and years the owner described, and that SourceX licenses approved operating records directly from companies.
Go deeper on returns platform replacements
- Returns platform replacement introduction email: a template for introducing the brand's decision-maker before the old app goes dark, with the disclosure included.
- Returns platform replacement meeting agenda: a timed agenda for the first owner conversation about return decision history.
- Returns platform replacement archive context checklist: a checklist of export, retention and ownership facts to confirm before cutover.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If the owner can trace returns from instruction to refund and wants to talk before the old app goes dark, register as a partner, check the brand against who qualifies, and read the program terms before you make the introduction.