iqseller
enter the dashboardRequest access
← Back to blog

Negotiating the Cost of Returns With Your Supplier

October 11, 2026

Negotiating with your supplier using data Return rate More on Returns Return Policy by Channel

When a batch comes out bad, the seller almost always absorbs it quietly. Not because it seems fair, but because by the time they finally decide to talk to the supplier three months have passed, the units got mixed with other shipments, every return was logged under the same generic reason, and there is no way to prove that one specific batch was the problem. The conversation turns into “I think that order came in bad” versus “nobody else has complained,” and that conversation is not winnable.

The supplier isn’t necessarily acting in bad faith. They’re in the same position you are: without evidence, they can’t tell a legitimate claim from an attempt to renegotiate price after the fact. And since they can’t tell, their default answer is no.

The good news is that this is fixed with recordkeeping discipline, not with negotiating skill. What turns a complaint into an argument is being able to say: of the 240 pieces in the March 12 batch, 31 came back, against a historical average of 9 per 240, and 80% of those 31 are logged as a stitching defect, not as sizing. Faced with that, the tone of the conversation changes on its own.

This article is about how to get to that data, what to separate before asking for anything, and what you can realistically ask for.

iqseller panel on returns by batch and by cause
Illustrative view of the module in iqseller.

the split that changes everything

Before talking to anyone you need a distinction most catalogs don’t have: a defect return is not the same as an expectation return, and only one of the two is the supplier’s responsibility.

A defect return happens because the product fails its own specification: an open seam, a missing piece, a battery that won’t charge, a color that doesn’t match the sample, packaging that can’t survive transit, a unit that arrived with factory damage. Here the product failed against what the supplier committed to deliver. It is claimable.

An expectation return happens because the buyer expected something else: a size that runs differently, a material that looked thicker in the photo, a size that seemed larger on screen, a function the listing didn’t explain well. Here the product meets its specification; what failed was your listing. It isn’t claimable, and pretending otherwise burns the supplier relationship without recovering a peso.

There’s a third category worth keeping separate because it belongs to nobody: pure buyer’s remorse and bracketing. They are a structural cost of the channel and the category, and folding them into a claim only dilutes the argument.

The split matters for a strategic reason: when you show up with a total return count, the supplier can — fairly — say most of it isn’t their fault. When you show up with the clean defect fraction, isolated and counted, you take that exit away.

document by batch, not by month

Monthly records are useful for your operation and completely useless for negotiating. The supplier didn’t sell you months: they sold you batches. And if your data isn’t organized the way theirs is, no conversation is possible.

Documenting by batch means four concrete things, none of them complicated:

  • Tie every receipt to a batch identifier — purchase order number, shipment date, container number, whatever your supplier uses — and keep it in your inventory record, not just in email.
  • Don’t blend batches in the warehouse more than strictly necessary, or at least track consumption order so you know which batch fed which sales.
  • Log the real reason for each return at receiving, with a short, fixed taxonomy. Five well-defined categories serve you far better than twenty nobody uses consistently.
  • Keep the physical evidence: photos of the failure, with the unit and the identifier visible.

With that you can compute the only thing that matters: each batch’s defect return rate against your historical average for that same SKU. A batch outside the range is a verifiable fact. A bad month is an impression.

Glossary: lead time, the real time your restock takes →

what it actually cost you

The second component of the argument is the amount, and this is where most people undershoot, because they ask for the merchandise cost and stop there. The real cost of a defect return is considerably higher, and all of it is provable:

  • The COGS of the unit you can’t resell.
  • The outbound freight you already paid.
  • The return freight, when you absorb it.
  • The channel’s or the 3PL’s processing fee.
  • The commission that isn’t recovered, if that reason doesn’t get credited.
  • The handling cost: receiving, inspecting, photographing, classifying.
  • And the heaviest one, least often counted: the lost sale, when the defective unit occupied stock you couldn’t sell.

An example with invented but consistent numbers: 31 units returned for defect from one batch, with COGS of $520 each, outbound freight of $95, absorbed return freight of $120, and $70 of handling and inspection. That’s $805 per unit, $24,955 total. That’s the number you bring to the table, not “about 30 pieces came out bad.”

