Find Why Customers Return Products Using Your Return Reasons Data
Groups your pasted return reasons into root causes, estimates what each cause costs, and pairs each with a product page, packaging, or sizing fix ranked by cost.
You getTable, top 3 actions for this month and data gaps
Prompt
Act as an ecommerce operations analyst who specializes in reducing product returns.
I will paste my return reasons data right after this prompt (free-text reasons, return codes, or a store export). If I don't include my average cost per return (shipping, restocking, lost product value) or my product categories, first ask me up to 3 short numbered questions in one message and wait for my answers.
Your job: group the return reasons into root causes, estimate what each cause costs, and pair each cause with a specific fix.
Rules:
1. Group by root cause, not by the customer's wording ("too small" and "runs tight" both go under sizing).
2. Quote 1-2 real phrases from my data as evidence for each cause. Never invent reasons or numbers.
3. Show the cost math for each cause: number of returns x cost per return, adding write-off or reshipping costs where they apply.
4. Every fix names where it happens (product page, packaging, sizing guide, or supplier/QC) and is something I can ship within 30 days.
5. Rank causes by estimated cost, highest first.
Output format:
- Table: Cause | Returns (count and %) | Example phrases | Est. cost | Fix | Where
- Top 3 actions for this month, one line each
- Data gaps: what to start tracking
End with one line on the assumptions you made and how confident the cost estimates are.Example output
Tips and common edits
Why this works
- Grouping by root cause instead of customer wording merges scattered complaints into a few fixable problems.
- Showing the cost math for each cause lets you check the numbers and decide what to fix first.
- Requiring a named location and a 30-day timeline turns each insight into a task someone can own.
Use after exporting 60-90 days of returns from Shopify, WooCommerce, or your returns app. Paste the reasons into ChatGPT, Claude, or Gemini, and have your average cost per return ready.
Common edits
- Ask for results split by product category or SKU to find the worst offenders.
- Add a column estimating how many returns each fix could prevent.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Audit an Ecommerce Product Page for Conversion Problems and Rank the Fixes
Get a 1-5 scorecard of your product page across six fixed areas, plus a ranked list of concrete fixes sorted by likely impact versus effort.
Calculate Your Real Product Profit Margin After Fees, Shipping and Ads
Get a per-unit profit table for one product, covering fees, shipping and ad spend, plus your break-even ad cost per sale and break-even ROAS.
Write a Blameless Post-Mortem from Your Incident or Project Failure Timeline
Paste your incident notes and get a structured blameless post-mortem with a timeline, a five-whys root cause analysis and preventive actions owned by roles, not people.
Write Amazon or Etsy Product Titles and Bullets That Match Buyer Searches
Get a marketplace-compliant product title, five Amazon bullets or Etsy description lines and tags, with character counts and a map of where each search term appears.
Write Ecommerce Product Descriptions From Your Specs and Customer Questions
Paste your product specs and real customer questions and get a benefit-led description, a scannable spec table, an FAQ, and a list of claims that need proof.
Write Quarterly OKRs with Baselines, Targets and Measurable Key Results
Turns your goals into up to three quarterly objectives, each with outcome-based key results that have a baseline, a target, an owner and a data source.