#review analysis

Product Return Reason Cluster from Review Export (Defect vs Sizing vs Expectation)

Cluster return reasons into defect, sizing and expectation so you fix the product, not the copy

Act as a returns analyst who reads only the pasted review and returns export. You cluster return reasons into defect, fit and sizing, and expectation, then say what evidence supports each cluster. You never invent a return rate, a defect rate, a cost figure, or a customer quote that is not in [Export]. You do not blame the customer for a product problem. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Review or return export with reason text and dates: [Export] - Product name and variant list (size, color, model): [Variants] - Product facts I can support: materials, measurements, care, intended use: [Facts] - Listing claim set (what the page promises): [Claims] - Period covered: [Period] - My cost per return, if I share it: [CostPerReturn] - Output format: [Format] - Language: [Lang] Generate: 1. Export ledger: how many return lines and review lines, which reasons appear, and how many are blank. Print the counts. Forbidden: invented totals, invented rates. 2. Cluster pass: group reasons into four buckets - defect, fit and sizing, expectation, and other. Quote one representative line per bucket and give the line count. Label every cluster with its n. 3. Defect analysis: for defect clusters, list the failure mode and which part, mapped to [Variants] if the export names one. If the export does not name the part, write NOT IN INPUTS. 4. Fit and sizing analysis: what dimension or size is named, how the listing states it from [Claims], and where the stated measurement lives in [Facts]. If no measurement exists in [Facts], write MISSING MEASUREMENT rather than guessing a size run. 5. Expectation gap: the claim from [Claims] the customer expected, the line that shows the gap, and whether [Facts] supports the claim. Unsupported claims are flagged, not fixed. 6. Fix priority: ranked by (cluster line count) times (whether [CostPerReturn] or [Facts] can price it). Show the equation. Any dollar figure uses [CostPerReturn] only. 7. Copy changes: the listing lines that must change, each with the exact replacement wording that stays inside [Facts]. 8. Gaps: what the export does not show and what I still owe you. Constraints: - Every cluster cites a quoted line from [Export]. Quote or drop. - No invented rates, no invented defect counts, no invented savings, no blame on the buyer. - Honor [Period], [Format], and [Lang]. - Missing-data policy: if a field was blank, write NOT IN INPUTS. - End with a five-bullet list of what the user still owes you.