Amazon

Reconciling Amazon refunds against your supplier costs

When an Amazon order is refunded, two things need to happen and only one of them happens automatically. Amazon takes the money back from you. Whether your supplier gives you anything back is an entirely separate conversation that nobody starts on your behalf.

The asymmetry

The marketplace refund is fast, automatic and visible. It appears in financial events and reduces your payout.

The supplier refund is slow, manual and invisible unless you go looking. It requires you to notice, to raise it, and to follow it up. Nothing in your workflow forces that to happen.

So the default outcome, in the absence of a process, is that you refund the customer and eat the supplier cost. Once, that is a few pounds. At volume it is a line item.

Why it goes unnoticed

Because the two events are separated by weeks and live in different systems. The Amazon refund lands in a settlement report. The supplier cost was paid a month earlier and is sitting in a different account. Nothing joins them.

The join has to be the order id, and it has to be recorded at purchase time. Retrofitting it later means matching amounts and dates, which is slow and error-prone.

What to record, and when

• At purchase: marketplace order id, supplier order id, amount paid, date
• At refund: refund amount, date, reason
• On claim: date raised with the supplier, and the outcome
• Outstanding: anything refunded to the buyer with no supplier resolution

That last row is the one that earns the effort. It is a list of money you are owed, and without it that list does not exist anywhere.

Not every refund is worth chasing

Be honest about the economics. Chasing a three pound item through a supplier dispute process costs more in time than it recovers. Set a threshold below which you write off automatically and above which you always pursue.

The value of the threshold is not the money saved on small items - it is that above the line, the chasing actually happens, because you are not deciding case by case whether it is worth it.

Return shipping is the hidden cost

For a dropshipper, a physical return is usually uneconomic: the item is with the buyer, the supplier is overseas, and return shipping exceeds the value. So the practical choice is refund without return.

That is often correct. Just make it a decision rather than a default, and record it, because a pattern of refund-without-return on one product is telling you something about that product.

The number worth watching

Track refunds as a percentage of orders, per product. A single refund is noise. One product generating five percent refunds while the rest of your catalogue generates one percent is a product to stop selling, and you will never see it without the per-product view.

---