Three channels, one book: what return rates actually tell a publisher

The same book returns at close to zero through offline distribution, barely measurably through a publisher’s own website, and at several percent on a third-party marketplace. Put those three numbers side by side in a review meeting and the conclusion writes itself: the marketplace is the problem and somebody is not managing it properly.

That conclusion is wrong. Return rate is not a measure of how well a channel is being run — it is a measure of how a channel is designed. Comparing the three without adjusting for that is like comparing a wholesale price to a retail price and concluding the wholesaler is underperforming.

Why do the three channels behave so differently?

Because they are three different transactions that happen to involve the same book.

	Offline distribution	Your own website	Third-party marketplace
Who is buying	A shop	A deliberate consumer	Someone searching for a title or a price
Who writes the returns policy	A negotiated trade agreement	You	The platform
Who adjudicates a dispute	Two businesses who expect to trade again	You	The platform
Consumer return rights	Do not apply	Apply, within your stated terms	Apply, generously, by design
End-customer change of mind	The shop’s problem; never reaches you	Governed by your policy	Funded by you
Who owns the customer	The shop	You	The platform

In offline distribution the buyer is a shop that sees the stock in bulk before accepting it. A customer who changes their mind is handled at that shop’s counter and never appears in your numbers at all.

On your own website the buyer is a consumer, but almost always a deliberate one. They came looking for you. Frequently they are a repeat buyer, an institution, a library, or someone who could not find the title elsewhere. And you write the returns policy.

On a marketplace, none of that holds. The policy is written by the platform and is deliberately generous, because generous returns are what make consumers willing to buy from sellers they have never heard of. That is the platform’s entire value proposition, and the seller funds it.

What is actually coming back?

Not what a returns process is built to catch. Genuine transit damage is a minority of cases. Two other patterns dominate, and neither is visible to a process that asks whether an item was defective.

Condition degradation with no claim of fault. The book arrives intact, is opened, is kept for a while, and comes back within the window in a state the platform finds acceptable and the publisher finds commercially useless.

Anyone who handles stock knows the signs on sight. A spine that has been fully opened and will not sit flat again. Pages that fan rather than sitting tight. Softened corners, a rubbed jacket, the faint curl a paperback takes after a week face-down on a table. Occasionally a folded corner two-thirds of the way in, which tells you roughly where the reader stopped.

Nothing on that list is damage. All of it is the difference between a copy you can sell and a copy you cannot.

This is where the mismatch bites. The platform asks whether the item is damaged. Your economics ask whether it is still saleable as new. Those are not the same question, and the gap is absorbed entirely by you. A new book is not just an undamaged book — it is an unhandled one, and a buyer paying full price can tell the difference the moment they open it.

Substitution. The returned item is not the item that was sent. Sometimes it is an unauthorised copy, sometimes an older printing, occasionally a different title of similar weight and dimensions.

A warehouse condition check confirms that a book of roughly the right size arrived in roughly the right condition. It is not an edition check, and the person doing it has seconds per parcel. Books are unusually exposed here compared with electronics, which carry serial numbers, or apparel, which carries tags — a book carries an ISBN on a cover that can be reprinted.

Neither pattern is a logistics failure, a listing error or an account management failure. Both are consequences of selling a high-value, easily substituted, easily consumed product under a returns policy you do not control.

Why the return reasons tell you nothing

Marketplaces commonly list books as replacement-only rather than returnable. Books still come back.

When they do, the customer selects a reason from a list, and that list is where the problem starts. The options are the ones used across a general catalogue: does not work properly, missing parts or accessories.

Consider what each of those would have to mean. Does not work properly — a book does not work. It has no moving parts, no power supply and no firmware. There is no state in which it fails to function, only states in which it is damaged, and damage has its own reason code.

Missing parts or accessories. A book arrives with all of its parts, on account of having one.

Neither reason can be literally true of a bound volume. They arrive anyway, in volume.

What this means in practice is that someone who wants to send a book back picks whichever option is nearest to hand, and the seller receives a defect report for an object that cannot be defective in the sense the word is being used. The genuinely damaged copy and the pretext arrive under the same label.

That is why the reason data cannot be used to improve anything. If a batch really did have a binding fault, it would be indistinguishable from a month of changed minds. The one signal that would tell a publisher something useful about their own production is destroyed before it reaches them.

It also makes cross-category comparison meaningless. A defect rate for a book and a defect rate for an appliance are not measuring the same thing, however similar the two figures look on a dashboard.

