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

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

At a glanceEstimated return cost by cause (90 days)Total estimated cost: $7,318 across 412 returns
  • Damaged in transit: $2,196
  • Runs small / sizing: $2,072
  • Color differs from photos: $1,148
  • Fabric feel / quality: $756
  • Changed mind / no reason: $574
  • Wrong item shipped: $572

Example for: an online apparel store, 412 returns over 90 days, $14 average cost per return, $22 write-off per damaged item.

Return Causes Ranked by Cost

CauseReturnsExample phrasesEst. costFixWhere
Damaged in transit61 (14.8%)"seam ripped when opened", "box crushed, button missing"61 x ($14 + $22) = $2,196Switch from poly mailers to padded mailers for knitwear; tape-test seams before packingPackaging, supplier/QC
Runs small / sizing148 (35.9%)"runs tight across shoulders", "ordered M, needed L"148 x $14 = $2,072Add garment measurements in cm and inches; add "runs small, size up" note on the 6 most-returned stylesSizing guide, product page
Color differs from photos82 (19.9%)"sage looked grey", "darker than pictured"82 x $14 = $1,148Reshoot top 10 colorways in daylight; add one unedited phone photo per colorProduct page
Fabric feel / quality54 (13.1%)"thinner than expected", "scratchy"54 x $14 = $756State fabric weight (GSM) and add a close-up texture shotProduct page
Changed mind / no reason41 (10.0%)"didn't need it", "no longer wanted"41 x $14 = $574Show return shipping fee at checkout to reduce impulse ordersProduct page, policy
Wrong item shipped26 (6.3%)"got a blue one, ordered black"26 x ($14 + $8 reship) = $572Add SKU barcode scan at packing stationFulfillment/QC

Total estimated cost: $7,318 over 90 days.

Top 3 Actions This Month

  1. Move knitwear to padded mailers and add a seam check before packing (targets $2,196).
  2. Publish measurement tables and "size up" notes on the 6 worst sizing styles (targets $2,072).
  3. Reshoot the 10 most-returned colorways in natural light (targets $1,148).

Data Gaps

  • Track which SKU and size each return came from; 38% of entries had no SKU.
  • Add a required reason dropdown so "changed mind" isn't used as a catch-all.
  • Log whether damaged items can be resold or are written off.

Assumptions: $14 cost applies to all returns and damage write-offs average $22; estimates are moderately reliable because 38% of rows lacked SKU detail.

Written by AI from this prompt. Your results will vary.

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 in Business