Hi - I’m looking for a very simple CSV export of items returned. The export should list each returned SKU on a separate row with
date returned / SKU / Shipping location / Order Number / refund amount
All reports and dimensions I have tried is not working. Any help in guidance would be great.
Thanks!
Try Shopify’s Analytics > Reports > **Exploration
**
I’ve found the AI bot gets pretty close when you ask it to find the data you’re looking for or update queries.
FROM sales
SHOW quantity_returned, returns
GROUP BY day, product_variant_sku, order_name, pos_location_name WITH TOTALS
HAVING returns > 0
ORDER BY day ASC
VISUALIZE quantity_returned
@NCLTD, Hi, You can genreate this report using Items returned by product premade report. Just paste the below SQL query in the report to see the data your are looking for. Find the screenshot for your reference.
Query
FROM sales
SHOW returns, total_returns
WHERE product_title IS NOT NULL
GROUP BY day, product_variant_sku, order_name, shipping_city WITH GROUP_TOTALS,
TOTALS
SINCE startOfDay(-365d) UNTIL today
ORDER BY day ASC, product_variant_sku ASC, order_name ASC, shipping_city ASC
LIMIT 1000
VISUALIZE returns TYPE bar
Thanks
Hi, you can easily create this export with DataChamp. You can either use the refunded template, which you can customize to your requirements, or build the report from scratch to include the specific fields you need. If you have any questions, feel free to reach out!
The ShopifyQL approach works for basic export but where it falls short is connecting return reasons to specific products in a way that’s actually actionable. You can pull quantity_returned and group by SKU, but the reason data and the product page context that caused the return aren’t in the same query. If you’re doing this regularly, the Returns API gives you line item level return reasons which is way more useful than the refund note field. You can pull returnLineItems with their returnReason and then join that against your product data to see which SKUs are driving the most returns and why. It takes some API work to set up but the output is way more useful than a flat CSV of refund amounts.
Refund data always feels simple until returns start piling up and someone asks why a specific product keeps coming back.
Then you realize the information is split across refunds, notes, shipping data, support conversations, warehouse comments, etc.
Getting the export is one problem. Figuring out what actually caused the returns is usually the harder part.
