A pallet arrives at a shop in Antwerp. Eleven of the sixty vases are chipped. The buyer photographs them on the shop floor and emails you at nine in the morning, politely, expecting this to be sorted out today.

What happens next usually depends on who opens that email. One person credits the full eleven without asking anything. Someone else asks for the pallet photos first and discovers the shrink wrap was already torn when it left the depot. A third says yes to a replacement shipment and forgets to tell finance, so the original invoice goes to a reminder two weeks later for an amount nobody intends to collect.

None of those people did anything unreasonable. There was just no policy, so each of them invented one.

Returns are the least discussed part of wholesale and one of the most expensive. This article covers what counts as a return in B2B, why most of them settle as credit notes rather than refunds, what your policy actually has to say, and how to reduce the number of them you deal with in the first place.

Returns in B2B are not returns in retail

A consumer buying from a webshop in the EU gets a statutory cooling-off period. A retailer buying from you does not. Business-to-business returns are governed by what the two of you agreed, which means your terms are the whole story.

That cuts both ways. You are not obliged to accept a return because a buyer changed their mind, which is more freedom than consumer sellers get. But if your terms are vague, the agreement defaults to whatever is in the email thread, and email threads tend to favour whoever is more persistent.

So the question is never really "do we accept returns". It is "what did we agree, and can we find it".

Four things that all get called returns

Most brands lump these together and then wonder why the process feels inconsistent. They are four different problems with four different answers, and only one of them is genuinely optional.

The first three are your problem whether you like it or not. Goods that arrive broken, faulty or incomplete were not what the retailer bought, and arguing about it costs more than the goods do.

The fourth is a commercial decision and it is where brands get into trouble. Taking back unsold stock turns your wholesale model into consignment without the margin that consignment carries. Say no as a rule. Say yes occasionally, knowingly, to a key account, with a restocking fee and a time limit attached, and never as a standing arrangement that nobody wrote down.

Why B2B settles in credit notes

A refund moves money back out of your bank account. A credit note reduces what the customer owes you. In wholesale, where the same retailer orders again in eight weeks, the second one is almost always the right instrument.

It keeps cash in the business, it leaves a clean audit trail against the original invoice, and it gives both sides a document that accounting systems on either end can actually process. A bank transfer with "damaged vases" in the reference does none of that.

A usable credit note needs the same discipline as an invoice: its own number, the date, a reference to the original invoice and purchase order, the affected lines with their SKUs and quantities, the value, the VAT treatment, and one line saying why. That last field matters more than it looks. Six months of credit notes with a reason on each one is the cheapest quality report your business will ever produce.

Two rules worth holding. Raise the credit against the original invoice, not as a floating balance someone has to remember. And decide whether credits can be paid out in cash after a period, or only ever offset against future orders, because a retailer who stops ordering with 400 euros of unused credit will eventually ask.

What your policy has to say

A wholesale returns policy fits on one page. Anything longer will not be read, and anything shorter will be argued with.

It needs a notification window for damage and shortages, counted from delivery rather than from when someone got round to unpacking. Short is normal here: three to five working days. Carriers run their own claim deadlines and some of them are tight, so a buyer who tells you three weeks later has usually cost you the ability to recover anything.

It needs to say what proof you want. Photographs of the damage and the outer packaging, the delivery note, and a note on the carrier's paperwork at the point of signing where the damage was visible. Asking for this consistently is what separates a claim you can file from a conversation you can only concede.

It needs to state who pays return freight, and in which cases. Faulty goods, you. Buyer's convenience, them. It needs to say whether goods have to come back at all, because for low-value breakage the shipping often exceeds the product, and credit-without-return is cheaper for everyone.

It needs a restocking fee for anything discretionary, somewhere between 15 and 25 percent, which exists less for the revenue than to make casual over-ordering slightly uncomfortable.

And it needs to say what the remedy is: credit note, replacement, or refund, and who chooses. Usually you choose, and usually the buyer prefers a credit anyway.

Put all of it in the same place as your payment terms, show it at onboarding, and attach it to the order confirmation. A policy a buyer has never seen is a policy you will be negotiating.

Seasonal and pre-order goods need their own line

Standard terms rarely survive contact with a pre-order season. Goods were committed months earlier, produced against that commitment, and delivered into a window the buyer agreed to. A cancellation in week three of production is not a return, it is a cancelled contract, and it should be treated as one.

Write the cut-off into the season: after this date, orders are firm. Deposits are non-refundable past the point where production is placed. Late delivery by you is the one case that reopens the question, and it is worth saying so explicitly rather than leaving the buyer to assume otherwise.

Most returns are made upstream

It is tempting to treat returns as a logistics problem. Usually they are a data problem that surfaced in a warehouse.

A single SKU covering four colourways produces wrong-item claims forever, because the pick is ambiguous before anyone touches a box. One SKU per variant removes an entire category of return.

Stale information does the same thing in a different way. A buyer ordering from a PDF sent in February gets a product that was reformulated in April, and the complaint that follows is accurate. Ordering from a live catalog with current images, specs and stock means the goods match what was on screen.

Then there is the ordinary re-keying error. Orders arriving by email get typed into a system by a person, and a transposed quantity becomes 120 units of something a shop that size could never sell. That is one of the clearer arguments for letting buyers order directly rather than replacing Excel for wholesale orders later, after the credit note.

And packaging. If one product generates most of your transit damage, the fix is a better box, not a faster claims process. Track credit reasons for a season and that product will name itself.

What to measure

Three numbers are enough. Credit value as a percentage of invoiced revenue, which tells you the scale. Credits by reason, which tells you where to spend your time. Credits by product, which is the one that finds the packaging problem and the badly described SKU.

Anything above two or three percent of revenue going out in credits is worth a serious look. Most brands have never calculated it, which is why it tends to sit higher than anyone expects.

How Orderchamp Cloud helps

Orderchamp Cloud does not make returns disappear, but it removes most of the ambiguity they are built on. Every order placed through your branded B2B Portal is a structured record: the exact SKUs, the quantities, the prices that applied to that retailer, and the terms in force on the day. When a claim arrives, you are looking at what was ordered rather than reconstructing it from an email.

Because buyers order from a live catalog at their own customer-specific prices, with current images and stock, the mismatch that causes a good share of claims does not get created. Nothing is re-typed, so nothing is re-typed wrong. Order history sits in one place for both sides, which turns most disputes into a short conversation about a record you can both see, handled in the same wholesale order management flow as everything else. For the wider picture of what a complete setup covers, see our guide to a B2B e-commerce solution.

Want fewer claims and a cleaner record when they happen? Explore Orderchamp Cloud or book a demo.

Frequently asked questions

Do B2B customers have a legal right to return wholesale orders?

How long should retailers have to report damage?

Can retailers cancel a pre-order?

What's the difference between a credit note and a refund?

What should a wholesale credit note include?