A merchant recently shared on Reddit:

“Welp, the supplier never actually shipped the item and to this day the label/package has not moved. When a chargeback is issued for a Shopify collective order…. The RETAILER is responsible for returning all of the funds.”

A product that never moved from the supplier’s end agitates a customer who didn’t receive it. And of course, the retailer is the one reaching for their wallet because the customer skipped your support inbox and went straight to file a chargeback.

Welcome to collaborative commerce, everybody.

To be fair, Shopify Collective is a genuinely powerful model - expand your catalog, skip the inventory risk, onboard suppliers in a few clicks. The sales side is elegant enough. But the return side? Well, it is still figuring itself out. And that mismatch creates a fun little setup where the merchant closest to the customer absorbs all the risk while the merchant closest to the product carries on with their day.

This blog is about that gap. We’ll break down why returns in Collective are structurally different from normal ecommerce returns, what they’re actually costing you, and the financial layer most merchants might not have thought to build. (FYI that's the real meat.)

Let's start with who actually owns the losses. Spoiler: it’s you.

What’s the actual crisis? The return or the ownership vacuum?

With Shopify Collective, when the sale goes well, nobody needs to think too hard about who did what.  

But returns don’t work like that.

Say a customer buys a $120 product through your store. Your commission is 20%, so you make $24. But the product arrives defective and the customer emails you, not the supplier they’ve never heard of.

Meanwhile, you’re waiting on a supplier response that takes two days. The customer gets impatient, files a chargeback, and suddenly your $24 commission is gone - along with an added $15-$25 dispute fee and the $20-ish you spent acquiring the customer.

It’s an awkward setup: you get all of the customer's feelings, none of the supplier’s control.

One merchant using Collective shared:  

“Suppliers can break connection with no warning, even if there are transactions pending, shipping, payment, etc… I could go on but not enough time. We have over 300 suppliers in collective, and have used it since early availability. We have encountered every problem that can be imagined”  

Now imagine dealing with a return when the supplier just… vanished.

What makes this worse than traditional ecommerce returns is the lack of shared visibility. You see the angry customer. The supplier - if they see anything at all - sees a one-off return in their dashboard, disconnected from the pattern forming on your end. You're the one reading the reviews. They’re the ones who could actually fix the problem.  

The automated return policies come with an escape clause

Shopify did introduce automated returns policies for Collective in December 2024 - a genuine step forward. But if you onboarded before that update, your default setup is manual. No automation. No synced return labels.  

One retailer described the experience:  

“I have customers contacting me for the label - and I sound awful telling them that I, as the store owner, can't upload it. Then they are left skeptical because the customer doesn't (and honestly shouldn't) have to know how we are working as a drop ship business through Collective. I have to reach out to the brand and bug them to upload the labels for my customers in most cases.”

And if the supplier’s return policy doesn’t align with yours? Shopify's own docs say to “negotiate with them outside of Shopify Collective.”  

(Translation: you’re on your own.)

And now, the operational friction turns into a margin problem. Processing a single return costs retailers between $10 and $65 when you factor in shipping, inspection, restocking, and support time.  

Fun factUS retailers lost $849.9 billion to returns in 2025.  

Those are vicious numbers for any merchant. Now multiply all of that friction across two merchant operations instead of one - with misaligned policies, no shared defect data, and a retailer who isn’t even operating on a full markup.

What happens to your margins when a Collective order goes sideways?

The return window is the part everyone plans for. But what happens after that?  

That’s when a product starts acting up after a few weeks of normal use. You check the order, but your return window is over. You ping the supplier, but their policy is even tighter than yours. They’re done; the customer isn’t. After three days of silence, the customer calls their bank.

That chargeback lands on your desk, not the supplier's.

Collective merchants remain disproportionately exposed

To complete the 'middleman' trifecta, you can’t control the product quality that triggered this whole chain. You didn’t source the materials. You didn’t run QA. You didn’t pack the box.  

One merchant on Shopify's community forums pointed:  

“We rarely ever have chargebacks, but as of 2026 we are covered in fraudulent chargebacks with buyers not even having to return goods and banks approve the chargebacks, giving them free goods plus money back!”

Nearly 45% of consumers admit to some form of return fraud or policy abuse. Others are frustrated buyers who hit a dead end in your post-purchase experience and found the chargeback button before they found a solution.

But the refund isn’t even the most expensive part. It’s the costs around it.

Reverse logistics eats $10-$20 per return in shipping and processing alone - straight out of your commission. Every disputed order generates support tickets, mediation emails with a supplier who may or may not respond within the week, and hours of documentation if you decide to fight the chargeback. And the one-star “terrible experience, never buying here again” lands on your storefront.  

And then the customer is just… gone.  

Why the standard playbook for returns doesn’t quite work here

Shopify recommends detailed product photography and accurate descriptions to reduce disputes. Excellent advice. Now try doing that for 200 products you’ve never unboxed.

Retailers inherit supplier risk without full supplier visibility

On Collective, you’re working with whatever the supplier gives you. And what the supplier gives you isn't always complete. SKUs, tags, barcodes, and custom metadata don't always sync from supplier to retailer. One merchant summed it up:  

“Limited reporting. No way to rate suppliers. Documents don't show where order originated, so it causes confusion for the customer.”

In practice, that means the retailer is expected to deliver a seamless customer experience on top of infrastructure they don’t fully control or monitor.

And even when descriptions are accurate, it doesn’t always matter. One merchant vented on Reddit:  

“Customer said the product didn't fit, sent photos that matched the website exactly, then went straight to a chargeback. The bank sided with him, and I lost the product and paid a fee on top of it.”

Returns apps solve the routing not the bill

Some return apps have done genuinely excellent work integrating with Collective. But when a product fails and no return policy covers it, the app routes the package. It doesn’t write the check.

Everything in the current merchant toolkit handles day 5, day 14, day 28. The real exposure lives on the other side of the window, where the only option left involves the customer’s bank and your chargeback ratio.

“In fact most never contact us even tho they get multiple emails from us for shipping and confirmations an delivery updates and the others contact us ask for a refund and as soon as we tell them you have to return but here’s a prepaid label they stop replying and open a chargeback instead.”
-A frustrated merchant on Reddit

And tightening your return policy to reduce that exposure? 82% of consumers say a bad return experience means they won’t shop with you again.  

A few things you can actually control before the next return hits

• Vet your suppliers. Ask about their return window, their average defect rate, and their response time before you list a single product. If they can't answer those questions, they'll definitely struggle to answer a return request.

• Align your return window with theirs before your first sale goes live, not after your first chargeback.

• Track which SKUs generate the most support tickets. Five complaints about the same stitching defect is a supplier problem..

What changes when you add a protection layer to your post-purchase stack

With Collective returns, every failure funnels back toward the retailer’s balance sheet.

However, a protection plan changes that equation.

Instead of entering your support queue, waiting, getting frustrated, and calling their bank, the customer files a claim. Someone else handles the resolution. Someone else covers the shipping. The who pays the question that’s been haunting this entire blog? Off your desk.  

Most warranty claims resolve as store credit or a replacement order placed through your store. So not only does the original commission stay in your account, you might earn a second one when the replacement ships.  

And that matters because Shopify is clearly betting big on Collective.  

But the merchants who scale it profitably will need more than tighter return policies or faster support - they’ll need financial protection built into the post-purchase experience itself.