> For the complete documentation index, see [llms.txt](https://docs.zigpoll.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zigpoll.com/guides/how-to-reduce-product-returns.md). # How to Reduce Product Returns Returns are usually treated as a logistics problem. They're a data problem. Every return is a customer telling you that something on the product page didn't match reality — and if you capture *what*, you can fix the page instead of eating the shipping cost forever. Most stores already know their return rate. Very few know their **return reasons at the SKU level**, which is the only version of the number you can actually act on. *** ## Building the survey ### Question 1 — The reason Add a **Single Choice** question: **"Why are you returning this item?"** Write options that map to a fix. "Didn't like it" is useless; these are not: * It didn't fit — too small * It didn't fit — too large * It looked different from the photos * The quality wasn't what I expected * It arrived damaged * It arrived too late * I ordered the wrong item * I changed my mind Splitting "too small" from "too large" matters enormously. A SKU with a 15% return rate that's *entirely* "too small" is a sizing chart fix. A SKU where returns split evenly between too small and too large is an inconsistent-manufacturing problem. Same rate, completely different response. ### Question 2 — The detail Add a **Long Answer** question: **"Tell us more — what would have helped you choose correctly?"** This question is doing the real work. Customers routinely name the exact missing element: a measurement, a photo of the fabric up close, a model with their body type, a note about the fit running small. ### Question 3 — Photo evidence (when relevant) For quality or damage returns, add a **File Upload** question and enable **mobile auto-capture** so the camera opens automatically on phones. Use [Question Logic](/questions/question-logic.md) to show this question only when someone selects "arrived damaged" or "quality wasn't what I expected." Photos of damaged goods let you distinguish a shipping problem from a manufacturing one without a support thread. ### Question 4 — Keep the customer A return doesn't have to be the end of the relationship. Branch on the reason: * **Wrong size** → offer an exchange. Use a **Redirect To** action pointing at the right variant. * **Changed my mind** → show a [Promo Code question](/tutorials/adding-discount-codes-to-your-survey.md) to convert the refund into store credit. * **Damaged** → route straight to support with a [Zendesk](/integrations/zendesk.md) or [Gorgias](/integrations/gorgias.md) action. *** ## Where to run it * **In the returns flow** — Trigger the survey when a customer initiates a return with a [Custom Survey Trigger](/tutorials/custom-trigger.md). Highest response rate, because they're already in the flow. * **Email when a return is received** — Send a [survey link](/survey-links.md) automatically once the return is processed. * **Post-delivery, before a return happens** — An [order delivery survey](/tutorials/order-delivery-survey.md) asking "How did it fit?" catches sizing problems from customers who are *keeping* the item. That data is free and it tells you the same thing. {% hint style="info" %} Tag the order and the customer with the return reason using the **Add Order Tag** and **Add Customer Metafield** Question Logic actions on Shopify. The reason then lives in Shopify alongside the order, where your merchandising team already works. {% endhint %} *** ## Reading the results The unit of analysis is the **SKU**, not the store. A 12% store-wide return rate is meaningless; it's an average of a catalog where a few products are quietly bleeding. 1. Export responses from the **Table** tab, or sync to [Google Sheets](/tutorials/sync-survey-responses-to-google-sheets.md). 2. Group by product. Zigpoll captures the Shopify line items associated with each response, so you can see the reason mix per SKU. 3. Rank products by **return rate x margin**. Fix the expensive ones first. Then match the dominant reason to the fix: | Dominant reason | The fix | | -------------------------------- | --------------------------------------------------------------------------------------------------- | | **Fit (skewed one direction)** | Update the size chart; add "runs small" to the product copy | | **Fit (split both directions)** | A manufacturing consistency problem — talk to the supplier | | **Looked different from photos** | Reshoot. Add photos in natural light, on varied body types, with a scale reference | | **Quality below expectations** | Either the copy is overselling or the product is underdelivering. The open-ends will tell you which | | **Arrived damaged** | Packaging or carrier — check whether it clusters by region | | **Arrived too late** | Set delivery expectations honestly at checkout | Z-GPT Insights will summarize the open-ended answers into themes automatically once you have volume, which is how you find the specific missing measurement without reading 400 responses. *** ## Prove it worked Fix one product page, then watch that SKU's return rate for the next 60 days. Returns are one of the few survey-driven fixes with a clean, direct financial readout — every avoided return is the shipping cost, the restocking labor, and the margin, all recovered. *** ## Related {% content-ref url="/pages/70rirBfJvG59hsGptkAE" %} [How to Find Out Why Visitors Aren't Buying](/guides/how-to-find-out-why-visitors-arent-buying.md) {% endcontent-ref %} {% content-ref url="/pages/4piDyM90vZseDkvbqgru" %} [Order Delivery Survey](/tutorials/order-delivery-survey.md) {% endcontent-ref %} {% content-ref url="/pages/IRRir9qUNoP5cQDOlBsl" %} [Fulfillment Survey](/tutorials/fulfillment-survey.md) {% endcontent-ref %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.zigpoll.com/guides/how-to-reduce-product-returns.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.