This is not a case of sellers being cheated by buyers so much as a category being served by a system built for something else. The fix is not available to the seller, which is worth stating plainly: on this channel, you cannot improve the quality of your own returns data.

Does the unboxing video requirement work?

Yes, but not mainly for the reason people assume — and it is available only on your own channel.

One publisher we work with requires a continuous recording of the package being opened before any return or refund claim is accepted. The condition sits in the published policy, visible before an order is placed rather than produced at the moment a claim is made.

The enforcement value is real but narrow. A recording settles the two disputes that are otherwise unwinnable: whether the right item was sent, and what condition it arrived in. Against substitution claims it is close to decisive, because that fraud depends on there being no record of what came out of the box.

Its limits matter too. It does nothing about a customer who receives exactly what they ordered, reads it, and returns it — the video simply confirms a perfect book arrived. And it documents what came in, not what goes back, so capture evidence on the return leg as well.

The larger effect is selection, not enforcement. Because the requirement is stated before purchase, it is read by everyone — including the few people considering a return they are not entitled to. They go elsewhere. The policy filters at the point of entry rather than adjudicating afterwards, and filtering is always cheaper than adjudicating.

Two cautions. The condition must be prominent and plainly worded at checkout, not buried in terms — a requirement customers only discover when they try to claim reads as bad faith and costs more in public complaints than it saves in refunds. And apply it with judgement: a genuine customer with a genuinely damaged book who forgot to record is someone you want to refund and keep. The policy is there to deter the deliberate, not punish the forgetful.

Confirm with your own legal advisor that a conditional-refund clause is enforceable where you trade, since consumer protection rules constrain how far a stated policy can override a legitimate claim.

None of this is available on a marketplace. You cannot add the condition, display it before purchase, or apply it when a claim is made. The tool that works best is precisely the one that channel takes away.

Is contesting the claims worth it?

Do it, and be realistic about the yield.

Claims processes are built to identify clear-cut fault: wrong item, missing item, obvious damage. They are not built to adjudicate “this copy is no longer sellable as new.” Documenting a returned book as visibly read, or as a different edition from the one dispatched, frequently does not clear the threshold the process is looking for.

Expect a recovery rate, not a remedy. Build the evidence capture anyway, then plan your economics as though most of the loss stays with you.

Where are the returns actually coming from?

This was the most useful thing to come out of the analysis, and it was not about the returns themselves.

Return abuse does not distribute evenly. It concentrates, heavily, in specific delivery areas — tightly enough that a small number of postal codes can account for a disproportionate share of a national return rate.

That changes what you can do about it. A publisher facing a national return rate has two obvious options, both bad: absorb it, or withdraw from the channel. A publisher who knows the returns are concentrated has a third — restrict serviceability at postal-code level, and keep every other customer.

The temptation under pressure is to restrict at state level. It is fast, it is one setting, and the number drops immediately. It also removes millions of legitimate customers to solve a problem caused by a few thousand. Treat it explicitly as a temporary measure while the postal-code analysis is completed, and hold yourself to finishing that analysis. A state-level block that quietly becomes permanent because nobody revisited it is a large, invisible revenue decision made by default.

Worth naming what a broad block means: a publisher who cannot deliver to entire regions has decided who gets access to its books. That may be a cost worth accepting. It should be accepted deliberately, not arrived at as a side effect of a dashboard looking better.

What should be on the review table instead?

Return rate is a cost ratio being read as a performance score. Replace it with the measure that actually decides anything: contribution per channel, after all channel-specific costs.

For each channel, take revenue and subtract everything that channel specifically costs — commissions and platform fees, fulfilment and shipping, payment charges, returns valued at the true loss rather than a notional restocking fee, reverse logistics, and the management overhead the channel requires.

For a read-and-returned new book, the true loss is close to the full unit cost. The copy cannot go back into saleable stock at full price. What is left is a secondary route — remaindered, sold as shelf-worn, given away, or pulped — and none of those recovers the margin the sale was supposed to produce.

This is worth being precise about, because a publisher already knows what a returned copy is worth. Whoever built the returns report usually does not, and a notional restocking figure carried into the channel comparison is how the marketplace ends up looking better or worse than it actually is.

