E-commerce Returns: How to Cut Costs and Keep the Customer (Krzysztof Kukla, Wygodne Zwroty)
E-commerce Returns: How to Cut Costs and Keep the Customer (Krzysztof Kukla, Wygodne Zwroty)
Episode in Polish, English subtitles available. Below: an edited English translation of the full conversation.
Krzysztof Kukla, at the time of recording CEO of Wygodne Zwroty, a Polish returns service, talks to Tomek Runowicz and Maciek Czerniak about turning returns in an online store from a cost into a source of data and loyalty. He covers how to write a returns policy customers understand, which hidden returns costs to count in customer service, the warehouse and accounting, and what happens when a brand drops free returns. He also explains how to handle returns of used items, why returns data should go back to Google Ads, and how to offer a customer a different size instead of a refund. The conversation was released in September 2024 and is aimed at owners and managers of online stores, mainly in fashion and footwear, where returns are a large share of costs.
Key takeaways
- A returns policy should be short and clear without a lawyer. Krzysztof's template: "You have 14 days to return the item without giving a reason. We'll refund you, say, within three days of the parcel reaching us." Keep the terms and conditions for the lawyers, let customers request returns online, and ask for the reason in an open text field rather than a list of checkboxes, because AI can analyze the answers quickly. (7:13)
- The minimum for dropping off a return is a dense network of points: retail chains such as Żabka convenience stores, InPost parcel lockers and other companies' lockers. A courier pickup at home is less convenient because you have to wait for it. Decathlon, which already had its returns well organized, wanted exactly that: a drop-off network beyond parcel lockers. (9:04, 10:30)
- Before changing anything, measure the baseline: returns-related chats, emails and calls, time spent finding parcels in the warehouse, manual refund transfers (Krzysztof saw a store that got about 60 confirmation texts a day from its bank), credit notes, and mid-collection products that come back after two weeks and have to be sold at a discount. Add the carts abandoned by customers put off by a wall of text in the returns policy. (12:39, 14:52)
- According to Krzysztof, in the 6 to 12 months before the recording, Polish brands including Kazar, Venezia, Lavard and Skalnik dropped free returns. Brands with physical stores often keep returns free in store, which creates a chance to upsell. In his view a fee in the "low teens of zlotys" is acceptable to a loyal customer, and the effect on conversion exists but is small. (17:15, 18:28)
- A little effort from the customer cuts returns sharply. One of Poland's top retailers stopped putting a return label in the parcel and asked for a simple online form instead: return volume fell by 60%. A rule of "one order, one free return," instead of returns sent back in instalments, cuts volume by 5 to 10%. (19:50, 20:41)
- The model process: an online request lets the warehouse plan its work, a scan of the shipping label identifies the parcel (also when the customer sent it outside the system, which applies to a few to a dozen-plus percent of returns), and one click refunds the customer, issues the credit note and puts the item back in stock. An automatic email saying "your return has arrived, we'll settle it within 3 to 4 days" takes load off customer service. (21:45, 23:01)
- Returns of used items make up 2 to 5% of returns according to Wygodne Zwroty's research, and stores usually don't dispute them. For repeat abuse, some stores keep a list of problematic customers (by phone number or email), secure their orders with a tag that can't be cut off, or exclude them from Google Ads campaigns. What matters is the ratio: 30 returns on 300 orders a year is still a healthy customer. (25:31, 27:53, 28:47, 29:33)
- Start improving with the cheapest changes: a simple policy communicated in the order email, the FAQ, the footer and checkout, and, in the warehouse, automatic order lookup. Finding an unregistered parcel often takes several minutes, sometimes more than ten. (31:00)
- When ad platforms learn from orders that are later returned, they optimize for the wrong customers. Krzysztof: "Google got a signal from the site that a transaction happened, worth 1,000 zlotys. (...) Then there's a return, and that 1,000 turns into a round zero. But Google doesn't know that." The fix is importing returns data into Google Ads and Google Analytics. (36:50, 38:43)
- A return doesn't have to end the sale. If the store learns about it right away, not when the parcel is opened, it can offer another size, and for a loyal customer ship it immediately and ask for a review. Precise product measurements, the model's height in photos, a customer size profile and customer photos under the product also prevent returns. (39:16, 42:10, 44:59, 47:42)
Guest
Krzysztof Kukla had, at the time of recording (2024), worked in e-commerce for over a decade. He ran AlleKurier, Wygodne Zwroty and Logistiko, was involved in Traffic Peaks (sponsored articles), and worked on sea freight, consolidating goods from China and customs clearance. Wygodne Zwroty, which he said had been running for three years and served over 1,300 brands, simplifies the returns process for online stores, mainly in fashion and footwear. In the episode he announces a full Shopify integration.
Hosts
Tomek Runowicz and Maciek Czerniak run wecanfly, a Shopify Premier Partner agency that helps established brands with complex migrations to Shopify Plus. Today we work with AI agents built into processes and guardrails based on experience from many projects, and every change is approved by an experienced person on our team.
Two of Krzysztof's tips have worked for our clients. For GANT's Polish store we automated returns with Shopify Flow and the InPost Quick Returns API: a standard return picks its own parcel size, keeps the customer informed and never lands on the customer service team's desk (GANT case study). At Le Collet, the main cause of returns was choosing the right size across collections, so instead of a static size chart we added detailed measurements for every category and the Keep AI size assistant (Le Collet case study). Foreign returns and shipping to European countries run through the integration we built for Global24 (Global24 case study).
We cover return policies per market, Shopify's return rules, self-serve returns and exchanges in Foreign Returns on Shopify: 10 Tips for Selling Internationally in 2026, and keeping customers after the first order in Loyalty Programs on Shopify: How to Design, Measure, and Scale Them. Jędrzej Przeździęk talks about retention in the episode OpenGift: How to build retention in e-commerce? (in Polish, with an English transcript).
Transcript
This transcript is based on the recording of this episode. We edited it for readability: we corrected transcription errors, punctuation, and merged sentences that were cut off mid-flow. We did not change the content, order, or meaning of anything said. Any errors or inaccuracies are our responsibility alone — not our guests'. If you spot something that needs correcting, email us.
Conversation released on 24 September 2024. Below is an edited translation of the conversation. Numbers and market data are given as they were said in the episode, and where something has changed or needs context, we add a dated 2026 update.
Who is Krzysztof Kukla and what is Wygodne Zwroty?
Tomek: Hi, welcome to another episode. This time we're back to returns in e-commerce, but we'll approach the topic a bit differently than before. We'll talk about how to turn returns into success for your e-commerce business, what data your store should analyze and how, and how to improve the returns process. At the end we'll also cover how a well-run returns process can be used effectively in marketing. Our guest today, Krzysztof Kukla, CEO of the Wygodne Zwroty product, will tell you all about it. Enjoy the conversation.
Hi Krzysztof, thank you very much for joining us for this episode. We have an interesting and slightly unusual topic, because we'll talk about a process that in e-commerce we tend to associate with negative experiences. Today we want to break the spell and show how it can be used and turned into business. But before we get into the conversation, could you tell us about yourself in a few sentences? I know from various sources, and above all from you, that you're very engaged and busy in many areas. Tell our listeners a bit about yourself.
Krzysztof: First, I'd like to thank you for the invitation. I'm very glad we can talk together today. I'll keep it short, let's not waste time on it. I've been working in e-commerce for over a decade. I run several projects, such as AlleKurier, Wygodne Zwroty and Logistiko, and I'm also involved in the Traffic Peaks project, which is sponsored articles. I also deal more broadly with sea freight and consolidating goods from China, and I'm involved in anything related to customs clearance.
Tomek: You know what, Krzysztof, I don't think it's ever happened that my introduction matched what the guest said so closely. Honestly, if that was the short version, I won't ask for the extended bio, because we'd probably have to record a separate episode. You just confirm you're the right person for today's topic. Among the companies you mentioned Wygodne Zwroty, a service and company that seems perfectly suited to today's subject. Could you give us a literally short ad break about what Wygodne Zwroty is?
Krzysztof: Okay, very briefly. Wygodne Zwroty simplifies and optimizes the returns process in online stores, mainly in fashion and footwear, where the problem usually hurts the store the most. Inefficient processes, high handling costs in both the warehouse and customer service. But also from the perspective of the consumer who has to return the item: it's frustrating and off-putting, and it means they either don't buy or go to a competitor. That's the short version.
Tomek: Also short, but very concrete, and I think it got the essence across. Thanks a lot for that introduction.
How can a store turn returns to its advantage?
Tomek: Let's get to the topic. Returns, as I said, seen from the outside, are mainly associated with a failed transaction, an unwanted stage in e-commerce. Let's try a different angle. I know you follow a different principle, which shows in the company you founded. We mentioned it in one of our episodes when we talked about building a better customer experience. So let's start there: how, in your view, can we break the spell of returns and use them to the store's advantage?
Krzysztof: I'd like to add something here. We all know that in e-commerce conversion and customer experience matter, and lots of people make sure the cart, the checkout and everything that happens until the goods are delivered is as good as it can be. But still few stores take care of the post-purchase process, especially when the item didn't match the customer's taste or size. That's where we commit 100% to improving the experience, because, surprisingly, it can very often spoil the impression the customer has of our brand.
Tomek: I completely agree. What's more, the returns stage often gives us the truest picture of how customers perceive our company. Nobody dresses up their comments and opinions in nice words there; they say very concretely why they're returning the item. So I think it's also a chance for a great, direct interaction with a customer who doesn't sugarcoat anything. With reviews, we encourage customers to leave one, and sometimes they do it just to say "leave me alone, here's a review, it was okay." With returns it's something completely different, right?
Krzysztof: Yes, I agree. Imagine what the customer went through: they chose a product online, paid upfront, waited for delivery, picked it up from the courier and put a lot of time into it. He put it on, or usually she did, and it doesn't fit. That customer really will spend a minute writing something. Even three or four sentences that give us a hint, because negative emotions have to come out somewhere, and it's better if they come out in our form than on external review sites.
Maciek: It's like when people send food back in a restaurant because they don't like something. Instead of using the chance to get feedback, the owner gets angry. And instead of saying what's wrong, that the pickle doesn't go with Nutella or whatever, the customer later pours out their anger in reviews, on Google and so on. How can we make sure returns aren't just an unpleasant obligation? How can we turn them to our advantage and see them as an opportunity? Are there strategies for that? Maybe you can tell us about a company that did it well?
How do you write a returns policy customers understand?
Krzysztof: I could tell many such stories, because we already serve over 1,300 brands, but I'll try to pick out the most important things. First of all, the starting point is the returns policy. It should be clear and simple, without legal language, because mostly nobody reads it, and that kind of language doesn't build trust. The message should be very simple: you have 14 days to return the item without giving a reason. We'll refund you, say, within three days of the parcel reaching us. That's it. That's enough. Of course, keep the terms and conditions for the lawyers, but with the customer, use that simple message.
Second, show what to do and what steps to take to send the return. It certainly shouldn't be a paper form where you write everything with a modern pen, at a time when we all have everything on our smartphones: the account number, the reasons, the checkboxes. Let's do it online, as simply as possible.
I'd also mention the reasons. Ask the customer in an open text field what made them return the product. Don't limit yourself to a single-choice field, because with today's technical possibilities we can use AI to analyze large data sets very quickly and draw conclusions. And an open answer doesn't narrow the perspective from which the customer looks at our product.
Maciek: That's interesting, because various tools and plug-ins for collecting feedback on returns often have preset parameters: was the size wrong, too big, too small and so on. As you say, those are fields to fill in and an imposed perspective.
Krzysztof: Yes.
Where should customers be able to drop off a return?
Krzysztof: What else? How the return is handed in, meaning where it physically has to be taken. I think the minimum standard is being able to drop it off in retail chains, for example in Żabka convenience stores. That's a must-have, and so are InPost parcel lockers and other companies' lockers, because there are more and more of them and they're gaining share. Don't lock yourself into one option. I prefer it myself, and over the last few years I've seen that it's the most preferred drop-off method. Not necessarily booking a courier pickup at home, because you have to wait for the courier. That is demanding: knowing someone will come at a set time, or maybe be late. It's unnecessary. Let people drop off returns in a dense network of points, and that's enough.
Tomek: Krzysztof, when Maciek asked what tips you'd give, I think he had a reason to ask about your huge experience, which you gained probably watching many companies that handled returns better or worse. Is there at least one case you consider a real model and could tell us about? Or why do you think a given client does it really well?
Krzysztof: I can give the example of Decathlon, which we serve. Because of its scale, it already had these processes very well sorted and does most of these things, but one thing was missing: it wanted to extend its drop-off network. Not only InPost lockers, but also Żabka stores or other retail chains. And I have to admit they do it well. They test different hypotheses, test free and paid returns, draw conclusions and analyze what's happening. The returns process from the customer's point of view is what they see in the browser. But what happens backstage, in the warehouse, in accounting or in the store's analytics, is a completely different story that most people don't see. I'd have a few examples, but I'd rather not talk about companies' internal processes.
Which hidden returns costs should you count?
Tomek: Of course, that's not what we expect from you, God forbid. But you know what you said, Krzysztof? You used a word that often works on me like a magnet: "analysis." Let's stay with that for a moment. How should we treat and approach the returns in our store? The one thing that seems basic when analyzing returns is working out the company's real revenue, minus returns. But I assume the analysis should go deeper. What should a store take into account when analyzing this process? What should it pay the most attention to? Ratios, metrics? How should it look at costs? What does your experience tell you?
Krzysztof: From my perspective, I'd start by measuring many things that aren't obvious at first. I'd start with customer service, meaning I'd tag or record how many returns-related tickets we handle in chat, by email and by phone: how to return, did the return arrive, when's the money, is everything okay. That's real time we lose.
Second: how long the physical handling of returns takes in the warehouse, from receiving parcels from one courier or many to finding those parcels in the system, manually if someone didn't register the return, or automatically by scanning the shipping label. Then the accounting work: clicking a refund at the payment provider or making a manual bank transfer. I've seen a store that handles dozens of returns a day make transfer after transfer, confirming each one by text message. We know how long it takes to get 60 texts a day from the bank. That's the time. Then credit notes, which we either issue ourselves or outsource to an accountant who charges us for every document. All of these are components that let you even know the baseline: how much time and energy we lose.
There are also more complex things. For example, we have a product from the middle of a collection. We sell it, it sits with the customer for two weeks or more and comes back, but now it has to be sold at a discount. Not because it's damaged, but because, for some products, it's no longer current or in fashion.
Tomek: Sure. So a whole lot of non-obvious, hidden costs that probably seem trivial at first glance, and the bigger the scale, the more of them can be hidden. But the time spent handling a return in different areas, and probably the disruption, because a return isn't the store's natural process of serving and shipping to the customer, really is an important part of this analysis.
Krzysztof: Yes. There's one more aspect that's hard to measure but definitely exists: how many carts are lost and transactions abandoned because someone read the returns policy and saw a wall of text, didn't understand it, or found out: "Please contact us and we'll give you instructions." That alone can worry some customers: "What, they won't take it back?" Or, for example, not refunding the original shipping cost, which by law the seller should refund. Of course, I mean refunding the shipping cost.
Tomek: That probably adds up to loyalty. If you once have a problem with a return in a store, you won't shop there again.
Krzysztof: Yes. Why did big players such as Allegro introduce Smart, which according to its stock market reports is probably one of its main cost items? For loyalty. Communicating free returns removes the worry about buying, so you buy. If need be, you'll send it back.
Do returns have to be free?
Tomek: Yes. The e-commerce market is still in a state where returns have to be free. It's seen as good practice. We know Zalando introduced that rule first and everyone followed. It's certainly a very costly part of the business, but there seems to be slowly growing pressure, or a sense, that maybe not always for free, because not paying for returns sometimes encourages customers to buy a lot, assuming upfront they'll try things on and send back the rest, a fairly large part. First, do you see a trend changing this? And second, as someone who works on returns and watches these processes, do you think they should be paid after all, or do we need some balance, some rules?
Krzysztof: I think the trend exists and has sped up a lot over the last six to 12 months, because e-commerce people see that something is wrong with sales. They're there, but not growing, sometimes even falling; there's a slump. We see more and more brands dropping free returns, even after many years. Recently, for example, Kazar, Venezia, Lavard, Skalnik and many smaller companies.
Several things happened, and here's one curiosity. Stores that have a network of shops in malls, or just physical stores, don't offer free returns online, but you can return the item for free in one of their shops. So customers go to the shop, and that's a great chance to upsell. From the store's point of view it's win-win: the customer still has a free return, and the store gets a chance to upsell.
Tomek: And what about those without physical stores? Do you have data on whether paid returns lower conversion?
Krzysztof: Based on what we've implemented: there is an impact, but it's not a sudden, clearly visible drop that breaks the business. If a customer is determined, the kind who will probably return, they'll look for a free return on Zalando, on Allegro or another fashion marketplace. I think a return fee in the low teens of zlotys is acceptable to a loyal customer. Customers who will return things will buy on a marketplace, which ends up giving it a return rate of around 70%. But if you drop free returns, you absolutely have to make the process as simple and pleasant as possible and keep the price as low as possible. Let's not put more obstacles in customers' way.
Maciek: That's a very interesting aspect, especially given how popular buy now, pay later has become, and especially in fashion, where people often order two or three sizes of the same product and the return is assumed from the start.
How does a little customer effort reduce returns?
Krzysztof: Yes. I've noticed a few things too. I have information from one of the top retailers in Poland that used to put a return label in the parcel. Just like that: free returns, and all you had to do was go to a drop-off point. When it stopped including the label and required the buyer to fill in a simple online form, that alone cut return volume by 60%. So adding a bit of gentle effort was enough.
Tomek: So on one hand let's simplify the method, and on the other let customers do at least a little work on the return.
Maciek: We once had a client who boasted that he had 0% returns. But that was because his returns process was so complicated that people simply gave up and wrote Google reviews about him instead.
Krzysztof: I think another quick win, if you offer free returns, is to stop one thing. Like you said: someone ordered three sizes or, say, five pieces of clothing, and the seller allows any number of returns per order. It ends with someone having, say, 30 days to return and sending items back in instalments over those 30 days. I've seen that in several stores. We can change that: you have one order and one free return. Introducing that rule alone cuts return volume by 5 to 10%.
Maciek: Okay, that's a great insight.
Tomek: A nice tip, honestly.
What should a model returns process look like?
Maciek: Good. Tell us how we can improve the returns process, because that's what your company actually did. You didn't invent returns, you just made them better. What can a merchant do to take care of this process? What should a model process look like?
Krzysztof: On the customer side, it's a simple process that requires an online request, so we collect the data and get the signal that the customer is returning something. That lets us plan warehouse work: we know, for example, that 200 parcels will arrive tomorrow. Second is the warehouse itself and how the process works there. The parcel should be identified very quickly. Ideally we scan the shipping label and immediately know, in one system, which order it is. And if someone sends it outside our system, which happens and still applies to a few to a dozen-plus percent of returns, it's worth having a system where, even when a parcel comes by Polish Post, we scan the waybill and know which order it is, although the return wasn't registered.
Then you quickly tick off which products arrived, one click, and the money should go back to the customer's account. The invoice should be issued automatically and the stock level quickly increased. That's how it should look. Depending on their technical possibilities, companies handle these elements differently. Some do it by hand, others have parts automated. We'd like to automate it fully for everyone.
Maciek: What else? Go ahead.
Tomek: No, sorry, go on, since you asked "what else?"
Krzysztof: Among things that are easy to implement: automatic communication with the customer. Imagine it's December 5th, the third pallet of returns has arrived, and we know we won't process them today or tomorrow. Maybe we'll get to them in three days. Then at least let customers know the return has reached us and will be settled within three or four days, and then send a second email saying everything has been handled. Without such a simple feature, customer service gets lots of tickets, a dozen or more calls or emails. It's a simple rule too: when parcels come in from the courier, we scan them all, the emails go out, and then we process the returns at our own pace.
Tomek: Since at this stage we're talking about how your product helps improve the process: do you have a case study you can show off, with numbers, like how much a process was improved or how much was saved on returns costs with the Wygodne Zwroty tool?
Krzysztof: I'll speak somewhat generally, but I'll give the example of Supersklep, a company from Kraków. We spoke recently and they confirmed that most of the questions about the returns process simply don't come in anymore, or only a marginal number, because simple information on the returns page of the website is enough. Second, email notifications solve that issue. Another thing: they see which returns will arrive today, so if a parcel isn't labeled correctly or something isn't included, they can work it out from our report, and receiving returns itself got much shorter.
I also want to say that we keep developing the tool. The project has been running for three years, our development team collects feedback from stores, and we follow the customer. We've done many returns process audits in large online stores in Poland, and based on them we release new iterations and features.
What do you do with returns of used items?
Maciek: While we're on improvements, I'm also interested in how you approach returns of used goods.
Krzysztof: According to our research in stores, it's a few percent of returns. Let's say two, three, at most five percent. Most stores take a very liberal approach: if someone sends back a used item, they don't even argue with the customer. They'd rather freshen it up or even repair it somehow. Of course, if someone goes too far, meaning you can see it's clothing worn at a party or a ceremony and it's no longer fit for use, there's often a smaller or larger deduction from its value. I've even seen a 99% deduction, because the item was useless. Then the consumer asks: "Okay, send it back to me after all." There are different ways to deal with this practice, because it exists, and looking at Western markets, I think it will unfortunately grow in Poland.
Tomek: Sorry, Maciek. I think it's a very delicate process. On one hand, the customer is probably fully aware and doing it on purpose, but still using the right to return. They expect it to be tolerated, maybe that the company won't react negatively and the return will go through. On the other hand, as a store owner, we want to assert our rights here, because it's a breach of the returns policy, and the product is either simply unsellable or has a significant defect that will affect its resale price. Keeping the balance in how you communicate it to the buyer is really an art, so they don't become dissatisfied with the store's service in general. So they don't pour out that mass of emotions you mentioned earlier in a review, which will be hard to defend against, because other comments will soon flood it.
Krzysztof: There are a few tips on how to prevent this. For example, some create customer blacklists, meaning a specific email address or, better, a phone number. If someone was a problematic customer once or twice, then next time an order comes from that phone number or email, we secure the item with a clip or a tag, an inserted strip that can't be cut off, and we communicate that. If it's removed, we can argue with the customer that it justifies a deduction in value, as with damage. Some stores do this, and it's effective. The key is to keep a good, systematic database of, let's call them, problematic customers, so you don't tag every product this way, because that costs more work than it brings potential benefit.
Tomek: Right.
Krzysztof: Another tip is what one of our clients does. He keeps a database of these customers, just emails, and excludes them from Google Ads campaigns by email address or phone number. He simply said: "I really don't want to advertise to them. Let them buy somewhere else."
Maciek: I have clients with problems like this: their customers, mostly women, make 100, 200, 300 returns a year. Very often these are so-called fashion influencers who borrow the clothes for free this way. Sometimes you see discussions on LinkedIn about what to do with such rascals.
Krzysztof: Yes. Of course, you always have to weigh it carefully, because someone making, say, 30 returns a year doesn't mean anything yet. If they placed 300 orders, the proportions are healthy and it's still fine.
Maciek: It's worse when someone returns what they bought for free.
Krzysztof: Yes.
Where do you start improving returns?
Tomek: Krzysztof, let's take the conversation a bit further. Existing processes and improvements to the returns process have come up a few times. Can you tell us where to even start improving these processes in a company? You've already said a bit about checking how it looks today. But the process consists of individual steps. First question: which one would you start with? Where would you look for that first step to get moving? And second: I assume that whenever you improve something that works, there's sometimes a temptation to take a shortcut, which leads to mistakes. In your experience and observations, which of these elements come up most often?
Krzysztof: What I see is that stores come to us needing to optimize the process. We tell them which areas to improve, and unfortunately that runs into the real need to involve the IT team or change warehouse processes. That's a hard moment. Then we conclude: let's start with the lowest-hanging fruit. I think it's a good approach, because people see that something has already been done, and that's how it works in companies. Let's start with the baseline and measure it roughly. It doesn't have to be pharmacy-level precision, but let's know roughly what the process looks like, so that in a quarter we know we invested this much and improved this much. Of course, the deeper you go, the more it costs, but the results will keep growing too.
Where would I start? With communication to consumers: simplifying the returns policy and communicating the returns process wherever possible, so that everything leads to the one place where the return is requested. For example, in the order email, in the FAQ, in the site footer, maybe during checkout as an extra nudge to remove objections. That way we collect the data in one place. Second, I'd look at how the process works in the warehouse and what we can automate there at low cost. Especially looking up orders, both registered returns and ones not registered in any way. From what I see, finding an unregistered order often takes from several minutes to more than ten, so that adds up to a lot of work.
Tomek: Okay, fine. When it comes to processes, I personally picture it like this: first I check how things look at my company, and then I tighten the individual steps, as you said, even with small changes at first. I assume implementing everything, especially at large scale, isn't always simple or easy, and it probably takes a long time. It takes some effort.
How can you use returns in marketing?
Tomek: Let's make a small pivot in our conversation. So far we've said returns shouldn't be the store's Achilles' heel and that they can help build loyalty and how customers perceive the brand. But it would be good to also explore how to use returns, which may not be obvious, to strengthen the message in marketing. It's a non-obvious element of a store that can have a very real impact on marketing.
Krzysztof: Okay, so how to communicate returns in marketing?
Tomek: Yes.
Krzysztof: I think Zalando does it very strongly. It emphasizes 100 days and so on. You don't need to invent much; you need to repeat the same thing. We don't have to give 100 days. I think Zalando uses the ownership rule: if you have to do something tomorrow or in a week, you'll still remember it. But in 100 days, it slips your mind. I'd give a lot to meet someone who notes in their calendar today, counts 100 days and sets a deadline for sending clothes back. That's certainly been calculated too.
Tomek: Yes, it lulls you, but there's also the endowment effect: the thing feels like mine since I've used it for so long, and it's harder to return it.
Krzysztof: Yes. I think a longer return window can be tested, because it depends on the customer profile, age and product. It'll work for some and not for others. You can also use a trick like this: if you return the item to us quickly, the return is free. Say you got the clothes on Monday; if you send them back on Tuesday, it's free. That motivates people not to wear the clothes.
Tomek: Mhm.
Krzysztof: And it means we get the goods back sooner, so we sell them sooner. It's a race against time.
Tomek: Yes. We can rotate stock much faster after all, because the item comes back into stock and we can quickly earn on it again.
Krzysztof: Yes. Procrastination is unfortunately common, and everyone remembers only on the last day. We see it on the charts: day 14 is often return day.
Tomek: Just like a student who starts studying the night before the exam.
Why should returns data go back to Google Ads?
Tomek: Since we're on marketing, I can't help asking about returns in the context of paid ad campaigns, for example Google Ads. I wanted to ask how to do this well. We know there are industries where returns reach as much as 70%; those are the ratios there. Then the performance agency shows us the results, and all the ROAS and ROI figures glow green. But if we factor in returns, it doesn't look so rosy anymore, right?
Krzysztof: Yes. And the agency will add that it's not really their fault, it's the product's or the customer's, and that they can't do anything about it. I say that's not entirely true. Unfortunately, most stores in Poland don't do this, due to a lack of technology or a lack of awareness that Google recommends automatically importing returns data into Google Ads, and into Google Analytics too. Imagine: Google got a signal from the site that a transaction happened, worth 1,000 zlotys. It has this consumer's profile and thinks: "Okay, now I'll look for similar profiles and optimize for customers like this." Then there's a return, and that 1,000 turns into a round zero. But Google doesn't know that and keeps optimizing for the wrong consumers. It's low-hanging fruit, but unfortunately most companies don't implement it.
Tomek: I think it comes mainly from a lack of awareness among merchants. But it's also not really in the interest of the people involved to talk about it, because it's easier and nicer to present sales results not distorted by returns and show off the results of your work, and harder to admit that reality is, as you said, completely different.
Krzysztof: Yes. But I think aware owners who understand how important this is in the whole process will demand it, or will count the way they should, because it's in their vital interest.
Maciek: How does it work technically? When a return happens, should the store tell the Google Ads API that the return took place?
Krzysztof: Yes. You can find the transaction and reverse it, that is, retract it, whether it was a full return or specific products from the transaction. That information is then taken into account by the algorithm that targets further ads.
2026 update (as of 14 November 2026): in Google Ads this is done with conversion adjustments. You can retract a conversion completely or restate its value, for example when a customer returned part of an order. Conversions need an order ID; for automated bidding to take the adjustment into account, it has to be uploaded within 7 days of the conversion being recorded, and adjustments are possible within 54 days overall (support.google.com). In Google Analytics 4, refunds are measured with the refund event and the transaction ID (developers.google.com).
What returns data should you collect and how should you use it?
Maciek: Okay, great. I think we can move on. Since we're on data, that's another interesting area. What data about returns should we collect, and how should we use it?
Krzysztof: From my perspective, first I'd warn against what I call data-itis, a disease of data: we have lots of data about everything, but no time, or no person on board who could find the time to analyze it, draw conclusions and see the change through. So I suggest starting with something simple and minimal, and only then gradually expanding it. I suggest an open-ended return reason. At first, that's easily enough. You can use it for product analysis, to improve the offer.
The second idea is trying to prevent returns. We have a customer who said she's withdrawing from the purchase. Fine, before she sends it back, let's contact her automatically, through marketing, or even manually if the goods are valuable. Let's offer her: size 34 doesn't fit, so we'll send another one, smaller or bigger, and do it automatically, as a suggestion. Most stores don't do this, because they learn about the return when the warehouse worker opens the parcel. And that's too late, because by the time she's returning it to you, she's already buying what she wants in another store.
Tomek: That's a really nice, interesting observation. In fact, Shopify announced this feature at the latest Shopify Editions. It's in development and being rolled out to everyone, but it addresses exactly the problem you described. When I get a return request in my store, instead of treating it as a regular return, settling it and ending the relationship with the customer, I can very easily offer them something instead, as you said. In many cases the return happens because the size, or maybe the color, doesn't fit. Then it's very easy to keep the customer, but it has to happen right at the start of the process, not several days later, once the product has reached us and we've worked out what the return was about and got back to the customer. It's definitely worth stressing that a return never means we lose the customer for that particular transaction. We can turn it around so the customer gets what they need, and for us as a store it won't be a return; it'll still be a sale.
2026 update (as of 14 November 2026): on Shopify, exchanges are created in the admin from the order, as part of a return. Shopify's self-serve returns still don't let customers request an exchange, only a return or a cancellation (help.shopify.com). If size exchanges are central to a store, it usually needs a returns app or a custom flow.
Krzysztof: Yes. I'll add that when a customer wants to return something, it's a great chance to build a relationship and turn them into a loyal customer. Imagine someone buys a dress for a party, and we have this customer's profile. She's bought from us for the sixth or tenth time and has been loyal. What's stopping us from sending her the new size right away? Today she reports that she wants to withdraw because the size is too small, and we ship immediately. With so many purchases, she's not a random person. We solve her problem and right after that ask for a review.
Tomek: A very good idea.
Maciek: I'm still thinking about the data. Do you use AI, which everyone's talking about, in any other way apart from analyzing the return reason customers enter? Can you as a tool give merchants any other insights?
Krzysztof: For now we focus on analysis that helps improve the product offer where possible. We're analyzing different scenarios, but I can't announce anything specific right now.
Maciek: Okay.
Tomek: That sounded mysterious. I sense something's coming, but for now Krzysztof prefers not to lift the veil. I think he knows more than he's saying.
How does Wygodne Zwroty integrate with Shopify?
Maciek: Many of our listeners are merchants who use Shopify. What does the Wygodne Zwroty integration with Shopify look like right now?
Krzysztof: The integration means creating API access to Shopify. We integrate with the order system, and then we can plug in so that all the data is collected. We're integrating Shopify right now and development is just finishing. I think it'll be available very soon.
Maciek: Okay, so it'll be available. So far we have a few clients on Shopify who use Wygodne Zwroty, but it seems that's through some embedded form for now.
Krzysztof: Yes, but there are quite a lot of these clients on Shopify, and the number is growing, so we decided to build a full integration. It's already at the final stage. I think we'll really launch it soon.
Maciek: Okay, great news.
Tomek: We're glad to hear it.
2026 update (as of 14 November 2026): the integration is live. The app "Wygodne Zwroty - Integracja z WygodneZwroty.pl" has been on the Shopify App Store since 17 June 2026, with a free plan and a Polish-only interface. Customers enter their order details, choose the products to return and generate a shipment, and the store sees return statuses and reasons in its admin (apps.shopify.com/wygodne-zwroty).
How can you reduce the number of returns?
Maciek: It would also be great to hear some practical tips from you, maybe backed by data, that are most effective at lowering the number of returns. I know it's not your business, but what can you do to have fewer returns?
Krzysztof: I'd say it is our business. I want to provide a service that doesn't just handle returns but solves the returns problem in general. From my perspective, I may be saying obvious things, but I see that most or many stores still don't do them. Precise product measurements, really precise, without asterisks saying it may be five centimeters smaller or bigger as a rough range. Measuring all the dimensions. If there's a model in the photo, giving her height, or her measurements in general, so there's a point of reference.
This is more complicated, but imagine this. For example, I buy shoes. I always bought them in brick-and-mortar stores, where I could try them on and walk a bit, and eventually I started buying online. How did I handle the size problem? I simply went to the same manufacturer's site and bought exactly the same size. They arrived, and there was no problem. My point is: build a profile of your customers. We know this woman currently wears size X, and we suggest it to her, knowing how this product line runs. There are also external tools for this, a few foreign ones. In Poland I don't think there's anything sensible yet, and such tools reduce returns. I think those are the basics, and every store has its own tricks too.
Tomek: Yes. In general, it's really no secret, although, as you said, our observations seem to match: these seem to be very basic things and requirements for stores, meaning the right product presentation and describing the dimensions or the real values. In a physical store, you get that by touching the product. Except for touch, we can convey practically any other information about a product, and taking care of even this part of the site is already a big step forward. Then there's customer profiling. We're testing such tools too. As you said, they're not Polish solutions. They work on a very similar principle and even benchmark your measurements against brands you use and other brands, to find the size that will suit you best.
Krzysztof: Yes, I agree. I also see that some stores encourage customers to post on social media and then link those posts under the product. Someone writes there: "I'm this size. Look how it looks, what do you think?" That's also a cue, if someone identifies with that customer.
Where can you find Krzysztof Kukla?
Tomek: Exactly. I don't know about you, Maciek, but I think we've pretty much covered the topic. I won't say completely, because Krzysztof has built a whole company on it, and I think he has plenty of ideas. As you said yourself, you keep developing and adapting the tool to what's needed. You're also a great example of something that came up here more than once: simply listening to the opinions, comments and feedback you get from customers, so the product keeps getting better. As a Shopify agency, we're also really glad your tool will soon be fully integrated with Shopify, because it adds value to Shopify as a technology in Poland.
I think we managed to wrap it all into a very concrete dose of knowledge on how to break the spell of these not-so-loved returns and turn them to the store's advantage, how to make them valuable, and how to build loyalty and an even better brand experience. Krzysztof, thank you very much for sharing your experience so openly and willingly. As I said at the beginning, through all the brands you run, you know a great deal about order handling. Tell us, Krzysztof, where's the best place to catch you if a listener wants to ask you more or dig deeper? I assume if someone is interested in Wygodne Zwroty, you'll invite them to the website and to get in touch. But is there a chance that in your very busy world you find time to talk on LinkedIn or by email with people who might be very interested in these topics?
Krzysztof: Yes, I'm very happy to discuss and debate with people who are interested in returns and want to improve and optimize them. I've seen a lot over the last few years and I'm happy to advise or give tips, but also to learn, because you always have to stay open to others. Find me on LinkedIn; I think it's a good place. We also visit the largest stores, do audits and give advice, if anyone's interested.
Tomek: You point out their mistakes on site.
Krzysztof: Let's say so. At the store's request. It's not that someone matures on their own to the idea that things could be done a bit better.
Tomek: Great. Krzysztof, thank you once again for being with us today, for loads of really great information and a very substantive conversation. Thank you for accepting our invitation. I think our companies will cross paths in business many more times, and we'll connect our clients with your service. Take care.
Krzysztof: Thank you very much for the conversation. It was great and substantive. Take care, bye.
Tomek: Bye.


