Economics  ·  February 2025  ·  6 min read

Should you just absorb it yourself?

Plenty of merchants replace lost parcels out of margin and skip protection. Sometimes that's right. How to work out whether it is right for you.

Before adding protection to a checkout, it's worth taking the alternative seriously: keep absorbing the losses and don't offer anything at all.

Plenty of good brands do this. Some should carry on doing it.

The case for absorbing it

If your loss rate is genuinely low, your average order value is small, and your customers rarely have problems, then a protection offer adds a decision to your checkout in exchange for solving a problem you don't really have. Every element at checkout costs something in attention, and attention at that moment is expensive.

There's also a clean version of the brand argument. Replacing a lost order without being asked, without a fee, and without a claims process is a good experience. If your margin supports it and your volumes are small enough that it doesn't scale into a real cost, that's a legitimate strategy rather than a naive one.

Where absorbing it quietly stops working

Three things usually break it.

The first is volume. Absorbing losses is a fixed proportion of revenue, so it grows exactly as fast as you do. Merchants tend to notice this the year after they stop noticing individual replacements.

The second is basket value. Replacing a small item is a rounding error. Replacing an expensive one is a genuine hit, and high-value carts are also the ones most attractive to claim abuse.

The third, and the one that actually forces the decision, is your team. Absorbing the cost is only half of it. Somebody still has to field the message, check the tracking, make the call, arrange the replacement and chase the carrier. That labour doesn't appear in a loss rate, and it lands on the people you can least afford to have doing it.

The arithmetic worth doing

Pull your last twelve months and find four numbers. How many orders had a delivery problem. What did replacing them cost, including freight. How many support interactions did each one generate. What is an hour of your support team worth.

Multiply the third and fourth together and add it to the second. That total is what absorbing it currently costs you, and it's reliably larger than merchants expect, because the labour is usually bigger than the goods.

Then ask a separate question: of the customers who had a problem, how many ordered again. That's the number that decides whether this is a cost problem or a retention problem.

The answer isn't always to buy something

If the arithmetic says your losses are small and your team barely notices them, keep absorbing it. Adding a protection offer to a checkout that doesn't need one is a conversion cost with no return.

If it says the labour is the real expense, the useful question isn't who pays for the replacement. It's who does the work. Those are different problems and they have different answers, and plenty of vendors will happily sell you the first solution for the second problem.


Written by the Guide Team. We publish what we learn running this for merchants, not what ranks.

Read nextShipping protection is not insurance

The distinction sounds like a technicality until a regulator asks. What shipping protection actually is, and why merchants should know the difference.

Post-purchase, handled properly.

See Guide running on your own catalogue. Thirty minutes, and an honest read on fit.

Thirty minutes, on your own catalogue · Free to install, and our team does the build