Returns operations, next to Loop and orders
ReturnGO returns sit outside order reporting. Return events, reasons, and refund transactions land in the shared returns table, matched to Shopify orders.
- Credential
- ReturnGO API key plus your shop name
- API budget
- 2,000 calls a day, shared by every store on the ReturnGO account; history fills in over several runs
ReturnGO
CRM, customer support, returns, and people operations platforms.
Why ReturnGO?
SourceMedium lands ReturnGO returns beside Loop Returns so post-purchase leakage is visible in the same warehouse as orders.
Return events
Returns sync at event grain with their line items, shipments, and ReturnGO transactions.
Customer-selected reasons
Each return keeps the reason the customer picked in ReturnGO, for its largest returned line.
Refund and gift-card amounts
Settled refund and gift-card transactions are attributed to the return they belong to.
No double counting
Once ReturnGO returns land for a store, they replace Shopify's native returns.
Before you analyze
Boundaries that change how ReturnGO numbers should be read.
Count returned orders once
Returns are events, and one order can have several. Use COUNT(DISTINCT sm_order_key) for returned orders.
Details in the docsUnknown money is NULL
ReturnGO records no upsell or exchange totals, so those fields are NULL, and a return cost with no known components is NULL rather than zero. Money coverage differs from Loop Returns, so check it before combining the two.
Details in the docsWhat you can ask
With SourceMedium Agent, you can query ReturnGO data using natural language. Here are some examples.
What share of last quarter's orders had at least one ReturnGO return? Which products drive the most ReturnGO returns? How does ReturnGO volume compare to Loop Returns? How it works
Setup depends on the source. We confirm access requirements, history, cadence, and customer responsibilities before implementation begins.
Create an API key
In ReturnGO, add an API key under Settings, then Integrations, then API.
Connect with your shop name
Enter the key and your shop name, usually your .myshopify.com domain. SourceMedium checks both before saving.
Let history catch up
History loads across several daily runs within ReturnGO's API budget. Compare totals once the counts stop climbing.
Ready to stop debating the numbers?
In 30 minutes, we will
-
Map your current systems and reporting gaps.
-
Show one workflow relevant to your team.
-
Outline likely fit, implementation scope, and next steps.
Book a walkthrough
Share a little context, then choose a time immediately after submitting.
Choose a time for your walkthrough
Open the calendar in a new tab
We couldn't load available times here.
Open the scheduling calendar in a new tab. If you cannot schedule now, we will still follow up.
Open scheduling calendar