Note that the argument gets stronger when you include what you are not claiming. Telling the supplier “of the 74 returns on that batch, 43 were sizing and I’m absorbing those; I’m claiming the 31 defect ones” proves the recordkeeping is serious and that you aren’t inflating. Paradoxically, giving up part of the claim is what makes the rest credible.

what you can ask for

There are more options than “give me my money back,” and it’s worth ordering them by how easy they are for the supplier to grant, because what’s cheap for them is usually enough for you.

Replacement on the next order. The easiest to concede: it doesn’t touch their cash flow, only their inventory. It works well when the product stays in your catalog and you’re going to buy again. It’s the first option to put on the table.

A credit note. A balance applicable to future purchases. Stronger than a replacement because it gives you product flexibility, and still comfortable for the supplier because it isn’t a cash outflow. It’s the reasonable middle ground in most cases.

A price adjustment going forward. If the problem is recurring and structural — a manufacturing tolerance, a material that doesn’t hold up — there’s no point fighting batch by batch. Better to convert the expected return cost into a permanent per-unit discount. It’s the most honest option when the defect isn’t going to be fixed.

A cash refund. The hardest to get and the one that strains the relationship most. Worth reserving for large, clear, well-documented cases.

A change in specification or packaging. The option that creates the most long-term value and that almost nobody asks for. If the defect comes from packaging that can’t survive transit, negotiating a different box is worth more than any credit note, because it eliminates the cost instead of splitting it.

And one agreement worth building over time: a written tolerance threshold. “If a batch’s defect rate exceeds X, it gets replaced automatically.” Setting that while the relationship is healthy is infinitely easier than negotiating it in the middle of a problem.

how to raise it without breaking the relationship

The supplier is an asset, not an adversary. Delivery matters as much as the data.

Lead with the fact before the ask: first the per-batch number against the average, the photographic evidence, and the cost breakdown; then what you want. The other way around reads as pressure.

Ask for one thing, not a list. A claim with five requests gets negotiated down on all five. One with a single request has a binary answer.

Claim quickly. A batch from eight months ago can no longer be traced on the supplier’s side, and they will say no, quite reasonably. The practical window is short, which is another argument for keeping records current.

And don’t claim everything. If every shipment comes with a claim, the supplier stops distinguishing them and your signal loses value. Claiming the batch that genuinely fell outside the range, with data, once or twice a year, is far more effective.

Glossary: real net margin, with everything deducted →

how this reads in iqseller

In the Profitability module, a return isn’t a footnote: it enters as a provision inside each SKU’s contribution margin, computed from that product’s historical rate and from what a full return costs — refund, channel commission, FBA or Full fees, shipping, and the unit that sometimes comes back unsellable. That turns the supplier conversation into arithmetic instead of a perception: you know exactly how much of your margin is going into that product’s returns.

The COGS loaded by the user is the piece that makes the second step possible. Because the unit cost is yours and you manage it per product, costing a quality problem comes out of the same data you use to cost everything else, without a separate spreadsheet.

And the per-channel comparison of the same SKU is what decides whose problem it is before you write to anyone. If the product returns evenly on Amazon and MercadoLibre, the cause is in the product and the conversation is with the supplier. If it spikes on one channel only, the cause is in that listing and the work is yours. Starting there avoids the claim that doesn’t hold up, which is the one that burns the relationship without recovering anything.

The Inventory module supplies the batch side: knowing what stock came in when and at what cost is what lets you attribute returns to a shipment rather than to a month.

the order that works

Summarizing the method in the sequence worth applying:

  1. Separate defect returns from expectation returns, with a short, fixed taxonomy.
  2. Tie every receipt to a batch and keep the identifier.
  3. Compute the defect rate per batch against your historical SKU average.
  4. Rule out your own listing first, by comparing the rate across channels.
  5. Quantify the full cost, not just the merchandise.
  6. Ask for one thing, starting with the easiest to concede.
  7. And negotiate the tolerance threshold for the future, while there’s still no dispute.

None of those steps requires a sophisticated tool. They require the record to exist before it’s needed, which is exactly the part that gets postponed. And then, when the bad batch arrives — because it will — the difference between absorbing $25,000 and recovering it is having written a number down the moment you opened the box.

See every metric in detail →

start selling smarter

Request access
hola@iqseller.app