What comes out is often counterintuitive. Offline shows almost no returns but carries deep trade discounts, long payment cycles and a working-capital cost. Marketplace shows painful returns alongside customer acquisition you did not pay for and reach into markets where you have no physical distribution. Direct usually shows the best margin per unit and the hardest ceiling on volume.

A channel with several percent returns can be worth more than a channel with none, and frequently is. You cannot see that from the return rate, and a review meeting that stops there will keep reaching the wrong conclusion with complete confidence.

What actually reduces the number?

In rough order of return on effort.

• Target the geography precisely. Postal-code-level restriction based on actual return data, reviewed quarterly. The highest-yield lever available, and the only one that does not cost you legitimate customers.
• Capture dispatch evidence systematically. Weigh, photograph, seal. It will not win every dispute, and it will win some.
• Make the listing do more work. Precise edition, binding, print year, page count, and photographs of the actual copy condition. A meaningful share of returns are expectation mismatches, and those are the cheapest to eliminate.
• Treat the channel as one input among several. A marketplace is very good at reach and structurally unable to protect margin. Titles where margin is thin and abuse risk is high may belong elsewhere. That is a portfolio decision, not a failure.
• Keep building the direct channel. Slower, but the only one where you write the rules — on returns, on payment terms, on the customer relationship.

The uncomfortable summary

Marketplace returns in book retail are not primarily an execution problem. They are the price of access to a channel whose rules are written by someone else, and they will not be managed down to the levels an offline trade channel produces, because the two are not the same kind of transaction.

The right response is not to fix the return rate. It is to price the returns honestly, target the concentrated abuse precisely, and then decide — with a real contribution number in front of you — whether the channel earns its place. Quite often it does. But that should be a finding, not an assumption, and certainly not a verdict handed down from a comparison that was never valid to begin with.

If you are not selling online yet

Much of the above reads as an argument against selling online. It is not. It is an argument for building the channel in the right order.

Start with your own storefront, where you write the returns policy, set the payment terms and own the customer record. Get the catalogue structured properly, the conditions stated clearly and the fulfilment reliable. Only then extend to marketplaces, treating them as a reach channel with known and priced-in costs rather than as the foundation.

Publishers who do it the other way round — marketplace first, direct later — spend years funding someone else’s customer acquisition and arrive at their own storefront with no list, no data and no habit of buying direct.

The objection we hear most often is cost, and it is largely out of date. A capable, stable storefront can be built on Shopify for a fraction of what a custom build used to require, with catalogue, payments, shipping and returns policy configured properly from day one. We build on Shopify and we build custom, so we have no stake in which answer suits you — and for a book catalogue, where the structure runs to thousands of titles with real metadata, how that catalogue is organised matters more than the platform does.

Layering business messaging on top costs little and does more for repeat purchase in most book businesses than paid advertising. Order confirmation, dispatch updates with tracking, delivery confirmation and reorder prompts on WhatsApp get read, where email does not. It also removes the “where is my order” calls your team is currently answering.

We build and manage exactly this. If you are a publisher, distributor or bookseller weighing a first move online — or reassessing one that is not performing — tell us where you are and we will look at the numbers with you, including the ones in this article.

Common questions

Is a marketplace return rate of several percent normal?

For books it is not unusual, and the figure on its own tells you very little. What matters is what the returns cost you after the returned stock is written down honestly, and whether the channel still contributes once that is subtracted.

Can we require an unboxing video on a marketplace?

No. The returns policy on a marketplace is the platform’s, and a seller cannot add conditions to it or apply them when a claim is made. The requirement only works on a channel where you write the terms.

Books are replacement-only on the marketplace. Why are we still getting returns?

Replacement-only describes the policy, not what happens. Claims still get raised, still get accepted, and stock still comes back. Plan on the basis of what arrives at your warehouse rather than what the policy page says.

How do we find which postal codes are the problem?

Export returns with delivery pincodes and count them against orders shipped to the same pincodes. Rate matters more than volume — a pincode with twenty returns from a thousand orders is fine; one with eight from fifteen is not. Review quarterly rather than once.

Should we stop selling on marketplaces?

Only if the contribution number says so. For many publishers the marketplace reaches readers no other channel does, and pays for itself even with the returns. Work out the number before deciding.

Does any of this apply outside publishing?

The channel structure does — anyone selling the same product through distribution, direct and a marketplace faces three different sets of rules. The specific exposure is worse for books because they are high value, easily substituted and consumable without being damaged.

More on this: Shopify or a custom build and returns and damage. See also eCommerce development.