Articles about return policies agree on the conclusion and repeat the same collection of figures. How many consumers check the rules before buying, how many return to a store with convenient returns, and how many abandon a purchase when return shipping is paid — these percentages circulate between articles without naming the study, sample, or year, so they cannot be verified or applied to a specific store. That is why you will not find them here, not even our own version. The only data that can settle the question is yours: the questions you receive and how people behave on your pages.
This article deliberately includes no market statistics about returns. Percentages repeated online usually give no source, sample size, or study date. Every metric described below is calculated from your own conversations and traffic.
Questions about returns measure how clear the rules are
If customers ask about returns before buying, that does not prove your policy is bad. It proves the information is unclear, incomplete, or buried too deeply. The rules may be very favorable — but if customers must ask about them, they still do not influence the decision. One person in dozens will write; the rest will close the tab.
Start by separating two completely different groups of questions. Pre-purchase questions (“what if it doesn't fit?” or “can I return it after trying it on?”) concern website content and are the subject of this article. Post-purchase questions (“how do I send it back?” or “when will I get my money?”) concern process and service — we discuss those separately in our article about complaint handling. Combining them in one report ruins the diagnosis because the first group concerns sales and the second service costs.
- A question asked from the product pageThe customer is beside the purchase button and cannot see the conditions. This is the strongest possible signal that information is missing at that exact point.
- A question about something covered in the termsThe answer exists, just not where the decision is made. The problem is content placement, not its absence.
- A question about return shipping costIf it recurs regularly, the amount is absent from the purchase journey or stated so generally that it settles nothing.
- A request to confirm the rulesThe customer read them but did not believe or understand them. This signals a problem with the language, not the location.
Each group leads to a different improvement, so counting all return questions together is not enough. A meaningful unit is the question plus the URL where it was asked. In Meetlead, the operator sees the customer's current page and the customer journey lists visited URLs, so the connection is recorded automatically.
Read your last thirty conversations with one question in mind: what did the customer want to know about returns before buying? See how Meetlead brings chat, callbacks, and tickets together in one place — including the URL where the question was asked.
Where this information belongs and at what stage of the decision
Most stores do have return information. It sits on a separate page linked from the footer and is written to comply with the law, not to be read during the decision. Yet the doubt “what if it doesn't work for me?” appears at a specific moment: while choosing a variant and beside the purchase button. The answer must appear there in a shortened form, not two clicks away. The question of timing works the same way in the gift season, which is why we separately explain how to state the last order date for delivery before Christmas without false promises.
Scroll the table sideways to see all columns.
| Location | What to write there | What to avoid |
|---|---|---|
| Product page, beside the purchase button | One sentence: how many days, who pays return shipping, and the condition in which the item must be returned | Only a “details in the terms” link with no information on the page |
| Size or variant selection | Information about exchanges for another size, if you offer them | Silence at exactly the point when doubt arises |
| Cart | Repeat the conditions in the summary before the customer gives their details | The first mention anywhere in the journey that return shipping costs money |
| Payment step | A one-sentence confirmation of rules the customer already knows | New restrictions that were not mentioned earlier |
| Return policy page | The complete step-by-step process, deadlines, return address, and form | A wall of text without headings, examples, or specific amounts |
| Order confirmation | A reminder of the return deadline and method | Silence until the customer starts looking for the information |
| Site-wide footer | One permanent link to one policy page | Several pages with conflicting versions of the same conditions |
The “what to avoid” column can matter more than the middle one because the most common problem is not missing content but poor placement. The same rule applies to the rest of the product description — we explain how to find gaps in our article about the product page. Returns are a special case, however: customers look for this information to stop fearing the decision, so providing it too late cannot rescue anything.
A buyer's rights in distance selling arise from the law and differ depending on the type of product, the status of the parties, and the sales channel. This article is not legal advice — consult a lawyer about the content of the rules themselves, and focus here only on whether customers can find and understand them.
The language of the rules: what worries and what reassures
Return rules are usually written defensively with abuse in mind. As a result, wording intended for a dishonest handful is read by everyone else and used to make a purchase decision. A phrase meant to protect the store instead says: we will look for a reason not to refund you.
Scroll the table sideways to see all columns.
| Phrase | How the customer reads it | How to improve it |
|---|---|---|
| Returns only in the original, undamaged packaging | If I open the parcel, I lose my right to return it | State clearly what customers may unpack, try on, and inspect |
| We consider returns individually | The decision depends on whoever happens to make it | Give the deciding condition instead of describing the review process |
| We reserve the right to refuse a return | They will find an excuse to refuse | Provide a closed list of exceptions with no open-ended clause |
| The buyer pays return shipping | I do not know whether that means twenty zlotys or a hundred | Give an amount or range for a typical parcel from your store |
| Refunds are issued within the statutory period | I have no idea when I will see my money | Explain when the period starts and how long it usually takes in your store |
| The product must be complete and unused | Trying it on probably counts as using it | Separate inspecting the product from using it normally |
The direction of improvement is the same in every row: replace a general formula with a decision. Customers do not need assurances about a friendly approach; they need a sentence that tells them what will happen in their situation. Return rules are also one of several elements people check before buying — we compare the others in our article about building trust on a website.
- Write the rules in the second person, just as you explain them in chat.
- State every figure explicitly: days, zlotys, and business days until the transfer.
- List exceptions as a closed set without phrases such as “including but not limited to.”
- Remove anything that sounds like a threat to an honest customer.
- Add one specific example of a typical situation involving your product range.
- Check that the short version on the product page and the full rules say the same thing.
- Ask someone outside the company to read the text and tell you what worried them.
Return cost disclosed early versus discovered at the end
Charging for return shipping is not a problem in itself. The problem is when the customer learns about it. The same amount stated on the product page is a condition of the offer; stated at the last step of the purchase, it is an unpleasant surprise — and that is how it will be remembered, together with the entire store. Postponing the information until the end does not reduce returns, only orders.
- Arrival on the product page
The visitor views photographs, changes the variant, and pauses at the size chart. There is no mention of returns beside the purchase button.
- Opening the policy page
A click on the footer link, a scroll halfway through the document, and a pause on the paragraph about return shipping costs.
- Return to the product page
The session returns to the same URL without adding the product to the cart. The visitor changes the variant twice more.
- Adding to the cart and opening the summary
The summary shows a different amount from the one remembered from the policy. The cursor pauses on that row.
- Leaving the summary
The session ends without an order. A few minutes later, someone asks in chat how much return shipping ultimately costs.
This sequence shows why the exit point alone can be misleading. Looking only at the step where the journey stopped, you would improve the cart. The recording together with the customer journey reveals the earlier visit to the policy page and return without a decision — shifting the improvement to where the problem actually arose.
A session recording and list of visited URLs show when the customer went to read the policy and what they did after returning. See how session recordings and maps work in Meetlead — separately for phones and desktops.
If a customer asks about a refund still in progress, use the guide: Refund still pending: explain the actual status to a customer.
How to use your own data to check whether the rules stop purchases
This is the part missing from return-policy guides. You do not need someone else's percentages, only three observations of your own: what customers ask and from where, who visits the policy page during the purchase journey, and where those sessions end. You can collect each one within a week without changing the store.
- Collect one month's questions about returns.Take thirty days of conversations, callbacks, and tickets. Keep only the pre-purchase questions; set the rest aside as an after-sales service topic.
- Assign every question to a URL.The operator sees the customer's current page, so you know whether the question came from a product page, the cart, or the policy page itself. The last option means the text is unclear.
- Count policy-page visits from the purchase journey.In the customer journey, look for sessions where the policy page appears between the product page and the cart. It is the closest available equivalent to asking, “are returns part of this decision at all?”
- Check what happens after that visit.Divide these sessions into two groups: those that return to the purchase and those that end on the policy. The ratio between them is your own metric, calculated every month using the same rules.
- Watch recordings of sessions that stopped.Five recordings are enough to see which paragraph stops the scrolling and whether the customer returns to it a second time.
- Check the reach of the short information on the product page.A scroll map will tell you whether the return sentence appears within the field of view for most visitors, separately on phones and desktops.
- Record the baseline before making improvements.Note the number of return questions and the proportion of sessions from step four before changing anything. Without that record, later assessment will be an impression, not a measurement.
If sessions end after customers have already given their details, the cause lies elsewhere and requires a different method — we explain how to break abandonment down by stage in our article about abandoned carts. Here, you are interested only in sessions where the return policy appeared before the decision.
Identify the one page from which questions about returns most often arise. Schedule an implementation — we will configure chat, recordings, and maps so you can see exactly where the decision stops.
A review routine instead of a one-off improvement
Once written, return rules remain untouched for years even though the product range, carrier, and return shipping prices change every few months. The gap between what the website says and what customer service does then emerges in chat. A short, repeatable review therefore works better than one major revision each year. During that review, also check how your team handles withdrawals submitted through the online withdrawal button.
- Once a month, review conversations for pre-purchase questions about returns.
- Check that the short information on the product page matches the full rules.
- Verify return shipping prices after every carrier price change.
- When adding a new product category, add its scenario to the rules immediately.
- Make one change at a time so you can attribute its effect.
- After a month, count whether questions about the same issue disappeared.
- Ask the service team what customers still ask despite what is written.
The second-to-last point is the most reliable metric. Sales growth depends on too many factors to attribute it to one sentence added beside the purchase button. The disappearance of a specific question after adding a specific piece of information, however, is direct evidence — visible within several weeks and countable in your own conversations.
It is also worth watching the direction of changes. The goal is not longer terms, but a shorter path from doubt to answer. If customers have stopped asking and sessions no longer end on the policy page, the return information is doing its job.
